Wireless Access

Reply
Occasional Contributor I
Posts: 6
Registered: ‎05-18-2012

Test L3 deployment, weird ARP issue with AP-93H

Hi All,

 

I've done L3 deployments a couple of times, routed stuff through multiple firewalls and routers, so I think I understand the basics. But I have no idea what's happening here... :)

 

Scenario: testing deployment with 620 controller and 2 93H APs. L2 connected works fine, firmware 6.1.3.5.

Connecting the other AP to a different vlan, vyatta (linux) router in between (also provides dhcp). Using DNS for controller location, also placed option 43 in dhcp, but that didn't solve it. I can't ping or arping the AP from the router or any other box. Here's the tcpdump from the booting of the AP:

 

15:50:03.230286 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328) 172.17.0.1.67 > 172.17.0.251.68: [udp sum ok] BOOTP/DHCP, Reply, length 300, xid 0x5d28ae04, secs 5, Flags [none] (0x0000)
	  Your-IP 172.17.0.251
	  Client-Ethernet-Address 00:1a:1e:10:06:6e
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Offer
	    Server-ID Option 54, length 4: 172.17.0.1
	    Lease-Time Option 51, length 4: 86400
	    Subnet-Mask Option 1, length 4: 255.255.240.0
	    Default-Gateway Option 3, length 4: 172.17.0.1
	    Domain-Name-Server Option 6, length 8: 10.1.40.163,10.1.40.166
	    Domain-Name Option 15, length 13: "accomm.gcd.ie"
	    Vendor-Option Option 43, length 4: 172.18.250.250
15:50:03.231031 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328) 172.17.0.1.67 > 172.17.0.251.68: [udp sum ok] BOOTP/DHCP, Reply, length 300, xid 0x5d28ae04, secs 5, Flags [none] (0x0000)
	  Your-IP 172.17.0.251
	  Client-Ethernet-Address 00:1a:1e:10:06:6e
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: ACK
	    Server-ID Option 54, length 4: 172.17.0.1
	    Lease-Time Option 51, length 4: 86400
	    Subnet-Mask Option 1, length 4: 255.255.240.0
	    Default-Gateway Option 3, length 4: 172.17.0.1
	    Domain-Name-Server Option 6, length 8: 10.1.40.163,10.1.40.166
	    Domain-Name Option 15, length 13: "accomm.gcd.ie"
	    Vendor-Option Option 43, length 4: 172.18.250.250
15:50:04.425777 IP (tos 0x0, ttl 255, id 3, offset 0, flags [DF], proto UDP (17), length 40) 172.17.0.251.8200 > 255.255.255.255.8200: [no cksum] UDP, length 12
15:50:06.457191 IP (tos 0x0, ttl 255, id 5, offset 0, flags [DF], proto UDP (17), length 40) 172.17.0.251.8200 > 255.255.255.255.8200: [no cksum] UDP, length 12
15:50:10.559354 arp who-has 172.17.0.1 tell 172.17.0.251
15:50:10.559373 arp reply 172.17.0.1 is-at 00:0e:0c:b1:33:a8
15:50:10.559452 IP (tos 0x0, ttl 255, id 7, offset 0, flags [DF], proto UDP (17), length 72) 172.17.0.251.1025 > 10.1.40.163.53: [no cksum] 1+ A? aruba-master.accomm.gcd.ie. (44)
15:50:10.559801 IP (tos 0x0, ttl 62, id 37635, offset 0, flags [none], proto UDP (17), length 212) 10.1.40.163.53 > 172.17.0.251.1025: [udp sum ok] 1* q: A? aruba-master.accomm.gcd.ie. 1/2/4 aruba-master.accomm.gcd.ie. A 172.18.250.250 ns: gcd.ie. NS ns2.gcd.ie., gcd.ie. NS ns1.gcd.ie. ar: ns1.gcd.ie. A 10.1.40.163, ns1.gcd.ie. AAAA 2001:4d68:200e:1111::a3, ns2.gcd.ie. A 89.124.205.6, ns2.gcd.ie. AAAA 2001:4d68:200e:1111::a6 (184)
15:50:15.557032 arp who-has 172.17.0.251 tell 172.17.0.1
15:50:16.556714 arp who-has 172.17.0.251 tell 172.17.0.1
15:50:17.556677 arp who-has 172.17.0.251 tell 172.17.0.1

 

172.17.0.1 is the router, 172.17.0.251 is the AP, 172.18.250.250 is the controller.

After finding the controller, the AP won't reply to any ARP request. Any ideas?

 

Cheers,

Tamas

 

Occasional Contributor I
Posts: 6
Registered: ‎05-18-2012

Re: Test L3 deployment, weird ARP issue with AP-93H

Update:

 

Hooked up the AP on layer 2, upgraded firmware and provisioned. Switched back port to original vlan, now works perfect...

Not sure about the original firmware on the AP.

Search Airheads
Showing results for 
Search instead for 
Did you mean: