Apple OSX Not responding to DHCP
This is probably not the cause of all of the self-assigned IP problems but I clearly see my MAC requesting a DHCP address, my router/firewall responding with that address and the MAC ignoring it. There seems to be something broken with either the user interface, networking or keychain or all three combined. Apple has no clue how to fix this problem. In fact, they do not even know they have a problem. The Geniuses at the Genius Bar are absolutely clueless.
I have a third party USB-Ethernet adapter connected to the Mac because I got fed up trying to get the Thunderbolt GE to work consistently. IP is IP. DHCP should work with any device if it is implemented properly. You can clearly see in the TCPDUMP capture below that the MAC is sending out the DHCP request and it is getting responded to but the Mac either ignores it or blocks it. This happens regularly with my WIFI interface as well.
If I fire up Linux under VirtualBox with a Bridged virtual adapter on that same exact USB-Eth interface I get an IP address very quickly when Linux DHCP requests an address. Linux works just fine. The Linux developers know how networking works, Apple does not.
I've done pretty much everything that has been suggested on this and other threads in other forums...all to no avail.
Here's a TCPDUMP sample (this will go on forever if you let it):
This is probably not the cause of all of the self-assigned IP problems but I clearly see my MAC requesting a DHCP address, my router/firewall responding with that address and the MAC ignoring it. There seems to be something broken with either the user interface, networking or keychain or all three combined. Apple has no clue how to fix this problem. In fact, they do not even know they have a problem. The Geniuses at the Genius Bar are absolutely clueless.
I have a third party USB-Ethernet adapter connected to the Mac because I got fed up trying to get the Thunderbolt GE to work consistently. IP is IP. DHCP should work with any device if it is implemented properly. You can clearly see in the TCPDUMP capture below that the MAC is sending out the DHCP request and it is getting responded to but the Mac either ignores it or blocks it. This happens regularly with my WIFI interface as well.
If I fire up Linux under VirtualBox with a Bridged virtual adapter on that same exact USB-Eth interface I get an IP address very quickly when Linux DHCP requests an address. Linux works just fine. The Linux developers know how networking works, Apple does not.
I've done pretty much everything that has been suggested on this and other threads in other forums...all to no avail.
Here's a TCPDUMP sample (this will go on forever if you let it):
Code:
17:02:45.648288 00:50:b6:4f:10:6d > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:50:b6:4f:10:6d, length 300
17:02:45.648892 00:25:90:cb:5d:b5 > 00:50:b6:4f:10:6d, ethertype IPv4 (0x0800), length 342: 10.254.0.161.67 > 10.254.0.181.68: BOOTP/DHCP, Reply, length 300
17:02:49.345262 00:50:b6:4f:10:6d > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 72: 169.254.3.237.5353 > 224.0.0.251.5353: 0 AAAA (QU)? hunter.local. (30)
17:02:49.345304 00:50:b6:4f:10:6d > 33:33:00:00:00:fb, ethertype IPv6 (0x86dd), length 92: fe80::250:b6ff:fe4f:106d.5353 > ff02::fb.5353: 0 AAAA (QU)? hunter.local. (30)
17:02:49.518808 00:50:b6:4f:10:6d > 01:00:5e:00:00:fb, ethertype IPv4 (0x0800), length 130: 169.254.3.237.5353 > 224.0.0.251.5353: 0*- [0q] 1/0/2 (Cache flush) AAAA fe80::250:b6ff:fe4f:106d (88)
17:02:49.518810 00:50:b6:4f:10:6d > 33:33:00:00:00:fb, ethertype IPv6 (0x86dd), length 150: fe80::250:b6ff:fe4f:106d.5353 > ff02::fb.5353: 0*- [0q] 1/0/2 (Cache flush) AAAA fe80::250:b6ff:fe4f:106d (88)
17:02:54.572948 00:50:b6:4f:10:6d > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:50:b6:4f:10:6d, length 300
17:02:54.573547 00:25:90:cb:5d:b5 > 00:50:b6:4f:10:6d, ethertype IPv4 (0x0800), length 342: 10.254.0.161.67 > 10.254.0.181.68: BOOTP/DHCP, Reply, length 300
17:03:02.947160 00:50:b6:4f:10:6d > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:50:b6:4f:10:6d, length 300
17:03:02.947644 00:25:90:cb:5d:b5 > 00:50:b6:4f:10:6d, ethertype IPv4 (0x0800), length 342: 10.254.0.161.67 > 10.254.0.181.68: BOOTP/DHCP, Reply, length 300
17:03:04.574139 00:50:b6:4f:10:6d > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 145: 169.254.3.237.17500 > 169.254.255.255.17500: UDP, length 103
17:03:11.826959 00:50:b6:4f:10:6d > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:50:b6:4f:10:6d, length 300
17:03:11.827495 00:25:90:cb:5d:b5 > 00:50:b6:4f:10:6d, ethertype IPv4 (0x0800), length 342: 10.254.0.161.67 > 10.254.0.181.68: BOOTP/DHCP, Reply, length 300
17:03:20.319246 00:50:b6:4f:10:6d > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:50:b6:4f:10:6d, length 300
17:03:20.319827 00:25:90:cb:5d:b5 > 00:50:b6:4f:10:6d, ethertype IPv4 (0x0800), length 342: 10.254.0.161.67 > 10.254.0.181.68: BOOTP/DHCP, Reply, length 300
17:03:29.293837 00:50:b6:4f:10:6d > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:50:b6:4f:10:6d, length 300
17:03:29.294249 00:25:90:cb:5d:b5 > 00:50:b6:4f:10:6d, ethertype IPv4 (0x0800), length 342: 10.254.0.161.67 > 10.254.0.181.68: BOOTP/DHCP, Reply, length 300
17:03:34.595069 00:50:b6:4f:10:6d > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 145: 169.254.3.237.17500 > 169.254.255.255.17500: UDP, length 103
17:04:04.616179 00:50:b6:4f:10:6d > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 145: 169.254.3.237.17500 > 169.254.255.255.17500: UDP, length 103
17:04:34.633683 00:50:b6:4f:10:6d > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 145: 169.254.3.237.17500 > 169.254.255.255.17500: UDP, length 103
17:04:38.279041 00:50:b6:4f:10:6d > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:50:b6:4f:10:6d, length 300
17:04:38.279563 00:25:90:cb:5d:b5 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 10.254.0.181 tell 10.254.0.161, length 46
17:04:39.280135 00:25:90:cb:5d:b5 > 00:50:b6:4f:10:6d, ethertype IPv4 (0x0800), length 342: 10.254.0.161.67 > 10.254.0.181.68: BOOTP/DHCP, Reply, length 300
17:04:40.209036 00:50:b6:4f:10:6d > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:50:b6:4f:10:6d, length 300
17:04:40.209487 00:25:90:cb:5d:b5 > 00:50:b6:4f:10:6d, ethertype IPv4 (0x0800), length 342: 10.254.0.161.67 > 10.254.0.181.68: BOOTP/DHCP, Reply, length 300
17:04:42.578508 00:50:b6:4f:10:6d > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:50:b6:4f:10:6d, length 300
17:04:42.578914 00:25:90:cb:5d:b5 > 00:50:b6:4f:10:6d, ethertype IPv4 (0x0800), length 342: 10.254.0.161.67 > 10.254.0.181.68: BOOTP/DHCP, Reply, length 300
17:04:47.581546 00:50:b6:4f:10:6d > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:50:b6:4f:10:6d, length 300
17:04:47.581962 00:25:90:cb:5d:b5 > 00:50:b6:4f:10:6d, ethertype IPv4 (0x0800), length 342: 10.254.0.161.67 > 10.254.0.181.68: BOOTP/DHCP, Reply, length 300
17:04:56.040690 00:50:b6:4f:10:6d > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:50:b6:4f:10:6d, length 300
17:04:56.041235 00:25:90:cb:5d:b5 > 00:50:b6:4f:10:6d, ethertype IPv4 (0x0800), length 342: 10.254.0.161.67 > 10.254.0.181.68: BOOTP/DHCP, Reply, length 300
17:05:04.560578 00:50:b6:4f:10:6d > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:50:b6:4f:10:6d, length 300
17:05:04.561169 00:25:90:cb:5d:b5 > 00:50:b6:4f:10:6d, ethertype IPv4 (0x0800), length 342: 10.254.0.161.67 > 10.254.0.181.68: BOOTP/DHCP, Reply, length 300
17:05:04.653758 00:50:b6:4f:10:6d > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 145: 169.254.3.237.17500 > 169.254.255.255.17500: UDP, length 103
Last edited by a moderator: