NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Static route with WG302 V2
Hi,
I am trying to get a WG302 to work on a different subnet for the wireless. This is how the setup is:
WG302 - IP address is 172.16.100.2, DHCP scope is 172.16.100.110 - 254
Default gateway is 172.16.100.1, which is connected to a firewall with a static route in place.
The wireless network shows up, and I can connect to it, but it cannot ping hosts on the network or access local/Internet resources.
Is there something missing? Is there a way I can add a static route through the interface? Or through the console?
Thanks
I am trying to get a WG302 to work on a different subnet for the wireless. This is how the setup is:
WG302 - IP address is 172.16.100.2, DHCP scope is 172.16.100.110 - 254
Default gateway is 172.16.100.1, which is connected to a firewall with a static route in place.
The wireless network shows up, and I can connect to it, but it cannot ping hosts on the network or access local/Internet resources.
Is there something missing? Is there a way I can add a static route through the interface? Or through the console?
Thanks
8 Replies
- if your primary DHCP uses 172.16.100.x then assuming you doing like
main router DHCP 172.16.100. 3~172.16.100.109
and you are trying to use WG302 DHCP 172.16.100.110-254
if this is how you are doing it?which is connected to a firewall with a static route in place
how you are routing...? jmizoguchi wrote: if your primary DHCP uses 172.16.100.x then assuming you doing like
main router DHCP 172.16.100. 3~172.16.100.109
and you are trying to use WG302 DHCP 172.16.100.110-254
if this is how you are doing it?
how you are routing...?
The main DHCP is 172.16.1.x which comes from a Win2K3 domain controller. DHCP is configured on the WG302 to provide addresses for 172.16.100.x (wireless subnet).
As far as the firewall/routing goes, it is like this:
Firewall port (172.16.100.1) -| -- | - LAN port on WG302 (172.16.100.2)
172.16.100.1 is configured as the default gateway on the WG302. On the firewall, 172.16.100.1 has a static route in place back to the main subnet, 172.16.1.x. So in theory a wireless client should be able to communicate with local and Internet resources, because the default gateway has a route configured to be able to do so.
Does this clean things up?- The primary DHCP is 172.16.1.x which comes from a Win2K3 domain controller. The DHCP I have configured on the WG302 is 172.16.100.x.
To answer the question about routing, the setup is like this:
The WG302 has an IP address of 172.16.100.2, and is connected to a port on the firewall configured with the IP address of 172.16.100.1. On the firewall a static route has been created for the address 172.16.100.1 to be able to route between the 172.16.1.x and 172.16.100.x subnets. The default gateway of the WG302 is set to 172.16.100.1. So in theory a wireless device which gets an IP of 172.16.100.x from the DHCP on the WG302 should be able to route between the subnets since the default gateway has a route for the two subnets.
Does this clear things up? - A WG302 cannot route - it's not a router. If you set it to issue a different ip range you'll need to have the upstream router perform the routing tasks - if it can - not all routers support subinterfaces and multiple local networks.
- depending switch but maybe good lawyer switch with vlan would be more suitable .
- I just bought a wireless router and it all works now.
Thanks jn865 wrote: I just bought a wireless router and it all works now.
Thanks
It all seems to work now - you'll be back when you discover that it doesn't route like you think it should. ;) I think you'll find the wireless clients can access the internet & the wired network, but the wired network clients can't see the wireless clients.- You are correct that the wireless can access the wired network and the Internet. I have not verified the latter of the two, and I do not believe it should matter for my implementation.
Thanks
