You are not logged in.

#1 2013-10-22 01:47:29

/dev/zero
Member
From: Melbourne, Australia
Registered: 2011-10-20
Posts: 1,176
Website

[Pseudosolved] DHCP Timeouts: Driver or Config Problem?

I have set up Archlinux on my (university-owned) desktop PC. It can connect to the LAN by static IP but my sysadmin says I have to connect by DHCP, the lease for the "static" IP I've been using will expire soon. However, both dhcpcd and dhclient keep timing out.

I don't want to pester the IT people too much because they nominally don't support Archlinux. I had to argue my case strongly for not using RHEL. They only let me use Archlinux because I said I'm an advanced user and I'm not going to need support. I don't want to have to eat my words too much smile. I've written an email to the IT dept anyway, asking if the dhcp server has any weird settings I should know about when configuring my client.

At first I thought there was a bug in my ethernet card driver (e1000e); see for example https://bugs.launchpad.net/ubuntu/+sour … bug/382671 - but when I try a different card (with driver alx) the result is still the same. Furthermore, the PC originally had RHEL installed and was connected using Network Manager - that's where I stole the address from to use as static wink. But now I've overwritten RHEL completely so there won't be any more config-theft from that department.

While stfwing for a solution, I noted the following forum threads:

but all of them (even the one that says "Solved") came to the non-solution that it's all because of an upstream bug. On the other hand, none of them mentioned trying more than one ethernet card - and furthermore, apparently, even with this bug, it is possible to work around it by doing combinations of unplugging/replugging the ethernet cable, rmmodding/remodprobing e1000e, and putting the interface down and up with "ip link". None of these workarounds have worked for me. I've also tried different versions of the e1000e module, such as by getting dkms-e1000e from AUR and manually changing the version to 2.5.4, with various options for that driver set in the modprobe config, most recently:

# /etc/modprobe.d/ethernet.conf
# Based on information from:
#  - askubuntu.com/questions/224403/frequent-disconnects-ubuntu-desktop-12-10-x64-intel-82579v-e1000e
#  - downloadmirror.intel.com/15817/eng/README.txt
options e1000e IntMode=1,1
options e1000e InterruptThrottleRate=3000,3000,3000
options e1000e RxIntDelay=0
options e1000e SmartPowerDownEnable=0
options e1000e EEE=0

All this suggests to me that maybe it's not anything to do with my drivers, and my question now more or less boils down to, is this more likely a config problem that can be fixed by changing my dhcp client settings, or is it more likely that the two different cards I've tried both have buggy drivers?

My dhcpcd.conf:

# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Inform the DHCP server of our hostname for DDNS.
hostname

# Use the hardware address of the interface for the Client ID.
clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
#duid

# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
#option ntp_servers
# Respect the network MTU.
# Some interface drivers reset when changing the MTU so disabled by default.
#option interface_mtu

# A ServerID is required by RFC2131.
require dhcp_server_identifier

# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
#nohook lookup-hostname
noipv4ll
noipv6rs

# Don't touch resolv.conf settings.
nohook resolv.conf

My output from dhcpcd:

# dhcpcd -d eno1
dhcpcd[660]: version 6.0.5 starting
dhcpcd[660]: eno1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
dhcpcd[660]: eno1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' CARRIER
dhcpcd[660]: eno1: using ClientID 01:b8:ca:3a:b3:54:af
dhcpcd[660]: eno1: soliciting a DHCP lease
dhcpcd[660]: eno1: sending DISCOVER (xid 0x4ad8bcfb), next in 3.90 seconds
dhcpcd[660]: eno1: sending DISCOVER (xid 0x4ad8bcfb), next in 8.55 seconds
dhcpcd[660]: eno1: sending DISCOVER (xid 0x4ad8bcfb), next in 16.28 seconds
dhcpcd[660]: eno1: sending DISCOVER (xid 0x4ad8bcfb), next in 32.88 seconds
dhcpcd[660]: timed out
dhcpcd[660]: exited

Info from various other commands follows.

$ lspci -nnvk | grep -A10 -i net
00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I217-LM [8086:153a] (rev 04)
	Subsystem: Dell Device [1028:05a4]
	Flags: bus master, fast devsel, latency 0, IRQ 47
	Memory at f7f00000 (32-bit, non-prefetchable) [size=128K]
	Memory at f7f39000 (32-bit, non-prefetchable) [size=4K]
	I/O ports at f040 [size=32]
	Capabilities: <access denied>
	Kernel driver in use: e1000e
	Kernel modules: e1000e
