Re: Adding Static route
- From: "moncho" <moncho990009@xxxxxxxxxxxxxxxxxx>
- Date: Wed, 12 Apr 2006 12:35:15 GMT
Thanks for the info Bill. After reading it, it made alot of sense.
The server is a TS server for VPN clients. We had it on
192.xxx.xxx.xxx address but our one client is using the same IP
scheme. Our VPN does not have a problem because it will route
back to the external IP of the client but the client cannot get to our
Internal IP.
Anywho, I figured out late yesterday that I will have to add static
routes back to the external IP of the client and all was well. This is
only good if they have static IP's.
I was thinking about putting the default gateway on the 172.xxx. and
removing it from the 192.xxx. This way our Internal users on the
192.xxx net do not need to worry about the default gateway and I
will not need to add static routes for my external clients if they
have Dynamic IP's.
Thanks again,
moncho
Any
"Bill Grant" <not.available@online> wrote in message
news:e459o4dXGHA.2268@xxxxxxxxxxxxxxxxxxxxxxx
You cannot route traffic based on where it came from. You can only
route it based on its destination address.
What is the purpose of this machine? If it is not the VPN device or the
gateway router, what does it do? I presume you want to use it as a router
between the 192.168.1.0 subnet and the remote devices.
If you want to route traffic between the 192.168.1.0 and the
172.31.23.0 subnets, adding a static route to this machine will not do it
for you. The routing decision for that is made at the gateway router at
192.168.1.25 .
If a machine in 192.168.1 has a packet for 172.31.23.x it will send it
to the default gateway (unless it has a specific route to send it
somewhere else). If the default gateway doesn't have a route for it, it
will be dropped because the gateway's default is out to the Internet
(which discards private traffic).
The first problem is to get the 172 31.23 traffic to your server at
192.168.1.15 . You could do that by adding a static route to the gateway
router. eg
172.31.23.0 255.255.255.0 192.168.1.15
You may also need a static route on this machine to get the traffic to
the VPN device eg
172.31.23.0 255.255.255.0 172.31.23.25
moncho wrote:
"Pierrot Robert" <mcthepro_at_hotmail.com> wrote in message
news:uUj8h7XXGHA.1084@xxxxxxxxxxxxxxxxxxxxxxx
What is the other(s) IP subnet on the other side of the 172.31.23.25
router ?
The IPs on the other subnets will be different because they are
coming in through
a VPN and some use dial-up connections.
The 172.31.23.25 is actually a VPN appliance and also acting as the
router (my bad
for not supplying this info0.
I figure if the .25 takes care of routing,VPN and Firewall, I just
need to point traffic
comin in on 172.31.23.xxx back to the .25.
THanks,
moncho
These are the subnets you need to do a "route add" for.
Pierrot
moncho wrote:
I need a little help setting the static route for the 2nd NIC. I
just want any external traffic that
comes in on the 172.31.23.0/24 Network to go back out the same way.
I know I cannot use
two default gateways and need to add a static route.
NIC #1
IP Address. . . . . . . . . . . . : 192.168.1.15
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.25
NIC #2
IP Address. . . . . . . . . . . . : 172.31.23.15
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
The IP of our other router is 172.31.23.25 (mask is 255.255.255.0)
Do i just use "route add -p 172.31.23.15 mask 255.255.255.0
172.31.23.25"
TIA
moncho
.
- Follow-Ups:
- Re: Adding Static route
- From: Bill Grant
- Re: Adding Static route
- References:
- Adding Static route
- From: moncho
- Re: Adding Static route
- From: Pierrot Robert
- Re: Adding Static route
- From: moncho
- Re: Adding Static route
- From: Bill Grant
- Adding Static route
- Prev by Date: SBS launchconsole.exe - is there similar tool available for 2003 standard
- Next by Date: Re: Share / NTFS Permissions Windows 2003 Server Subfolder
- Previous by thread: Re: Adding Static route
- Next by thread: Re: Adding Static route
- Index(es):
Relevant Pages
|