|
FreeBSD Ports and Packages Installation and upgrading of ports and packages on FreeBSD. |
|
Thread Tools | Display Modes |
|
|
|||
dhcpd, vista and wlan
Hi,
I have an interesting problem with MS Vista and dhcpd running of my FreeBSD router. dhcpd doesn't want to give an ip address to any of the MS Vista clients on the WLAN side, but on the LAN it works fine and MS XP doesn't have this problem over the WLAN. I have a bridge between ath0 and rl3 called bridge0 and this is used for assigning the ips from dhcpd. Does any know why this only affects MS Vista clients? Thanks hamba |
|
|||
I have no idea, but can you see the Vista DHCP requests with tcpdump?
f you can see them, then compare them with the XP requests.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
|||
hmm, I see this when requesting an ip using vista,
Code:
# tcpdump -i bridge0 port 67 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on bridge0, link-type EN10MB (Ethernet), capture size 96 bytes 10:24:38.545526 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:16:ea:25:76:b0 (oui Unknown), length 300 10:24:39.001127 IP fire.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300 10:24:42.111139 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:16:ea:25:76:b0 (oui Unknown), length 300 10:24:42.112175 IP fire.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300 10:24:50.427196 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:16:ea:25:76:b0 (oui Unknown), length 300 10:24:50.428296 IP fire.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300 10:25:07.493860 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:16:ea:25:76:b0 (oui Unknown), length 300 10:25:07.495414 IP fire.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 300 Code:
2008-11-20 10:24:38.545322 rule 44/0(match): pass in on ath0: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:16:ea:25:76:b0, length 300 2008-11-20 10:24:38.545440 rule 42/0(match): pass out on bridge0: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:16:ea:25:76:b0, length 300 Code:
# tcpdump -i bridge0 port 67 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on bridge0, link-type EN10MB (Ethernet), capture size 96 bytes 10:32:28.316675 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:19:db:04:86:9e (oui Unknown), length 300 10:32:29.001626 IP fire.bootps > 10.1.10.199.bootpc: BOOTP/DHCP, Reply, length 300 10:32:29.006178 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:19:db:04:86:9e (oui Unknown), length 326 10:32:29.009442 IP fire.bootps > 10.1.10.199.bootpc: BOOTP/DHCP, Reply, length 300 Code:
2008-11-20 10:32:28.316448 rule 44/0(match): pass in on ath0: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:19:db:04:86:9e, length 300 2008-11-20 10:32:28.316569 rule 42/0(match): pass out on bridge0: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:19:db:04:86:9e, length 300 |
|
|||
Try the following to get a more verbose output
Code:
# tcpdump -eni bge0 -s512 -vv tcpdump: listening on bge0, link-type EN10MB 22:01:05.378827 00:10:18:00:9f:fd ff:ff:ff:ff:ff:ff 0800 342: 0.0.0.0.68 > 255.255.255.255.67 : [udp sum ok] xid:0x4cef1e6d vend-rfc1048 HN:"hercules" RQ:192.168.222.231 DHCP:DISCOVER PR: SM+BR+DG+DN+NS+HN [tos 0x10] (ttl 16, id 0, len 328) 22:01:05.380115 00:08:c7:05:ca:0b ff:ff:ff:ff:ff:ff 0806 60: arp who-has 192.168.222.248 tell 192.168.222.10 22:01:05.380561 00:08:c7:05:ca:0b 00:10:18:00:9f:fd 0800 342: 192.168.222.10.67 > 192.168.222 .248.68: [udp sum ok] xid:0x4cef1e6d Y:192.168.222.248 S:192.168.222.10 vend-rfc1048 DHCP:OFF ER SID:192.168.222.10 LT:43200 SM:255.255.255.0 DG:192.168.222.10 DN:"utp.net" NS:192.168.222 .10 [tos 0x10] (ttl 16, id 0, len 328) 22:01:07.395831 00:10:18:00:9f:fd ff:ff:ff:ff:ff:ff 0800 342: 0.0.0.0.68 > 255.255.255.255.67 : [udp sum ok] xid:0x4cef1e6d vend-rfc1048 HN:"hercules" RQ:192.168.222.248 DHCP:REQUEST SID: 192.168.222.10 PR:SM+BR+DG+DN+NS+HN [tos 0x10] (ttl 16, id 0, len 328) 22:01:07.455589 00:08:c7:05:ca:0b 00:10:18:00:9f:fd 0800 342: 192.168.222.10.67 > 192.168.222 .248.68: [udp sum ok] xid:0x4cef1e6d Y:192.168.222.248 S:192.168.222.10 vend-rfc1048 DHCP:ACK SID:192.168.222.10 LT:43200 SM:255.255.255.0 DG:192.168.222.10 DN:"utp.net" NS:192.168.222.1 0 [tos 0x10] (ttl 16, id 0, len 328) 22:01:07.465087 00:10:18:00:9f:fd ff:ff:ff:ff:ff:ff 0806 42: arp who-has 192.168.222.248 tell 192.168.222.248 22:01:07.465237 00:08:c7:05:ca:0b 00:10:18:00:9f:fd 0800 62: 192.168.222.10 > 192.168.222.248 : icmp: echo request (id:a656 seq:0) (ttl 255, id 53252, len 48) 22:01:07.465270 00:10:18:00:9f:fd ff:ff:ff:ff:ff:ff 0806 42: arp who-has 192.168.222.10 tell 192.168.222.248 22:01:07.465380 00:08:c7:05:ca:0b 00:10:18:00:9f:fd 0806 60: arp reply 192.168.222.10 is-at 00:08:c7:05:ca:0b 22:01:07.465395 00:10:18:00:9f:fd 00:08:c7:05:ca:0b 0800 62: 192.168.222.248 > 192.168.222.10 : icmp: echo reply (id:a656 seq:0) (ttl 255, id 53475, len 48) Notice the ARP requests issued by the server (192.168.222.10) as well as the client (192.168.222.248). And the ICMP ping issued by the server.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
|||
Basically, vista dchp requests insists on the broadcast flag
to be set, thus causing problems with dhcp serving devices. As a new user, I can't post the link to help you : ( Look aroud the web, the broadcast flag problem is well known. Typical of Microsoft expectiong users to modify the binary monstrosity that is the Windows registry. Backups are a good idea here. Also, the power saving features implemented in vista could also cause problems. The above solution is more likely thoguh. |
|
|||
Also, make sure IPV6 is not in use as a primary routing mechanism.
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Dell 1395 WLAN Drivers | yanjchan | FreeBSD General | 2 | 30th August 2009 09:28 AM |
dhcpd and dns | sputnik | OpenBSD General | 8 | 8th May 2009 02:50 PM |
dhcpd within ezjail? | zelut | FreeBSD General | 7 | 10th February 2009 10:31 PM |
WLAN | giga | FreeBSD General | 2 | 5th February 2009 03:53 PM |
wlan -> monitor mode | ccc | FreeBSD Security | 2 | 4th November 2008 09:19 PM |