Hi there,

I am trying to get connected onto a network with a DHCP setting, 3Com PCI card in FC 3. There has been no problem, but now that it is connected to a new DSL service, IP address can not be determined. I checked 'lsmod', 'lspci', whose output seems to be as expected.

'ifconfig' yields 'lo' and 'eth0'. 'eth0' section has an unexpected output, which includes what seems to be 'IPv6' (shows inet6 addr) without inet addreess. Under GUI setting I did not choose IPv6 for eth0.

'route' command yields:

169.254.0.0 * 255.255.0.0 U 0 0 0 lo

which misses 'eth0'. 'ifconfig' does show 127.0.0.1 for 'lo', and the above
result contradicts what is in ifconfig.

The first time when my laptop was moved to a new connection, it complained that the link in /etc/sysconfig/network-scripts/ifcfg-lo.rpmsave does not have a target, so I created one by copying from another location.
Since then when I try to activat 'eth0', IP address determination fails.

Ideas will be much appreciated !

Have you tried "route add -net default gw 192.168.1.1 dev eth0" to see if you could get it going?

..

Hi,

Thanks for the suggestion.

The output of
# route add -net default gw 192.168.1.1 dev eth0
>> SIOCADDRT: NETWORK is unreachable

What would this mean ?

Another thing I noticed is that 'ifconfig -a' shows 'sit0'. I have not explicitly enabled ipv6 previously, and /var/log/messages says

'dhclient sit0: unkonwn hardware address type 776'.

Previously (maybe the last time before I moved to a new network) I used a netgear router with a wireless card - would it have somehow affected the setting ?

"169.254.0.0"
==========

Addresses in the range 169.254.0.0 to 169.254.255.255 are used automatically by some PCs and Macs when they are configured to use IP, do not have a static IP Address assigned, and are unable to obtain an IP address using DHCP.

Thanks. If I try

# route add -net default gw 169.254.0.0 dev eth0

it still does not allow me to add a route. So just to try out, I did

# ifconfig eth0 169.254.0.1 netmask 255.0.0.0
then did the above route command, 'eth0' does show up in a routing table.

My question now is how to figure 'eth0' to work with DHCP.
Any ideas ?

Edit:

/etc/sysconfig/network-scripts/ifcfg-eth0


Add:

BOOTPROTO=dhcp

Run:

/etc/rc.d/init.d/network restart

or

ifdown eth0
ifup eth0

# you'll need to be root for all this.

Thanks. The script for eth0 already has the line to have DHCP, and still it does not work.

Just thinking about it, my previous connection had a router and a modem, but the current one only has a modem. Will it be a possibility that my laptop is looking for a modem ?
If so, how to detect this and how to fix this problem ?

With your current connection do you have a static IP, or is it dynamic? If you dont know call your ISP, and ask. Seeing how you are posting I'm guessing you have another computer that you are hooking up to this modem?

If so make sure you reboot the modem when you switch from one computer to another. Also did you ever give the ISP the MAC address of your other computers ethernet card?

Hi

This is a long shot, just so that's said


I once had the same dilemma with a wireless connection and ndiswrapper

If you type "arp" I guess you get no output or HWADRESS (Incomplete) ?

If so, find the module that belongs to your NIC , rmmod that module, modprobe it, restart network services (don't reboot) and type "arp" again (or route). It might just show up probably.

If an expert reads this : I know, I know.... but it worked once for me

Good luck

Thanks all. Yes, I have tried your suggesetions, but the same problem persists ...
Help !

It's weird, my 3com 3c-905tx card also faces the same issue in debian 3.1. But i switched to a Intel card already.

Try setting a static IP address and see whether it is able to ping the router

3com card did that to me to in Debian, MAC address kept disappearing .... not experiencing any of that are you ? Just a thought

I believe the issue is that the network device, eth0, is looking for a DHCP address and it is not receiving one. That being said, this device is not getting one, so the interface is not coming up. Since the device is not up it will not show in the route table.

Mike K.

Thanks for replies.

As I said earlier, I do not have a router for this new connection. I think that might cause a problem since when I had a router/modem combination I had no problem, and not it suddenly pops up. In fact before the router/modem combination I did not have a problem connecting to this very network.

Obviously eth0 is not getting IP address, and if I assign IP address etc., eth0 does get active, but obviously my network is set up for DHCP.

So the problem does still exist !