Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Hi there guys. I have a quick question if any 1 has the time to confirm this. Im wanting to use a netgear FVS 318 VPN firewall router to route between two lans instead of a wan and a lan setup.
I have a subnet on the main side of the college 10.1.18.0. All clients get a 10.1.18.x address and the gateway is 10.1.18.1 (which is a port on layer 3 vlan switch) I have a room on its own with a server which runs dhcp and hands out addresses in the 192.168.0.0 range. My question is this... Can i use the the netgear firewall setup like this to give the room internet from the 10.1.18.0 range. I was thinking of plugging a network cable from the 10.1.18.0 range into the wan port on the netgear and giving it a wan address of say 10.1.18.254 and a lan adress of 192.168.0.254 and in the dhcp scope of the seperate room making their default gateway 192.168.0.254 (The netgear in this case) Thanks so much for your help. Regards Shaun
This should work for you, but you have to configure the standard gateway for the WAN port at the netgear router as well as the DNS server, the netgear should use at the WAN port.
The standard gateway of the netgear should be 10.1.18.1.Please send a reply, if you solved the problem !!!
0 
Cool so if i understand what you are saying i can make the wan ip say 10.1.18.254 and the dns and gateway adresses for the wan side 10.1.18.1 (pointing to the gateway of the layer 3 switch) ???
Shaun
0
The routers WAN interface will just connect as a normal client PC.
So if a normal PC can connect, why not a routers WAN interface?The main things are the right configured addresses for gateway and dns at the netgear as well as at the clients of the 192.168.x.x network.
For those clients, the netgear is the gateway and the DNS server.Please send a reply, if you solved the problem !!!
0
Ups, I made a mistake.
It woun't function, because the 10.x.x.x addresses are reserved for private networks.
A router will not route such addresses over the WAN port.
That's the problem.Sorry.
Please send a reply, if you solved the problem !!!
0
Give it a try, it works.
I tried it by myself.
Only if the IP on the WAN port is a routable (public) IP, the local IP addresse will not be routed.Please send a reply, if you solved the problem !!!
0
Ok cool that is weird because we have the same router in our server room.The wan ip is set to 10.1.31.241 and gateway is 10.1.31.242 (Which is a cisco router that connects to our remote site) The lan side is set to 10.1.16.3 which is a local subnet at the site where the Netgear router is... This seems to be working.. isnt 10.1.31.x range not routable over the wan port ??? It seems to be working tho :) Will set the other one up on monday and post the results :)
0
It seems to work, when the WAN interface of the router has a private, nonroutable address.
If the WAN interface has a public IP, the router must not route such private IPs to the internet.
See this link for the private IP ranges:
http://www.faqs.org/rfcs/rfc1918.htmlPlease send a reply, if you solved the problem !!!
0
Exactly im agreeing with you 100% but the weird thing is its working in our production environment as i said above lol... I will even give you a print screen on the router setup.... Anyway ill just give it a try...
0
Well gave it a try and much to my amazement its working hahahaha... 10.1.18.0 is routing over the wan port to the lan ip of 192.168.0.0. Well at least on netgear routers... Thanks for the advice on setting it up.
Shaun
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
