CPE:RB112 2.9.49 F/W using Wistron CM9 a/b/g MINICPCI PAC Wireless 19 OR 24db ROO2. Frequency/Ch-Width:5.8Ghz-20Mhz Encryption:WPA2
I have been experiencing strange behavior as of late when installing new clients onto the network.
I connect to the AP of choice with a -70 to -65 without problem; but the ARP Listwill not dynamically set the preferred Gateway Address which I am sure is inhibiting IP traffic flow for the connected client device?
At this time I already have other clients connected to the same AP and other AP’s alike with no troubles what-so-ever using the identical RouterBoard/MINIPCI/Antenna configurations.
As a matter of fact out of pure frustration I have taken a back-up from functioning client devices and then restored those into the new client devices I am having trouble with.
After changing IP Address, Gateway and such after restoring the config though these devices all behave the same, connect to the AP with great signal strength but the ARP List does not dynamically set the Gateway address therefore not allowing communications to the outside world…
I have double checked my Firewall, all I have in there is a rule to allow traffic between ether1 and wlan1- no red text all good.
Likewise I have double checked the NAT, it is utilizing WLAN1 as the out-interface- no red text all is good.
All of my functioning clients CPE’s of the identical build are populating the ARP List with the Gateway Address and are able to go to the outside world!
Has anybody got any suggestions?
I have been trying to rectify this issue since Thursday without any success, I have even tried all devices I have in stock and all are behaving identical as described above…
I would sure appreciate some help with this one, thank you.
In desperation knowing this is wrong, I went ahead and set the Gateway of one of the CPE’s I can’t see the public from to the IP of another client device which is properly functioning on the same AP within the same sub-net and viola! Internet connectivity but from The Dude in the NOC I can’t access the CPE using the IP of another clients as it Gateway???
Maybe this will help with troubleshooting?
Anyone got suggestions or has run into the same issue like this??
Has anyone got any idea why my newly added client devices require the use of other client device as the Default Gateway?
In example: Today I installed a few new clients: 172.16.4.25, 172.16.4.18, 172.16.4.40 & 172.16.4.36.
On each of the above mentioned CPE’s I wound up using the IP 172.16.4.10 as their Default Gateway.
CPE 172.16.4.10 is a properly functioning client CPE which uses the IP 172.16.4.1 as it’s Default Gateway.
Why am I having to do this to establish IP communications to the outside world?
This is all very strange, other clients are utilizing the Gateway IP’s which are handed out by my AIRLok… Gateway Addresses: 10.0.0.1
10.10.0.1
172.16.2.1
172.16.3.1
172.16.4.1
172.16.5.1
172.16.6.1
172.16.7.1
192.168.0.1
Another problem this is causing me is I am unable to monitor clients VIA The Dude, which in-turn will force me to re-trip to ALL newly installed clients homes to correct the Default Gateway once this dilemma is figured out!
I sure would appreciate some input or suggestions regarding this issue… <@
ARP is not responsible for settings gateway. ARP is responsible to bind together local client IP address and MAC address.
Do you use DHCP-client for the interface ?
If yes, than you have to use 'ip dhcp-cliet set add-default-route=yes
Please, provide with simple network diagram, where include current network configuration.
You have to use gateway as border network of the router (border between different network).
For Dude you have to ensure that is proper routing between Dude server and your local network.
