I recently upgraded my myth box to my old desktop -- Athlon 64 3500+ on an ABIT AV8 motherboard. I had been using a USB wireless adapter (Linksys WUSB54G, I think) and had gotten use to the seemingly unsolvable problem of having to either run dhclient a couple times once the machine boots or letting it sit for 30-40 mins on its own before it connects to the router and obtains an IP address.
After a fairly smooth auto-upgrade with the new hardware, I'm noticing that a mysterious "eth1" has appeared and is filling up syslog pretty regularly. After being on overnight, the system had froze, and I think it might be because of this. eth0 is the USB device -- not sure what eth1 is:
Code:
Mar 10 06:16:26 mythtv dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
Mar 10 06:16:31 mythtv dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
Mar 10 06:16:40 mythtv dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
Mar 10 06:16:50 mythtv dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
Mar 10 06:17:00 mythtv dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
Mar 10 06:17:01 mythtv /USR/SBIN/CRON[6666]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Mar 10 06:17:11 mythtv dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 10
Mar 10 06:17:21 mythtv dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
Mar 10 06:17:27 mythtv dhclient: No DHCPOFFERS received.
Mar 10 06:17:27 mythtv dhclient: No working leases in persistent database - sleeping.
Mar 10 06:23:44 mythtv dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
Mar 10 06:23:51 mythtv dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 21
Mar 10 06:24:12 mythtv dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
Mar 10 06:24:27 mythtv dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 18
Mar 10 06:24:45 mythtv dhclient: No DHCPOFFERS received.
Mar 10 06:24:45 mythtv dhclient: No working leases in persistent database - sleeping.
I disabled the onboard ethernet adapter in BIOS, and thought maybe if I enabled it it would somehow see there is nothing connected and just ignore it. Unfortunately, my troubles have multiplied like tribbles and now there is an additional eth2-rename added to the mix:
Code:
Mar 10 21:35:29 mythtv dhclient: There is already a pid file /var/run/dhclient.pid with pid 3428
Mar 10 21:35:29 mythtv dhclient: killed old client process, removed PID file
Mar 10 21:35:29 mythtv dhclient: Internet Systems Consortium DHCP Client V3.0.4
Mar 10 21:35:29 mythtv dhclient: Copyright 2004-2006 Internet Systems Consortium.
Mar 10 21:35:29 mythtv dhclient: All rights reserved.
Mar 10 21:35:29 mythtv dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Mar 10 21:35:29 mythtv dhclient:
Mar 10 21:35:32 mythtv dhclient: Listening on LPF/eth2_rename/
Mar 10 21:35:32 mythtv dhclient: Sending on LPF/eth2_rename/
Mar 10 21:35:32 mythtv dhclient: Listening on LPF/eth1/00:12:17:9c:11:9f
Mar 10 21:35:32 mythtv dhclient: Sending on LPF/eth1/00:12:17:9c:11:9f
Mar 10 21:35:32 mythtv dhclient: Listening on LPF/eth0/00:50:8d:d7:66:23
Mar 10 21:35:32 mythtv dhclient: Sending on LPF/eth0/00:50:8d:d7:66:23
Mar 10 21:35:32 mythtv dhclient: Sending on Socket/fallback
Mar 10 21:35:32 mythtv dhclient: DHCPDISCOVER on eth2_rename to 255.255.255.255 port 67 interval 7
Mar 10 21:35:32 mythtv dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
Mar 10 21:35:32 mythtv dhclient: DHCPOFFER from 192.168.0.1
Mar 10 21:35:32 mythtv dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67
Mar 10 21:35:32 mythtv dhclient: DHCPACK from 192.168.0.1
Mar 10 21:35:32 mythtv dhclient: bound to 192.168.0.102 -- renewal in 296650 seconds.
Mar 10 21:35:34 mythtv dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Mar 10 21:35:39 mythtv dhclient: DHCPDISCOVER on eth2_rename to 255.255.255.255 port 67 interval 9
Mar 10 21:35:39 mythtv dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Mar 10 21:35:48 mythtv dhclient: DHCPDISCOVER on eth2_rename to 255.255.255.255 port 67 interval 10
Mar 10 21:35:53 mythtv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
Mar 10 21:35:55 mythtv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Mar 10 21:35:58 mythtv dhclient: DHCPDISCOVER on eth2_rename to 255.255.255.255 port 67 interval 12
Mar 10 21:35:59 mythtv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
Mar 10 21:36:00 mythtv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
Mar 10 21:36:10 mythtv dhclient: DHCPDISCOVER on eth2_rename to 255.255.255.255 port 67 interval 11
Mar 10 21:36:10 mythtv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
Mar 10 21:36:13 mythtv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
Mar 10 21:36:21 mythtv dhclient: DHCPDISCOVER on eth2_rename to 255.255.255.255 port 67 interval 12
Mar 10 21:36:24 mythtv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
Mar 10 21:36:24 mythtv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
Mar 10 21:36:33 mythtv dhclient: No DHCPOFFERS received.
Mar 10 21:36:33 mythtv dhclient: No working leases in persistent database - sleeping.
Mar 10 21:36:39 mythtv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
Mar 10 21:36:41 mythtv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
Mar 10 21:36:52 mythtv dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Mar 10 21:36:54 mythtv dhclient: No DHCPOFFERS received.
Mar 10 21:36:54 mythtv dhclient: Trying recorded lease 192.168.0.102
Mar 10 21:36:54 mythtv dhclient: bound: renewal in 263722 seconds.
Mar 10 21:36:56 mythtv dhclient: No DHCPOFFERS received.
Mar 10 21:36:56 mythtv dhclient: No working leases in persistent database - sleeping.
I've tried a number of things: ifconfig eth1 down, creating a file called "ifcfg-eth1" in /etc/sysconfig/network-scripts/ and setting "ONBOOT=no", creating a script to do ifconfig eth1 down and having it run at bootup ... no luck.
During boot up when it says "Starting networking...", dhclient runs and only tries to connect using eth0 (which fails to work -- as I said, it normally takes a couple of tries). So somewhere after that eth1 and now eth2-rename are getting added to the mix.
Here is my /etc/network/interfaces:
Code:
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# The loopback interface
# automatically added when upgrading
auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp
Any clue on what is going on, and how I might go about fixing it?
Thanks!
- Anthony
View unanswered posts
View active topics
KnoppMyth 
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register