$ modinfo e1000e
filename:       /lib/modules/3.11.6-1-ARCH/updates/e1000e.ko
version:        2.5.4-NAPI
license:        GPL
description:    Intel(R) PRO/1000 Network Driver
author:         Intel Corporation, <linux.nics@intel.com>
srcversion:     14FC0D45EE1DAA1B5E0DBBA
alias:          pci:v00008086d000015A3sv*sd*bc*sc*i*
alias:          pci:v00008086d000015A2sv*sd*bc*sc*i*
alias:          pci:v00008086d000015A1sv*sd*bc*sc*i*
alias:          pci:v00008086d000015A0sv*sd*bc*sc*i*
alias:          pci:v00008086d00001559sv*sd*bc*sc*i*
alias:          pci:v00008086d0000155Asv*sd*bc*sc*i*
alias:          pci:v00008086d0000153Bsv*sd*bc*sc*i*
alias:          pci:v00008086d0000153Asv*sd*bc*sc*i*
alias:          pci:v00008086d00001503sv*sd*bc*sc*i*
alias:          pci:v00008086d00001502sv*sd*bc*sc*i*
alias:          pci:v00008086d000010F0sv*sd*bc*sc*i*
alias:          pci:v00008086d000010EFsv*sd*bc*sc*i*
alias:          pci:v00008086d000010EBsv*sd*bc*sc*i*
alias:          pci:v00008086d000010EAsv*sd*bc*sc*i*
alias:          pci:v00008086d00001525sv*sd*bc*sc*i*
alias:          pci:v00008086d000010DFsv*sd*bc*sc*i*
alias:          pci:v00008086d000010DEsv*sd*bc*sc*i*
alias:          pci:v00008086d000010CEsv*sd*bc*sc*i*
alias:          pci:v00008086d000010CDsv*sd*bc*sc*i*
alias:          pci:v00008086d000010CCsv*sd*bc*sc*i*
alias:          pci:v00008086d000010CBsv*sd*bc*sc*i*
alias:          pci:v00008086d000010F5sv*sd*bc*sc*i*
alias:          pci:v00008086d000010BFsv*sd*bc*sc*i*
alias:          pci:v00008086d000010E5sv*sd*bc*sc*i*
alias:          pci:v00008086d0000294Csv*sd*bc*sc*i*
alias:          pci:v00008086d000010BDsv*sd*bc*sc*i*
alias:          pci:v00008086d000010C3sv*sd*bc*sc*i*
alias:          pci:v00008086d000010C2sv*sd*bc*sc*i*
alias:          pci:v00008086d000010C0sv*sd*bc*sc*i*
alias:          pci:v00008086d00001501sv*sd*bc*sc*i*
alias:          pci:v00008086d00001049sv*sd*bc*sc*i*
alias:          pci:v00008086d0000104Dsv*sd*bc*sc*i*
alias:          pci:v00008086d0000104Bsv*sd*bc*sc*i*
alias:          pci:v00008086d0000104Asv*sd*bc*sc*i*
alias:          pci:v00008086d000010C4sv*sd*bc*sc*i*
alias:          pci:v00008086d000010C5sv*sd*bc*sc*i*
alias:          pci:v00008086d0000104Csv*sd*bc*sc*i*
alias:          pci:v00008086d000010BBsv*sd*bc*sc*i*
alias:          pci:v00008086d00001098sv*sd*bc*sc*i*
alias:          pci:v00008086d000010BAsv*sd*bc*sc*i*
alias:          pci:v00008086d00001096sv*sd*bc*sc*i*
alias:          pci:v00008086d0000150Csv*sd*bc*sc*i*
alias:          pci:v00008086d000010F6sv*sd*bc*sc*i*
alias:          pci:v00008086d000010D3sv*sd*bc*sc*i*
alias:          pci:v00008086d0000109Asv*sd*bc*sc*i*
alias:          pci:v00008086d0000108Csv*sd*bc*sc*i*
alias:          pci:v00008086d0000108Bsv*sd*bc*sc*i*
alias:          pci:v00008086d0000107Fsv*sd*bc*sc*i*
alias:          pci:v00008086d0000107Esv*sd*bc*sc*i*
alias:          pci:v00008086d0000107Dsv*sd*bc*sc*i*
alias:          pci:v00008086d000010B9sv*sd*bc*sc*i*
alias:          pci:v00008086d000010D5sv*sd*bc*sc*i*
alias:          pci:v00008086d000010DAsv*sd*bc*sc*i*
alias:          pci:v00008086d000010D9sv*sd*bc*sc*i*
alias:          pci:v00008086d00001060sv*sd*bc*sc*i*
alias:          pci:v00008086d000010A5sv*sd*bc*sc*i*
alias:          pci:v00008086d000010BCsv*sd*bc*sc*i*
alias:          pci:v00008086d000010A4sv*sd*bc*sc*i*
alias:          pci:v00008086d0000105Fsv*sd*bc*sc*i*
alias:          pci:v00008086d0000105Esv*sd*bc*sc*i*
depends:       =20
vermagic:       3.11.6-1-ARCH SMP preempt mod_unload modversions=20
parm:           copybreak:Maximum size of packet that is copied to a new bu=
ffer on receive (uint)
parm:           TxIntDelay:Transmit Interrupt Delay (array of int)
parm:           TxAbsIntDelay:Transmit Absolute Interrupt Delay (array of i=
nt)
parm:           RxIntDelay:Receive Interrupt Delay (array of int)
parm:           RxAbsIntDelay:Receive Absolute Interrupt Delay (array of in=
t)
parm:           InterruptThrottleRate:Interrupt Throttling Rate (array of i=
nt)
parm:           IntMode:Interrupt Mode (array of int)
parm:           SmartPowerDownEnable:Enable PHY smart power down (array of =
int)
parm:           KumeranLockLoss:Enable Kumeran lock loss workaround (array =
of int)
parm:           CrcStripping:Enable CRC Stripping, disable if your BMC need=
s the CRC (array of int)
parm:           EEE:Enable/disable on parts that support the feature (array=
 of int)
