Can't connect on wired network - Bad file descriptor

leandroaveiro · 2009-09-15 22:14:55

Hi everybody...

I'm using wicd daemon and never had any trouble before... in fact, I can connect normally to other wired and wireless networks. But recently I stambled onto a network which I can connect on Windows normally, but on Arch, wicd log says the following:

2009/09/15 21:01:12 :: Putting interface down                                                    
2009/09/15 21:01:12 :: Releasing DHCP leases...                                                  
2009/09/15 21:01:12 :: Setting false IP...                                                       
2009/09/15 21:01:12 :: Flushing the routing table...                                             
2009/09/15 21:01:12 :: Putting interface up...                                                   
2009/09/15 21:01:12 :: Running DHCP                                                              
2009/09/15 21:01:12 :: dhcpcd: version 5.0.7 starting                                            
2009/09/15 21:01:12 ::
2009/09/15 21:01:12 :: dhcpcd: eth0: rebinding lease of 192.168.0.194
2009/09/15 21:01:12 ::
2009/09/15 21:01:22 :: dhcpcd: eth0: broadcasting for a lease
2009/09/15 21:01:22 ::
2009/09/15 21:01:23 :: dhcpcd: eth0: offered 172.16.1.196 from 172.16.1.254
2009/09/15 21:01:23 ::
2009/09/15 21:01:23 :: dhcpcd: eth0: acknowledged 172.16.1.196 from 172.16.1.254
2009/09/15 21:01:23 ::
2009/09/15 21:01:23 :: dhcpcd: eth0: checking for 172.16.1.196
2009/09/15 21:01:23 ::
2009/09/15 21:01:23 :: dhcpcd: eth0: hardware address 00:00:5a:72:ef:5f claims 172.16.1.196
2009/09/15 21:01:23 ::
2009/09/15 21:01:23 :: dhcpcd: eth0: send_raw_packet: Bad file descriptor
2009/09/15 21:01:23 ::
2009/09/15 21:01:33 :: dhcpcd: eth0: rebinding lease of 192.168.0.194
2009/09/15 21:01:33 ::
2009/09/15 21:01:42 :: dhcpcd: timed out
2009/09/15 21:01:42 ::
2009/09/15 21:01:42 :: DHCP connection failed
2009/09/15 21:01:42 :: exiting connection thread
2009/09/15 21:01:42 :: Sending connection attempt result dhcp_failed

I also tried to disable wicd and bring back the network daemon up, but I couldn't connect this way either. Any clues?

Thanks a lot!

leandroaveiro · 2009-09-16 22:19:29

I got the log from /var/log/everything... Here's what happens the I select the wired network on Wicd:

Sep 16 21:12:27 leandro dhcpcd: dhcpcd not running
Sep 16 21:12:28 leandro kernel: input: b43-phy0 as /devices/virtual/input/input14
Sep 16 21:12:28 leandro kernel: b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
Sep 16 21:12:28 leandro kernel: Registered led device: b43-phy0::radio
Sep 16 21:12:28 leandro kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep 16 21:12:28 leandro dhcpcd: dhcpcd not running
Sep 16 21:12:28 leandro kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
Sep 16 21:12:28 leandro dhcpcd: version 5.0.7 starting
Sep 16 21:12:28 leandro dhcpcd: eth0: rebinding lease of 192.168.0.194
Sep 16 21:12:38 leandro dhcpcd: eth0: broadcasting for a lease
Sep 16 21:12:38 leandro dhcpcd: eth0: offered 172.16.1.196 from 172.16.1.254
Sep 16 21:12:38 leandro dhcpcd: eth0: acknowledged 172.16.1.196 from 172.16.1.254
Sep 16 21:12:38 leandro dhcpcd: eth0: checking for 172.16.1.196
Sep 16 21:12:39 leandro dhcpcd: eth0: hardware address 00:00:5a:72:ef:5f claims 172.16.1.196
Sep 16 21:12:39 leandro dhcpcd: eth0: send_raw_packet: Bad file descriptor
Sep 16 21:12:39 leandro kernel: eth0: no IPv6 routers present
Sep 16 21:12:49 leandro dhcpcd: eth0: rebinding lease of 192.168.0.194
Sep 16 21:12:58 leandro dhcpcd: timed out

Appreciate any help! I don't think this is a common problem because Google desn't return many results on "dhcpcd" and "bad file descriptor".

Thanks!

leandroaveiro · 2009-09-20 20:54:19

I still don't know why dhcpcd gives this message, but I installed dhclient from the Download area of Arch website and added

dhclient eth0"

to the end of boot and the network is up again.

linfan · 2009-10-13 09:40:50

I keep getting the same error at work and it almost drives me crazy - I am inclined to think there is something wrong in the network. Funny, though, the mac laptops work with our routers, but for linux and netcfg it just keeps bugging with its dhcpcd: wlan0: send_raw_packets: Bad file descriptor...

As I run my private linux laptop the system admins don't give a shit about my problems. I hope, though, that there was some error msg or any todos.

kjon · 2009-10-13 10:46:23

when dhcpcd starts spitting crap (like dhclient), I preffer to use pump. It's on aur.

vacant · 2009-10-13 11:42:36

leandroaveiro wrote:

Sep 16 21:12:38 leandro dhcpcd: eth0: broadcasting for a lease
Sep 16 21:12:38 leandro dhcpcd: eth0: offered 172.16.1.196 from 172.16.1.254
Sep 16 21:12:38 leandro dhcpcd: eth0: acknowledged 172.16.1.196 from 172.16.1.254
Sep 16 21:12:38 leandro dhcpcd: eth0: checking for 172.16.1.196
Sep 16 21:12:39 leandro dhcpcd: eth0: hardware address 00:00:5a:72:ef:5f claims 172.16.1.196
Sep 16 21:12:39 leandro dhcpcd: eth0: send_raw_packet: Bad file descriptor

check the MAC of your NIC using ifconfig, is it 00:00:5a:72:ef:5f?

Arch Linux

#1 2009-09-15 22:14:55

Can't connect on wired network - Bad file descriptor

#2 2009-09-16 22:19:29

Re: Can't connect on wired network - Bad file descriptor

#3 2009-09-20 20:54:19

Re: Can't connect on wired network - Bad file descriptor

#4 2009-10-13 09:40:50

Re: Can't connect on wired network - Bad file descriptor

#5 2009-10-13 10:46:23

Re: Can't connect on wired network - Bad file descriptor

#6 2009-10-13 11:42:36

Re: Can't connect on wired network - Bad file descriptor

Board footer