You may be able to do an "if" statement in your boot up files to
connect to the cable before your network loads, not sure if that will work
though. The "10" address is a private address that your system
automatically assigns when no DHCP server is found. You may want to assign
a private IP to the card, as a secondary, that may take the time off for
the boot looking for a DHCP server. Unfortunatly, if you don't connect
till after you boot, then you may have a very hard time getting a
resolution to this unless your provider can give you something that will be
a permenant connection, or static IP address. (which you can get from most
cable providers if you ask) Getting a static IP may be your best
bet. Hope this helps!
Fred
At 09:45 PM 12/17/00 -0400, you wrote:
>Need some network guidance. I'm not an expert so feel free to throw the
>information
>at me.
>
>I just got a cable modem (the older type that dials) and after some fiddling I
>managed to get it to dial and connect for me. There are two oddities
>however. When
>the box boots eth0 takes forever to come up. Makes sense since its using
>DHCP but how
>can I work around this? I don't connect until after I boot, obviously.
>
>When I bring the box down eth0 will not come down and I have to power off.
>I have
>been able to work around this by doing an ifconfig eth0 down before
>shutting down.
>Why does an ifconfig eth0 down work while the shutdown command hangs?
>
>Also, after I boot, an ifconfig reveals an IP address like 10.2.23.3. (or
>something
>like that) Since I'm using DHCP, an IP address would not be obtained until
>I manually
>connect to my ISP. Where did the 10... address come from?
>
>Any network gurus that may have some pointers?
>
>Thanks
>Mike
>
>
>
>
>
>_______________________________________________
>Redhat-list mailing list
>[EMAIL PROTECTED]
>https://listman.redhat.com/mailman/listinfo/redhat-list
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