parm:           Node:[ROUTING] Node to allocate memory on, default -1 (arra=
y of int)
parm:           debug:Debug level (0=3Dnone,...,16=3Dall) (int)
$ uname -a
Linux pc2517 3.11.6-1-ARCH #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013 x86_64 GNU/Linux
$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DE=
FAULT=20
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state =
UP mode DEFAULT qlen 1000
    link/ether b8:ca:3a:b3:54:af brd ff:ff:ff:ff:ff:ff
$ ifconfig eno1
eno1: flags=3D4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 128.250.24.134  netmask 255.255.255.0  broadcast 0.0.0.0
        inet6 fe80::baca:3aff:feb3:54af  prefixlen 64  scopeid 0x20<link>
        ether b8:ca:3a:b3:54:af  txqueuelen 1000  (Ethernet)
        RX packets 35313  bytes 10688467 (10.1 MiB)
        RX errors 0  dropped 2  overruns 0  frame 0
        TX packets 3652  bytes 553429 (540.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xf7f00000-f7f20000 =20

I've put a pastebin of output from

# tcpdump -i eno1

here.

In the tcpdump, if you grep for lines containing "BOOTP/DHCP", you can see my card (with MAC address b8:ca:3a:b3:54:af) requesting an IP lease but not receiving any reply.

Finally, the lspci info from the second network card I tried:

$ lspci -nnvk | grep -A8 -i ethernet
09:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit Ethernet [1969:10a1] (rev 10)
        Subsystem: Toshiba America Info Systems Device [1179:fa40]
        Flags: bus master, fast devsel, latency 0, IRQ 18
        Memory at d1000000 (64-bit, non-prefetchable) [size=256K]
        I/O ports at 2000 [size=128]
        Capabilities: <access denied>
        Kernel driver in use: alx
        Kernel modules: alx

It occurred to me that the DHCP server might be configured to only accept certain MAC addresses, but it was trivial for me to spoof the university computer's MAC using instructions from the wiki. I.e. when I tried using the other card, it requested a lease using the same ClientID.

Please let me know if more information is needed. Thank you for your attention.

Last edited by /dev/zero (2013-10-24 02:58:52)


Linux is NOT Windows | The Rootless Root
Toshiba Satellite i5-3230M 2.6GHz CPUs, 4Gb RAM, ArchLinux, wmii, nVidia GeForce GT 740M.

Offline

#2 2013-10-22 02:40:30

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 12,969

Re: [Pseudosolved] DHCP Timeouts: Driver or Config Problem?

I started to wade through that tcpdump, then I lost my will sad

So, let me fall back on the seat-of-the-pants approach. 

I have no evidence this will help, but have you tried disabling IPv6 ?
Also, are you running a firewall?  Is it set to permit inbound DHCP packets?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Like you, I have no idea what you are doing, but I am pretty sure it is wrong...Jasonwryan
----
How to Ask Questions the Smart Way

Online

#3 2013-10-22 02:47:00

/dev/zero
Member
From: Melbourne, Australia
Registered: 2011-10-20
Posts: 1,176
Website

Re: [Pseudosolved] DHCP Timeouts: Driver or Config Problem?

ewaller wrote:

I have no evidence this will help, but have you tried disabling IPv6 ?
Also, are you running a firewall?  Is it set to permit inbound DHCP packets?

Sorry, I forgot to mention, I considered both of these aspects. I've tried connecting with IPv6 both enabled and disabled, both using commandline flags to both clients and also by setting kernel parameters at boot. I've set up a Simple Stateful Firewall and the problem does not vary, whether the iptables service is running or not.

PS: I also reproduced the problem when booting from the 2013-10 Archlinux CD with no firewall configured at all.

Last edited by /dev/zero (2013-10-22 02:49:19)


Linux is NOT Windows | The Rootless Root
Toshiba Satellite i5-3230M 2.6GHz CPUs, 4Gb RAM, ArchLinux, wmii, nVidia GeForce GT 740M.

Offline

#4 2013-10-22 03:35:24

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 12,969

Re: [Pseudosolved] DHCP Timeouts: Driver or Config Problem?

And no local router or switch.  You are plugged straight into the campus router, yes?

You mentioned another card, and that you spoofed its MAC.  Is that other card in another computer? Does that computer connect using DHCP?
When you spoofed its MAC, you could not discover a server, correct?

What if you clear your static address before trying DHCP?
Is 128.250.24.134 real?  That seems like a weird address.   128 == 0x80 == 0b1000.0000   Something smells odd there.
Is this a private address space, or is your machine routeable from the Internet?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Like you, I have no idea what you are doing, but I am pretty sure it is wrong...Jasonwryan
----
How to Ask Questions the Smart Way

Online

#5 2013-10-22 04:31:37

/dev/zero
Member
From: Melbourne, Australia
Registered: 2011-10-20
Posts: 1,176
Website

Re: [Pseudosolved] DHCP Timeouts: Driver or Config Problem?

ewaller wrote:

And no local router or switch.  You are plugged straight into the campus router, yes?

How would I be able to tell the difference? The ethernet cable disappears under my desk and from there disappears into a wall. Traceroute? - but I'm not sure which flags would be optimal or how to interpret the results.


ewaller wrote:

You mentioned another card, and that you spoofed its MAC.  Is that other card in another computer? Does that computer connect using DHCP?
When you spoofed its MAC, you could not discover a server, correct?

Correct. The second card is in my laptop. Normally my laptop connects fine by dhcp, albeit through wifi - this is the first time I've tried my laptop on ethernet.

When I spoofed the MAC, I got exactly the same output using DHCP as when I tried on the desktop. The laptop was able to connect statically, just like the desktop.


ewaller wrote:

What if you clear your static address before trying DHCP?

Yep, still the same.


ewaller wrote:

Is 128.250.24.134 real?  That seems like a weird address.   128 == 0x80 == 0b1000.0000   Something smells odd there.
Is this a private address space, or is your machine routeable from the Internet?

I think routeable from the internet? Via my 3G device (therefore no university networks involved), I can do the following on my laptop:

$ host 128.250.24.134
134.24.250.128.in-addr.arpa domain name pointer pc1877.ms.unimelb.edu.au.

All Melbourne University systems seem to run in the 128.250.*.* space.


Linux is NOT Windows | The Rootless Root
Toshiba Satellite i5-3230M 2.6GHz CPUs, 4Gb RAM, ArchLinux, wmii, nVidia GeForce GT 740M.

Offline

#6 2013-10-22 04:35:02

/dev/zero
Member
From: Melbourne, Australia
Registered: 2011-10-20
Posts: 1,176
Website

Re: [Pseudosolved] DHCP Timeouts: Driver or Config Problem?

The plot thickens. I just got an email from my sysadmin:

/dev/zero's sysadmin wrote:

The dhcp server log has many "DHCP DISCOVER" from you:

Oct 22 06:25:06 xxxxx bootpd[6974]: DHCP DISCOVER [en1]: 1,b8:ca:3a:b3:54:af
Oct 22 06:25:06 xxxxx bootpd[6974]: DHCP DISCOVER [en0]: 1,b8:ca:3a:b3:54:af
Oct 22 06:25:41 xxxxx bootpd[6974]: DHCP DISCOVER [en0]: 1,b8:ca:3a:b3:54:af
Oct 22 06:25:41 xxxxx bootpd[6974]: DHCP DISCOVER [en1]: 1,b8:ca:3a:b3:54:af
Oct 22 06:25:46 xxxxx bootpd[6974]: DHCP DISCOVER [en0]: 1,b8:ca:3a:b3:54:af
:

but no "DHCP REQUEST".


Linux is NOT Windows | The Rootless Root
Toshiba Satellite i5-3230M 2.6GHz CPUs, 4Gb RAM, ArchLinux, wmii, nVidia GeForce GT 740M.

Offline

#7 2013-10-22 05:14:38

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 12,969

Re: [Pseudosolved] DHCP Timeouts: Driver or Config Problem?

On my machine:

ewaller$@$odin ~ 1001 %host 192.168.1.2
2.1.168.192.in-addr.arpa domain name pointer odin-wireless.
ewaller$@$odin ~ 1002 %

odin-wireless is the dhcphostname being passed into dhcpcd by wicd.   Your dhcpchostname is pc1877.ms.unimelb.edu.au 
Where did that come from?  Was it assigned to you?
If so, where do you set it?  Is it in /etc/dhcpd.conf?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Like you, I have no idea what you are doing, but I am pretty sure it is wrong...Jasonwryan
----
How to Ask Questions the Smart Way

Online

#8 2013-10-22 05:23:24

/dev/zero
Member
From: Melbourne, Australia
Registered: 2011-10-20
Posts: 1,176
Website

Re: [Pseudosolved] DHCP Timeouts: Driver or Config Problem?

ewaller wrote:

Your dhcpchostname is pc1877.ms.unimelb.edu.au 
Where did that come from?  Was it assigned to you?
If so, where do you set it?  Is it in /etc/dhcpd.conf?

No, it appeared out of nowhere as far as I know. I think assigned by the same dhcp server that I'm trying to connect to? When I first received the desktop box, the hostname in it was pc2517.ms.etc; this pc1877 is news to me.

NB: I reused the same hostname pc2517.etc when installing Archlinux. Now I've changed it to pc1877.etc but no results have changed.

Last edited by /dev/zero (2013-10-22 05:49:22)


Linux is NOT Windows | The Rootless Root
Toshiba Satellite i5-3230M 2.6GHz CPUs, 4Gb RAM, ArchLinux, wmii, nVidia GeForce GT 740M.

Offline

#9 2013-10-22 06:05:19

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 12,969

Re: [Pseudosolved] DHCP Timeouts: Driver or Config Problem?

Well, this is interesting.  I tried the host command on the address and *poof* I got pc1877.ms.unimelb.edu.au  also. 
Attempts to resolve pc2517.ms.unimelb.edu.au to an address indicate there is no address with that host name.

I don't know what this all means.  But, I think your IP department advertises pc1877 to the world with a link to the IP you are using.
Mayhap try setting your dhcphostname to pc1877 and see if anything interesting happens.

Edit:  I will pick this back up again in the morning.

Last edited by ewaller (2013-10-22 06:06:03)


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Like you, I have no idea what you are doing, but I am pretty sure it is wrong...Jasonwryan
----
How to Ask Questions the Smart Way

Online

#10 2013-10-22 06:08:18

/dev/zero
Member
From: Melbourne, Australia
Registered: 2011-10-20
Posts: 1,176
Website

Re: [Pseudosolved] DHCP Timeouts: Driver or Config Problem?

ewaller wrote:

Edit:  I will pick this back up again in the morning.

Ditto smile And thanks for your time.


Linux is NOT Windows | The Rootless Root
Toshiba Satellite i5-3230M 2.6GHz CPUs, 4Gb RAM, ArchLinux, wmii, nVidia GeForce GT 740M.

Offline

#11 2013-10-22 21:22:15

/dev/zero
Member
From: Melbourne, Australia
Registered: 2011-10-20
Posts: 1,176
Website

Re: [Pseudosolved] DHCP Timeouts: Driver or Config Problem?

I just tried tcpdump with a few different flags and the result seems a bit more readable.

# sudo tcpdump -vlenxx -i eno1 -s 1500 port bootps or port bootpc
tcpdump: WARNING: eno1: no IPv4 address assigned
tcpdump: listening on eno1, link-type EN10MB (Ethernet), capture size 1500 bytes
08:07:19.701212 b8:ca:3a:b3:54:af > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 378: (tos 0x0, ttl 64, id 49162, offset 0, flags [none], proto UDP (17), length 364)
    0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from b8:ca:3a:b3:54:af, length 336, xid 0x364612f2, Flags [none]
	  Client-Ethernet-Address b8:ca:3a:b3:54:af
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Discover
	    Client-ID Option 61, length 7: ether b8:ca:3a:b3:54:af
	    SLP-NA Option 80, length 0""
	    MSZ Option 57, length 2: 1500
	    Vendor-Class Option 60, length 52: "dhcpcd-6.0.5:Linux-3.11.6-1-ARCH:x86_64:GenuineIntel"
	    Hostname Option 12, length 6: "pc2517"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, Classless-Static-Route, Static-Route, Default-Gateway
	      Domain-Name-Server, Hostname, Domain-Name, BR
	      Lease-Time, Server-ID, RN, RB
	      Option 119
	0x0000:  ffff ffff ffff b8ca 3ab3 54af 0800 4500
	0x0010:  016c c00a 0000 4011 b977 0000 0000 ffff
	0x0020:  ffff 0044 0043 0158 83ce 0101 0600 3646
	0x0030:  12f2 0000 0000 0000 0000 0000 0000 0000
	0x0040:  0000 0000 0000 b8ca 3ab3 54af 0000 0000
	0x0050:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0060:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0070:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0080:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0090:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00a0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00b0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00c0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00d0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00e0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00f0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0100:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0110:  0000 0000 0000 6382 5363 3501 013d 0701
	0x0120:  b8ca 3ab3 54af 5000 3902 05dc 3c34 6468
	0x0130:  6370 6364 2d36 2e30 2e35 3a4c 696e 7578
	0x0140:  2d33 2e31 312e 362d 312d 4152 4348 3a78
	0x0150:  3836 5f36 343a 4765 6e75 696e 6549 6e74
	0x0160:  656c 0c06 7063 3235 3137 370d 0179 2103
	0x0170:  060c 0f1c 3336 3a3b 77ff
08:07:24.012710 b8:ca:3a:b3:54:af > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 378: (tos 0x0, ttl 64, id 27750, offset 0, flags [none], proto UDP (17), length 364)
    0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from b8:ca:3a:b3:54:af, length 336, xid 0x364612f2, secs 5, Flags [none]
	  Client-Ethernet-Address b8:ca:3a:b3:54:af
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Discover
	    Client-ID Option 61, length 7: ether b8:ca:3a:b3:54:af
	    SLP-NA Option 80, length 0""
	    MSZ Option 57, length 2: 1500
	    Vendor-Class Option 60, length 52: "dhcpcd-6.0.5:Linux-3.11.6-1-ARCH:x86_64:GenuineIntel"
	    Hostname Option 12, length 6: "pc2517"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, Classless-Static-Route, Static-Route, Default-Gateway
	      Domain-Name-Server, Hostname, Domain-Name, BR
	      Lease-Time, Server-ID, RN, RB
	      Option 119
	0x0000:  ffff ffff ffff b8ca 3ab3 54af 0800 4500
	0x0010:  016c 6c66 0000 4011 0d1c 0000 0000 ffff
	0x0020:  ffff 0044 0043 0158 83c9 0101 0600 3646
	0x0030:  12f2 0005 0000 0000 0000 0000 0000 0000
	0x0040:  0000 0000 0000 b8ca 3ab3 54af 0000 0000
	0x0050:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0060:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0070:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0080:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0090:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00a0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00b0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00c0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00d0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00e0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00f0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0100:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0110:  0000 0000 0000 6382 5363 3501 013d 0701
	0x0120:  b8ca 3ab3 54af 5000 3902 05dc 3c34 6468
	0x0130:  6370 6364 2d36 2e30 2e35 3a4c 696e 7578
	0x0140:  2d33 2e31 312e 362d 312d 4152 4348 3a78
	0x0150:  3836 5f36 343a 4765 6e75 696e 6549 6e74
	0x0160:  656c 0c06 7063 3235 3137 370d 0179 2103
	0x0170:  060c 0f1c 3336 3a3b 77ff
08:07:31.512797 b8:ca:3a:b3:54:af > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 378: (tos 0x0, ttl 64, id 51047, offset 0, flags [none], proto UDP (17), length 364)
    0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from b8:ca:3a:b3:54:af, length 336, xid 0x364612f2, secs 12, Flags [none]
	  Client-Ethernet-Address b8:ca:3a:b3:54:af
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Discover
	    Client-ID Option 61, length 7: ether b8:ca:3a:b3:54:af
	    SLP-NA Option 80, length 0""
	    MSZ Option 57, length 2: 1500
	    Vendor-Class Option 60, length 52: "dhcpcd-6.0.5:Linux-3.11.6-1-ARCH:x86_64:GenuineIntel"
	    Hostname Option 12, length 6: "pc2517"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, Classless-Static-Route, Static-Route, Default-Gateway
	      Domain-Name-Server, Hostname, Domain-Name, BR
	      Lease-Time, Server-ID, RN, RB
	      Option 119
	0x0000:  ffff ffff ffff b8ca 3ab3 54af 0800 4500
	0x0010:  016c c767 0000 4011 b21a 0000 0000 ffff
	0x0020:  ffff 0044 0043 0158 83c2 0101 0600 3646
	0x0030:  12f2 000c 0000 0000 0000 0000 0000 0000
	0x0040:  0000 0000 0000 b8ca 3ab3 54af 0000 0000
	0x0050:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0060:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0070:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0080:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0090:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00a0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00b0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00c0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00d0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00e0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00f0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0100:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0110:  0000 0000 0000 6382 5363 3501 013d 0701
	0x0120:  b8ca 3ab3 54af 5000 3902 05dc 3c34 6468
	0x0130:  6370 6364 2d36 2e30 2e35 3a4c 696e 7578
	0x0140:  2d33 2e31 312e 362d 312d 4152 4348 3a78
	0x0150:  3836 5f36 343a 4765 6e75 696e 6549 6e74
	0x0160:  656c 0c06 7063 3235 3137 370d 0179 2103
	0x0170:  060c 0f1c 3336 3a3b 77ff
08:07:48.337853 b8:ca:3a:b3:54:af > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 378: (tos 0x0, ttl 64, id 20817, offset 0, flags [none], proto UDP (17), length 364)
    0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from b8:ca:3a:b3:54:af, length 336, xid 0x364612f2, secs 29, Flags [none]
	  Client-Ethernet-Address b8:ca:3a:b3:54:af
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Discover
	    Client-ID Option 61, length 7: ether b8:ca:3a:b3:54:af
	    SLP-NA Option 80, length 0""
	    MSZ Option 57, length 2: 1500
	    Vendor-Class Option 60, length 52: "dhcpcd-6.0.5:Linux-3.11.6-1-ARCH:x86_64:GenuineIntel"
	    Hostname Option 12, length 6: "pc2517"
	    Parameter-Request Option 55, length 13: 
	      Subnet-Mask, Classless-Static-Route, Static-Route, Default-Gateway
	      Domain-Name-Server, Hostname, Domain-Name, BR
	      Lease-Time, Server-ID, RN, RB
	      Option 119
	0x0000:  ffff ffff ffff b8ca 3ab3 54af 0800 4500
	0x0010:  016c 5151 0000 4011 2831 0000 0000 ffff
	0x0020:  ffff 0044 0043 0158 83b1 0101 0600 3646
	0x0030:  12f2 001d 0000 0000 0000 0000 0000 0000
	0x0040:  0000 0000 0000 b8ca 3ab3 54af 0000 0000
	0x0050:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0060:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0070:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0080:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0090:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00a0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00b0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00c0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00d0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00e0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x00f0:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0100:  0000 0000 0000 0000 0000 0000 0000 0000
	0x0110:  0000 0000 0000 6382 5363 3501 013d 0701
	0x0120:  b8ca 3ab3 54af 5000 3902 05dc 3c34 6468
	0x0130:  6370 6364 2d36 2e30 2e35 3a4c 696e 7578
	0x0140:  2d33 2e31 312e 362d 312d 4152 4348 3a78
	0x0150:  3836 5f36 343a 4765 6e75 696e 6549 6e74
	0x0160:  656c 0c06 7063 3235 3137 370d 0179 2103
	0x0170:  060c 0f1c 3336 3a3b 77ff

4 packets captured
4 packets received by filter
0 packets dropped by kernel
17 packets dropped by interface

You'll probably notice that the hostname is back to pc2517, but that's only the most recent one I've tried; all the others I've tried (pc{2517,1877}{,.ms.unimelb.edu.au}) give the same results.

It says at the end "17 packets dropped by interface" which probably isn't good news; on the other hand we've already established that DHCP-DISCOVERs are arriving at the server, so something is working.


Linux is NOT Windows | The Rootless Root
Toshiba Satellite i5-3230M 2.6GHz CPUs, 4Gb RAM, ArchLinux, wmii, nVidia GeForce GT 740M.

Offline

#12 2013-10-22 21:47:31

/dev/zero
Member
From: Melbourne, Australia
Registered: 2011-10-20
Posts: 1,176
Website

Re: [Pseudosolved] DHCP Timeouts: Driver or Config Problem?

More information to hand. I just called dhcpcd with the "inform" flag:

# dhcpcd -d -s 128.250.24.134/24 eno1

and it successfully took. I can ping google and everything. However, I'm not sure if this quasi-solution will make my sysadmin happy.


Linux is NOT Windows | The Rootless Root
Toshiba Satellite i5-3230M 2.6GHz CPUs, 4Gb RAM, ArchLinux, wmii, nVidia GeForce GT 740M.

Offline

#13 2013-10-24 02:56:57

/dev/zero
Member
From: Melbourne, Australia
Registered: 2011-10-20
Posts: 1,176
Website

Re: [Pseudosolved] DHCP Timeouts: Driver or Config Problem?

Well, I haven't solved this, except in as much as I've made the problem go away. My sysadmin just sent me this:

/dev/zero's sysadmin wrote:

I tried Ubuntu, RHEL6 and Archlinux on a test machine here, the result:

Ubuntu 12.04:

Oct 24 12:58:28 xxxxx bootpd[10770]: DHCP DISCOVER [en1]:
1,0:21:9b:3b:61:e1 **untu>
Oct 24 12:58:28 xxxxx bootpd[10770]: DHCP DISCOVER [en0]:
1,0:21:9b:3b:61:e1 **untu>
Oct 24 12:58:28 xxxxx bootpd[10770]: OFFER sent pc1877t 172.29.135.204
pktsize 3
31
Oct 24 12:58:28 xxxxx bootpd[10770]: DHCP REQUEST [en1]: 1,0:21:9b:3b:61:e1
**ntu>
Oct 24 12:58:28 xxxxx bootpd[10770]: DHCP REQUEST [en0]: 1,0:21:9b:3b:61:e1
**ntu>
Oct 24 12:58:28 xxxxx bootpd[10770]: ACK sent pc1877t 172.29.135.204
pktsize 331

RHEL6.4:

Oct 24 12:55:32 xxxxx bootpd[10770]: DHCP DISCOVER [en1]: 1,0:21:9b:3b:61:e1
Oct 24 12:55:32 xxxxx bootpd[10770]: DHCP DISCOVER [en0]: 1,0:21:9b:3b:61:e1
Oct 24 12:55:32 xxxxx bootpd[10770]: OFFER sent pc1877t 172.29.135.204
pktsize 3
31
Oct 24 12:55:32 xxxxx bootpd[10770]: DHCP REQUEST [en1]: 1,0:21:9b:3b:61:e1
Oct 24 12:55:32 xxxxx bootpd[10770]: DHCP REQUEST [en0]: 1,0:21:9b:3b:61:e1
Oct 24 12:55:32 xxxxx bootpd[10770]: ACK sent pc1877t 172.29.135.204
pktsize 331

Archlinux 2013.10.01:

Oct 24 10:56:55 xxxxx bootpd[10692]: DHCP DISCOVER [en1]:
ff,0:0:0:2:0:1:0:1:19:
fb:1e:c3:0:21:9b:3b:61:e1 **
Oct 24 10:56:55 xxxxx bootpd[10692]: DHCP DISCOVER [en0]:
ff,0:0:0:2:0:1:0:1:19:
fb:1e:c3:0:21:9b:3b:61:e1 **
Oct 24 10:57:02 xxxxx bootpd[10692]: DHCP DISCOVER [en1]:
ff,0:0:0:2:0:1:0:1:19:
fb:1e:c3:0:21:9b:3b:61:e1 **
Oct 24 10:57:02 xxxxx bootpd[10692]: DHCP DISCOVER [en0]:
ff,0:0:0:2:0:1:0:1:19:
fb:1e:c3:0:21:9b:3b:61:e1 **
Oct 24 10:57:18 xxxxx bootpd[10692]: DHCP DISCOVER [en1]:
ff,0:0:0:2:0:1:0:1:19:
fb:1e:c3:0:21:9b:3b:61:e1 **
Oct 24 10:57:18 xxxxx bootpd[10692]: DHCP DISCOVER [en0]:
ff,0:0:0:2:0:1:0:1:19:
fb:1e:c3:0:21:9b:3b:61:e1 **

So, the DHCP server doesn't understand what archlinux is taking about. :-(

You may want set static address:

# host pc2517
pc2517.ms.unimelb.edu.au has address 172.29.135.33

with

nameserver 128.250.24.192
nameserver 128.250.24.193
nameserver 128.250.66.5
search ms.unimelb.edu.au
gateway 172.29.135.1
netmask 255.255.255.0

So, Archlinux: 0, Squeaky wheel gets the oil: 1.


Linux is NOT Windows | The Rootless Root
Toshiba Satellite i5-3230M 2.6GHz CPUs, 4Gb RAM, ArchLinux, wmii, nVidia GeForce GT 740M.

Offline

#14 2013-10-24 04:41:30

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 12,969

Re: [Pseudosolved] DHCP Timeouts: Driver or Config Problem?

I have not been ignoring you smile   I have been overcome by events.

Two things you may want to revisit.

First, are all of your pacnew files integrated?  I note that I had one for /etc/dhcpcd.conf.
Second, in /etc/dhcpcd.conf, have you tried enabling clientid and disabling duid ?

Last edited by ewaller (2013-10-24 04:41:45)


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Like you, I have no idea what you are doing, but I am pretty sure it is wrong...Jasonwryan
----
How to Ask Questions the Smart Way

Online

#15 2013-10-24 05:25:52

/dev/zero
Member
From: Melbourne, Australia
Registered: 2011-10-20
Posts: 1,176
Website

Re: [Pseudosolved] DHCP Timeouts: Driver or Config Problem?

ewaller wrote:

I have not been ignoring you smile   I have been overcome by events.

No worries smile


ewaller wrote:

First, are all of your pacnew files integrated?  I note that I had one for /etc/dhcpcd.conf.

N/A. The system is newly installed and has no pacnew files. I double-check anyway with:

sudo find /etc -type f -regex ".*\.pacnew"

and get no results.


ewaller wrote:

Second, in /etc/dhcpcd.conf, have you tried enabling clientid and disabling duid ?

Sure did!


Thanks anyway for trying to help smile


Linux is NOT Windows | The Rootless Root
Toshiba Satellite i5-3230M 2.6GHz CPUs, 4Gb RAM, ArchLinux, wmii, nVidia GeForce GT 740M.

Offline

Board footer

Powered by FluxBB