public IP being blocked

[garymansperger]

I have a new node to my network. The new node is 100% NS5 units in the form of 2 APs (2 sectors) and 9 clients.
The settings are all close to default
The radios are all on a private ip range (172.16.37.xx). I give each client a public static IP (207.47.32.xx) which they put into their routher.
Overall I have 5 such nodes but the rest are on a mix of older 2.4GHz radios (EnGenious, ubnt, etc). All work fine but this new "Show Case" node with all NS5s.
The problem of the moment is that I can ping the 172 net from both ends with no problems. But the clients are being blocked from the 207 public network (i.e They can log into the web browsers of all the NS5s but can not get to Google).
As there are some 40 other clients on other nodes that do not have this problem, I think I have some setting in the NS5 wrong, but can not find anything.
Any Ideas?

Thanks,
Gary

[dan]

Gidday, is a default gateway set correctly for the realworld network?
Can you perform a traceroute and see where it stops?

[garymansperger]

the gateway would do it, but I do not think that is the problem.

One thing I did not report is that if I put a computer on the client end with the public address in it rather than a router, I can not ping it from the POP end either, so the problem must be between the client and POP -- and everything between is 5GHZ ubnt radios.

[dan]

Gidday, you'll need to make sure you have turned NAT off to enable the core to see all the way back through to inside the radio.
You'll need to also make sure you have a route to the distant network on your core to enable getting to your distant network past your nano's outside IP address. Unless you put the whole lot in bridge mode then its just a Layer 2 connection through to your inside PC device between you and the core without NATing or Routing

Cheers
Dan

[garymansperger]

Dan,
I do have the client in bridge (station) mode so DHCP/NAT etc is off.
I noticed that even in bridge mode, the Network setup page is asking for DNS. I do not know why as in bridge mode the radio is simply connecting to the network like a wire.
However putting in the real dns should not hurt, so I have set up a new radio the same as the one installed at client with two exceptions:
I did put in real dns addresses
Maybe more important I put in 3.2.2-rc from the ubnt forum.

wish me luck & thanks for your suggestions.

ps- how deep into this WISP stuff are you?

[dan]

Gidday, another thing to try is putting the unit into Station WDS mode and the AP's (if they are nanos) into Access Point WDS mode. This will pass through all traffic without 'arp NATing' which sounds bizaar but caused so many issues on our network.

We have well over 100 Nanostations deployed now, most are going bloody marvelously!

We're just getting VLAN's working now and its going ok.
What else you wanna know ;)

Regards
Dan

[UBNT-Mike.Ford]

Dan,
I do have the client in bridge (station) mode so DHCP/NAT etc is off.
I noticed that even in bridge mode, the Network setup page is asking for DNS. I do not know why as in bridge mode the radio is simply connecting to the network like a wire.
However putting in the real dns should not hurt, so I have set up a new radio the same as the one installed at client with two exceptions:
I did put in real dns addresses
Maybe more important I put in 3.2.2-rc from the ubnt forum.

wish me luck & thanks for your suggestions.

ps- how deep into this WISP stuff are you?

Hey Gary,

When not in WDS bridging mode, the unit uses a form of ARPNAT when passing traffic from the Ethernet interface to the Wirless interface. The DNS server is here for this reason.

Thanks,

Mike

[garymansperger]

Hi Mike,
Here is what I am seeing (at least 2 clients connected to same AP (all NS5)

I move the client public IP to a different number. The client will be up and work fast (better than 13M up/down) for around 1 to 3 min. It will then slows down and within another min it will no longer work.
It seems to repeat - I can move them to a different IP, they are up then down.

All of the time I can log into the NS5 (on the private IP) client and all is good -- I can run speed test to the AP and it is better than 13M

I have gone done to the client and plugged my laptop into the radio and it work fine for a couple min, then failed.
I have by this ruled out a bad client router or computer.

I have quite a few other clients that work fine.

Via email, I will sent you the setup files of every radio in the path between client and my wired network.

Gary

[UBNT-Mike.Ford]

Hello Gary,

What is the ack timing that is reported on the main page of this unit when the speed slows down?

Thanks,

Mike