Re: way OT: route table

From: nic (anonymous_at_discussions.microsoft.com)
Date: 04/02/04 

Date: Fri, 2 Apr 2004 10:36:47 -0800

Thanks for the quick response. In your post you said to
try this:
>>first try
>>route -p add 32.76.0.0 mask 255.255.0.0 192.168.16.1

Maybe I'm not userstanding or I didn't explain myself.
The default gateway is at 192.168.16.1.
The private gateway is at 192.168.0.1.

when accessing 32.76.x.x I need to go through the private
gateway (192.168.0.1) NOT the default gateway
(196.168.16.1). Adding a route add line of:
>>route -p add 32.76.0.0 mask 255.255.0.0 192.168.16.1
would cause the request to go through the default gateway
and not the private gateway. When I try to add a route of
>>route add 32.76.x.0 mask 255.255.255.0 192.168.0.1

I get an error saying "either the interface index is wrong
or the gateway does not lie on the same network as the
interface". The private router is set up to pass all
traffic to the private network but I'm having trouble
accessing the private gateway.

If I'm on the 192.168.16.0 network, how can I send a
request to the 192.168.0.1 gateway?
pinging yahoo for example I want to go through
192.168.16.1 but
pinging 32.26.x.x I want to go through 192.168.0.1

Once again sorry if you already answered the question, I
just don't quite understand the answer.

>-----Original Message-----
>NIC:
>
>Here is my $0.02:
>
>first try
>route -p add 32.76.0.0 mask 255.255.0.0 192.168.16.1
>but don't forget you need the routing tables set up in
your
>access router also. Both ends. And both ways. This
should
>get ping to work. DNS, is another post.
>
>You have your internal IP range of 192.168.16.0
>your access router (CSU/DSU interface) has an interface on
>your local network as 192.168.16.1 (I think this is what
you
>implied in your post.)
>
>IP routing of the data packets happens in your access
>router and the external address is probably 192.186.0.1
>
>on the other side of the point-to-point is another access
router with
>an address pointing to you with something like
192.186.0.2 or something.
>(what ever it is, it must be within the mask of the two
access router
>external IP address.)
>
>Another IP routing of data packets takes place inside the
remote access
>router and the local interface of the remote access
router will probably be
>something like 32.76.0.1
>
>You set up your local routing table to forward all
32.76.X.X to the local
>interface on your access router.
>The local access router should have its route table setup
>to forward all 32.76.X.X to the remote access router.
>the remote access router should know to pass all
>32.76.X.X to the remote local interface.
>
>If it is setup correctly, the remote site could have a
different
>IP Scheme at the local interface of the remote access
router,
>but as long as the routing tables along the way know to
keep
>passing 32.76.X.X along to the next router, your packet
should
>get to network 32.76.X.X.
>
>I hope this is not too confusing. Just remember, the
routing
>tables must be set up to find your local IP Scheme also.
>
>Phil S.
>
>"nic" <anonymous@discussions.microsoft.com> wrote in
message
>news:1783b01c418d1$74bc3760$a401280a@phx.gbl...
>> I'm not sure who to ask. If any of you know of a better
>> newsgroup just let me know.
>>
>> OK, we are running SBS 2000 with an internal IP network
of
>> 192.168.16.0 (net mask 255.255.255.0, gateway
>> 192.168.16.1). We have a need to add a frame-relay
point
>> to point connection with another company. This uses a
>> completely different router and is on a seperate network
>> of 192.168.0.0 (net mask 255.255.255.0, gateway
>> 192.168.0.1) This will give us a private connection to
>> their network. On their network I have to reach one of
>> their servers (32.76.xx.xx). I was told I could add a
>> static route in the route table to access the private
>> network. (I have a server that needs to be on the main
>> network but still access the private network)
>>
>> I tried adding a static route of
>> >>route add 192.168.0.0 mask 255.255.255.0 192.168.0.1
>>
>> This fails saying the interface could not be found. If
on
>> that machine, I change my IP to go to the private
network,
>> I can successfully ping the gateway. But how can I
remain
>> on the 192.168.16.0 network but still access the
>> 192.168.0.1 gateway? I'm hoping there is a networking
>> guru out there. I'm pretty sure it will involve a
static
>> route but i'm having trouble.
>>
>> Thanks
>
>.
>

Relevant Pages

  • Re: [SLE] connection redundancy
    ... which is the router just this side of the ... >>because it's own gateway is still up. ... You'll also need three network cards to put into this Linux box. ... your internal LAN can route packets to the Internet. ...
    (SuSE)
  • Re: Cant access secure Web pages
    ... and which need to be contacted via the Default Gateway. ... The Default Gateway being the software process that does the network ... Gateway (as set up by your ISP's DHCP packet to the router), ... me so I can send it directly (to the MAC address discovered by ARP). ...
    (uk.comp.sys.mac)
  • Re: please advise - problem with routing
    ... Actually, these are HOST addresses, not NETWORK addresses. ... I will assume that this means from the 192.168.1.x/24 subnet you can ... your Internet Router, and not related to routing between the two internal ... Gateway using Interface 192.168.1.12. ...
    (microsoft.public.windows.server.networking)
  • Re: Adding a route question
    ... Do I have my network cards gateways configured correctly? ... Subnet mask 255.255.255.0 ... With one router it is ... > gateway" so no static routes need to be manually ADDED. ...
    (microsoft.public.win2000.networking)
  • Re: 1 server 2 nic 2 adsl lines, gateway problem
    ... That won't work to have 2 external NICs connected to 2 separate routers. ... need a dual WAN type router instead that will connect to a single external ... > the gateway address on nic 1 to access router 192.168.0.254 ...
    (microsoft.public.windows.server.sbs)