You are not logged in.

#1 2007-07-31 12:37:12

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

Upgraded IPW3945 Yesterday and....

I upgraded the IPW3945 package a day or two ago and my "eth2" interface became "eth1".  My "eth0" is my wired LAN card and eth1 (formerly eth2) is my wireless card.  I'm on a laptop and so seldom (if ever) use the wired (eth0) card.  The wireless works (after changing eth2 to eth1).

Anyway, ever since the upgrade I am getting my "/var/log/everything.log" filled up with this:

Jul 31 08:26:25 plunkerbunkey dhcpcd[4845]: eth0: broadcasting for a lease
Jul 31 08:26:55 plunkerbunkey dhcpcd[4845]: eth0: timed out
Jul 31 08:26:55 plunkerbunkey dhcpcd[4845]: eth0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth0.info'
Jul 31 08:26:55 plunkerbunkey dhcpcd[4845]: eth0: checking 169.254.40.121 is available on attached networks
Jul 31 08:26:56 plunkerbunkey dhcpcd[4845]: eth0: adding IP address 169.254.40.121/16

This happens over and over and over.  I tried changing the line in rc.conf for INTERFACES to read:

INTERFACES=(lo !eth0 eth1)

but it didn't stop the messages.

Here is the pertinent section of my rc.conf:

lo="lo 127.0.0.1"

#---- Wired (LAN)
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
eth1="dhcp"

#---- Wireless (eth1)
wlan_eth1="eth1 essid NotForGeneralUse"

WLAN_INTERFACES=(eth1)
INTERFACES=(lo eth0 eth1)

Does anyone have a clue on how to "disable" this?  I tried setting eth0 to a "static" address but that didn't work either.  It's like something else is telling the PC that eth0 is "active".

Thanks in advance for the help.


Matt

"It is very difficult to educate the educated."

Offline

#2 2007-07-31 15:19:44

mykhal
Member
Registered: 2007-04-03
Posts: 35

Re: Upgraded IPW3945 Yesterday and....

If your dhcpcd version is >= 3.1.1, try to downgrade, it might solve your problems.

Last edited by mykhal (2007-07-31 22:25:40)

Offline

#3 2007-08-01 12:17:28

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

Re: Upgraded IPW3945 Yesterday and....

Well, there was a dhcpcd upgrade to 3.1.3 last night.  I tried it and it didn't work.  I'm going to try one more thing, then downgrade and see if that works....


Matt

"It is very difficult to educate the educated."

Offline

#4 2007-08-01 13:04:08

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

Re: Upgraded IPW3945 Yesterday and....

Rolled back to dhcpcd 3.0.19 and the messages went away.  This means that SOMETHING changed.  Unfortunately I'm not smart enough to know how to narrow things down any farther.  I'm also not necessarily SURE this is a "bug".  The laptop still works as normal with the latest dhcpcd, it's just that it keep searching for an IP address on the WIRED LAN connection when it's not plugged in (AND filling up the log!!).  Could this be an issue with ifplugd and dhcpcd?  Should I report a bug on this?


Matt

"It is very difficult to educate the educated."

Offline

#5 2007-08-01 13:29:52

mykhal
Member
Registered: 2007-04-03
Posts: 35

Re: Upgraded IPW3945 Yesterday and....

Offline

#6 2007-08-01 14:24:37

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

Re: Upgraded IPW3945 Yesterday and....

OK, will do.  Thanks!


Matt

"It is very difficult to educate the educated."

Offline

#7 2007-08-12 10:26:36

shining
Pacman Developer
Registered: 2006-05-10
Posts: 2,043

Re: Upgraded IPW3945 Yesterday and....

I get this dhcpcd error on my wireless interface, not on my ethernet interface.
After each boot, I've to restart the network, and this time dhcpcd works. It's very annoying.
I downgraded dhcp to 3.0.19 and still have the same problem.
So I suppose it's an issue with ipw3945, not with dhcpcd ?


pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))

Offline

#8 2007-08-12 17:35:30

shining
Pacman Developer
Registered: 2006-05-10
Posts: 2,043

Re: Upgraded IPW3945 Yesterday and....

shining wrote:

I get this dhcpcd error on my wireless interface, not on my ethernet interface.
After each boot, I've to restart the network, and this time dhcpcd works. It's very annoying.
I downgraded dhcp to 3.0.19 and still have the same problem.
So I suppose it's an issue with ipw3945, not with dhcpcd ?

I changed several things today, and now it works again..
The main change I did is switching back from iphitus network scripts ( http://wiki.archlinux.org/index.php/Network_Scripts ) to default arch scripts.

Maybe it brings up the interface differently, or maybe I didn't configure them exactly in the same way.. I'm not sure.
For example, I now have this line :
IWOPTS="mode managed essid $ESSID channel 11"

While in my profile with the new system, I only specified the essid, not the channel.


pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))

Offline

Board footer

Powered by FluxBB