I have a Meru Controller thats sat on this subnet:
I'm trying to get to a AP on this subnet:
I can ping the device but I cant traceroute to the device.
traceroute to 172.16.200.1 (172.16.200.1), 30 hops max, 40 byte packets
1 10.0.0.76 (10.0.0.76) 13.993 ms 13.993 ms 13.993 ms
2 * * *
3 * * *
down to 30.
Would that mean I need to add a static route on 10.0.0.76 (HP ProCurve Switches) i.e.
ip route 172.16.200.0 255.255.255.0 172.16.200.1
Or am I way off?
If it can ping then L3 traffic is getting there and back ok.
Bugger thought that was the case, I was clasping at straws.
What are you pinging from the controller or a desktop?
Our meru AP's don't have IP's,
What is the actual issue?
So we have a remote site that connects to the main site via a site to site VPN.
The controller is on the main site and the APs have IPs assigned via the firewall (checked on the firewall and it has a IP).
When the AP was on the main site I specificed the IP of the controller so it wont try and use broadcast.
But the AP still wont connect so I started wondering if the issue was down to the routing.
you may need to bring the AP back to the site and set its discover mode from L2 only to L3 prefered mode, but you may already have done this to set the IP.
can you ping it from the Meru Controller?
You may need to specify the route on the Controller.
I havnt tried L3 but I will and that does make sense. Maybe I'll set a static IP on the AP (once I bring it back again).
Yes I can ping the AP from the controller.
Have you also double-checked your ACLs? It is possible that you haven't allowed enough ICMP for Windows to perform the traceroute.
Just for closure, I spoken to Meru who have spent quite a lot of time on this issue and still have no idea. So I've just received a serial to 3.5mm jack cable so we cant see what's happening on the AP's themselves. Will report back.
That's not closure LOL, :)
Originally Posted by RobD