Cant access my access point on network, strange tracert
-
192.168.1.2 = My TP-Link Wireless Router Archer C9 I use as a Access Point only
tracert 192.168.1.2
Tracing route to 192.168.1.2 over a maximum of 30 hops
1 36 ms 29 ms 29 ms 192.168.10.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.Trace complete.
192.168.1.15 = My Synology Diskstation
tracert 192.168.1.15
Tracing route to diskstation.localdomain [192.168.1.15]
over a maximum of 30 hops:1 29 ms 29 ms 29 ms 192.168.10.1
2 29 ms 29 ms 35 ms diskstation.localdomain [192.168.1.15]Any ideas why I cant access the TPLINK Archer C9 192.168.1.2 on the VPN side (I can access it fine on the local network)? This seems to be the only device on my network I cant access on the vpn client-side
-
Probably has no concept of a default gateway on the LAN side so it has nowhere to send traffic for other than its local subnet.
There might be a setting in the router for "Access point" mode or something.
If you really need to access it you can do outbound NAT on LAN for destination 192.168.1.2.
-
Probably has no concept of a default gateway on the LAN side so it has nowhere to send traffic for other than its local subnet.
There might be a setting in the router for "Access point" mode or something.
If you really need to access it you can do outbound NAT on LAN for destination 192.168.1.2.
Hmm… so the destination device (the archer router/access point) is not able to route back to the device trying to communicate with it?
I notice it's not in the ARP Table , i think all my devices are except this archer
what do you mean outbound nat on lan? not sure..
-
When you set the IP address of the access point's LAN interface, is there a place to put a default gateway? Usually not in consumer routers doing access point duty.
Something like the 192.168.1.2/32 rule here. In Firewall > NAT, Outbound
Note the hybrid checked.
 -
yeah if you look at their c9 emulator.. The lan settings have no place for a gateway.. So going to be impossible to access the gui from another network.
But you may be able to create a route for your other network in the advanced routing section - see 2nd pic from their emulator
If not then sure the source natting that Derelict suggest would be work around for devices that do not let you set a gateway or route to get off their local network.
-
When you set the IP address of the access point's LAN interface, is there a place to put a default gateway? Usually not in consumer routers doing access point duty.
Something like the 192.168.1.2/32 rule here. In Firewall > NAT, Outbound
Note the hybrid checked.
This worked, Thank you
-
Glad it worked. Thanks for the thanks.
-
Wouldn't it just be easier to create the route on the AP vs doing a source nat? Did you try that?
-
My pfSense router is at 192.168.1.1 and the AP is 192.168.1.2. My OpenVPN pool is 10.0.8.0. I am having the same issue where the TP-Link router has no gateway information, so the webgui does not load over openVPN.
Do I need to forward the 10.0.8.0 network to the gateway 192.168.1.1? I was successful in doing the other method of outbound NAT. This is new to me, but I would like to learn the route method.
Thanks,
Jerold -
If you can enter a default route in the static routes, then enter one pointed at the pfSense interface. That would be the preferred method.
