From: Peter B. <pe...@pu...> - 2008-03-17 20:08:05
|
The error just means udhcpc wasn't running when you did the ifdown command. One interesting thing to note here is that the link is up but half duplex according to udhcpc. I'll wager that your environment doesn't have a half duplex 100 mbit network running. I wonder if there is a negotiation issue on the Ethernet layer that is causing the device to not be compatible with your work network. In the past, I've seen a lot of problems using Ethernet devices that couldn't auto negotiate correctly and would then not be able to TX or RX without errors or at all. I also find it odd that you have as many bytes received without an IP address. I think that means the device is hearing some intermediate device chattering at it a lot. Possibly related to link negotiation issues. If you can get tcpdump, that would give you some idea as to what is making all that noise. m_a...@co... wrote: > Hi, > > nope - we have both statically assigned dhcp and dynamic. I have brought my mac laptop in before and gotten it to work on this lan. > > When I do the ifdown eth0 > > all I get back is: > > cat: /var/run/udhcpc.eth0.pid: No such file or directory > > when I do the ifup eth0 it prints: > > eth0: link down > > udhcpc (v1.2.1) started > Sending discover... > eth0: link up, 100Mbps, half-duplex,... > sending discover... > sending discover... > no lease, failing > > so will double check about dhcp addresses being dolled out here at work... > > 'mark > > -------------- Original message ---------------------- > From: Lawrence Harris <gumstix@HariTech.com> > >> Just a thought but does your office network hand out IP's based on MAC >> maybe? You can have DHCP but still restricted so that people can't put >> random machines on the network. I don't think the gumstix does anything >> special - you could do ifdown/ifup eth0 and see if that does anything. >> >> Lawrence >> >> m_a...@co... wrote: >> >>> Hi, >>> >>> I have a verdex XL6p with a netwifimicro sd card. This was working fine when >>> >> at home and there my ethernet is just wired to a NAT firewall router. So things >> like ipkg update worked great from the gumstix. >> >>> Today I brought it into work, and there it sits behind a proxy firewall. The >>> >> problem is that I can't even get the gumstix to obtain a DHCP address. I have >> made sure the port and cable are working, but am starting to wonder if when it >> was first brought up at home, if there was some gateway address which it stored >> in flash so that when I put it onto a new LAN (no longer 192.168....), it would >> not work. >> >>> doing a ifconfig shows that eth0 is up, but it does not have an assigned dhcp >>> >> address. So things like ping to known IP addresses does not work. >> >>> eth0 Link encap:Ethernet HWaddr DE:14:4E:AB:55:50 >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>> RX packets:1981 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:1000 >>> RX bytes:455913 (445.2 KiB) TX bytes:1180 (1.1 KiB) >>> Interrupt:131 DMA chan:ff >>> >>> Any ideas? >>> >>> thanks! >>> >>> 'mark >>> >>> -- Pete Funny=Truth Truth=Beauty So take it as a complement when people say you look Funny. |