Re: dhclient or network problem
On Mon, Jul 10, 2017 at 12:55:53PM +0200, Dejan Jocic wrote:
> On 10-07-17, Franz Angeli wrote:
> > Hi,
> >
> > i have a problem with dhclient:
> >
> > for example interface name eno52 (tg3, Broadcom Limited NetXtreme
> > BCM5719 Gigabit Ethernet PCIe (rev 01) :
> >
> > root@********:~# dhclient eno52 -v
> > Internet Systems Consortium DHCP Client 4.3.5
> > Copyright 2004-2016 Internet Systems Consortium.
> > All rights reserved.
> > For info, please visit https://www.isc.org/software/dhcp/
> >
> > Listening on LPF/eno52/3c:a8:2a:e7:87:bf
> > Sending on LPF/eno52/3c:a8:2a:e7:87:bf
> > Sending on Socket/fallback
> > DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 4
> > DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 10
> > DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 7
> > DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 9
> > DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 15
> > DHCPDISCOVER on eno52 to 255.255.255.255 port 67 interval 16
> > No DHCPOFFERS received.
> > No working leases in persistent database - sleeping.
> >
> > tcpdump during dhclient doesn't show anything?!?
> >
> > root@*********:~# tcpdump -i eno52
> > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> > listening on eno52, link-type EN10MB (Ethernet), capture size 262144 bytes
> >
> >
> > root@*******:~# ip addr show eno52
> > 9: eno52: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state
> > DOWN group default qlen 1000
> > link/ether 3c:a8:2a:e7:87:bf brd ff:ff:ff:ff:ff:ff
> >
> >
> > if i use the same ethernet cable on my laptop all works fine...
>
> Don't you think that you have enough of a clue there :P That eno52 is,
> as you can see ethernet card, of course it will work when you connect it
> with ethernet cable. If you want it to work with wifi, that is another
> story. What is your wifi card, do you have something starting with w in
> the output of ip addr show? What is the output of the lspci -v | grep -i
> -A6 net?
> >
Uh, no mate, I don't think that is what the OP meant. I suspect the
laptop is a different computer. And telling us the cable works in his
laptop is designed to head off suggestions the cable might be at fault.
He never mentiond WiFi anywhere.
Mark
Reply to: