ethernet interface problem?

[jjanderson5]

I have a LAN setup with 3 Kubuntu PCs running Kubuntu and 1 PC running Windows XP.
I have internet connectivity on one of the Kunbuntu PCs and on the Windows PC. The
other 2 PCs have lost internet connectivity.

The two with no connectivity are running 7.04 and 7.10 versions of Kubuntu.


It looks to me like they have no local IP address. From the PCs, named 'hodges'
and 'peewee', that have no apparent IP address I can ping the PC named 'spooner'
which does have connectivity. So I know my ethernet is working. I can also ftp
from hodges and peewee to spooner.

Last night I had full internet connectivity from peewee, but this morning I ran into
the current problems. I rebooted both peewee and hodges just to see what would
happen, but that did not help.

I ran 'ifconfig' on each of them. Spooner looked normal to me, but both hodges and
peewee gave results I have not seen before. In particular, no IP address showed up
for 'eth0'. The results of ifconfig for each PC is shown at the end.

It seems to me that if no IP address shows up on the ifconfig output, that would
indicate there is not IP address currently assigned to the PC and hence the PC
will not work on the LAN. Is this correct? What then do I do to get my ethernet
configuration reset to normal?

As a curiosity, the ifconfig output for hodges and peewee shows
an entry for eth0:avah. I did a search and it looks like this can
be used with wireless and/or wired connections. Maybe this
should work for me, but the IP address show is not the typical
192.168.xxx.xxx that I would expect to be used for my LAN.

Can someone help? Thank you in advance.

Jim Anderson



ifconfig output from spooner


eth0 Link encap:Ethernet HWaddr 00:40:F4:48:E9:0B
inet addr:192.168.2.100 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::240:f4ff:fe48:e90b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2709 errors:0 dropped:0 overruns:0 frame:0
TX packets:1091 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:484363 (473.0 KiB) TX bytes:249137 (243.2 KiB)
Interrupt:10 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:82 errors:0 dropped:0 overruns:0 frame:0
TX packets:82 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6512 (6.3 KiB) TX bytes:6512 (6.3 KiB)




ifconfig output from hodges


eth1 Link encap:Ethernet HWaddr 00:04:23:15:71:FD
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:106 errors:0 dropped:0 overruns:0 frame:0
TX packets:1395 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:9538 (9.3 KB) TX bytes:63127 (61.6 KB)

eth1:avah Link encap:Ethernet HWaddr 00:04:23:15:71:FD
inet addr:169.254.7.63 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:828 errors:0 dropped:0 overruns:0 frame:0
TX packets:828 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:83833 (81.8 KB) TX bytes:83833 (81.8 KB)






ifconfig output from peewee


eth0 Link encap:Ethernet HWaddr 00:10:5A:AB:E5:01
inet6 addr: fe80::210:5aff:feab:e501/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1257 errors:0 dropped:0 overruns:0 frame:0
TX packets:806 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:84475 (82.4 KiB) TX bytes:60109 (58.7 KiB)
Interrupt:10 Base address:0x4000

eth0:avah Link encap:Ethernet HWaddr 00:10:5A:AB:E5:01
inet addr:169.254.6.95 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:10 Base address:0x4000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:546 errors:0 dropped:0 overruns:0 frame:0
TX packets:546 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:52380 (51.1 KiB) TX bytes:52380 (51.1 KiB)

[Detonate]

Re: ethernet interface problem?

This problem has been seen before, and I'm pretty sure it has something to do with the avhi-dameon.
And a problem with DNS. Do a search on that unusual IP address and avhi-dameon and hopefully you will come up with some pertinent threads.

[jjanderson5]

Re: ethernet interface problem?


I did not find too much on my search, but it looks like the avahi daemon
should work. It looks to me like the address that it assigns is my problem.
The address assigned is 169.254.6.95. When I checked my router, it
is configured for dhcp with a range from 192.168.2.100 to 192.168.2.149.

I think if I can limit the range for avahi to match this IP range, things should
work. Is this possible? I'm trying to find documentation now and will post if
I find the answer.

Jim Anderson

[Detonate]

Re: ethernet interface problem?

Have you tried using a static IP? Just set a static IP, say 192.168.2.150 on one of the computers and 192.168.2.151 on the other.

[jjanderson5]

Re: ethernet interface problem?

I was able to fix this by going to

system settings -> network Settings -> Zeroconf service directory.

I disabled Zeroconf.

I was then able to go to

system settings -> network Settings -> network connection

where I disabled the ethernet connection and deleted it. I then
create a new ethernet connection with an address 192.168.2.101.
This works.

[Detonate]

Re: ethernet interface problem?

That's good to know that Zeroconfig may be part of the problem.