• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 221
  • Last Modified:

Need router to accept traffic from two sources

I need my 3com router to accept traffic from the following: 1) 192.168.0.xxx addresses and 2) a single address on a 68.255.169.xxx network.  But here's the part that's throwing me off, the LAN side of the 3com router is ALREADY on the 192.168.0.xxx and the WAN side is ALREADY on the 68.255.169.xxx network.  As it is now, the router is handling traffic from the 192.168.0.xxx network just fine, but it's not allowing through traffic from the 68.255.169.xxx network (obviously, because the LAN side is on a different subnet than the traffic it's trying to allow).  I was told that I need to add a static route to allow the 68.255.169.x traffic to access the 192.168.0.xxx LAN side of the router (this router only has a web interface with the following fields: destination network, subnet mask, gateway address, and a drop down with the choices "LAN" or "WAN").  Could someone please tell me what to enter for each field?  Also, as plainly as possible, could someone explain what is meant by destination address, gateway address, and "LAN" and "WAN" as it applies here to static routes?  Thanks much.
0
QuiteSupersonic
Asked:
QuiteSupersonic
1 Solution
 
JFrederick29Commented:
You shouldn't need static routes as the two networks are on the same router.  Routing between the LAN and WAN interfaces should be automatic.  What are you trying to do and what is not working?
0
 
Don JohnstonInstructorCommented:
The router doesn't need a static route for a directly connected network. It already knows about those since it's directly connected to them.

As fas as adding a static route, the fields are:

Destination address - The IP address of the network/device you need to get to.
Subnet mask - The mask used with the address above.
Gateway address - The IP address of the next device (router) you would go through to get to the destination.
LAN/WAN - Which interface you will go out of while going to the destination.

But if a 192.168.0.0 device is unable to get to a 68.255.169.0 device I suggest verifying your end station IP addresses, masks and default gateways.

-Don
0
 
epylkoCommented:
As well as NAT and any bogon access lists.

-Eric
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now