Networking Forums

Networking Forums > Network Hardware > Network Routers > Alright, new issue.. Help!

Reply
Thread Tools Display Modes

Alright, new issue.. Help!

 
 
ValeX
Guest
Posts: n/a

 
      04-12-2006, 02:50 PM
Ok, so im somewhat new at this.. I'll try to explain what im doing..

Internet(65.x.x.x) -> Firewall (192.168.1.x) -> (192.168.1.4) internal
Router (192.168.4.x)

Does this make sense?
Basically, we have a 192.168.1.x network here, and I am trying to add
an internal router (linkysys RV042). The WAN of the router is
192.168.1.4 and the lan is 192.168.4.x

I have had some success, but its weird. If I set the router in
'gateway' mode, I can get internet on a computer on the 4.x network
just fine. BUT, the 192.168.1.x network cannot see the 192.168.4.x
computer. If i set the router to 'router' mode, I can now see the
192.168.4.x computer from the 192.168.1.xcomputer (there is a route
that was setup for me in the managed firewall....). BUT I cannot now
get internet from a 192.168.4.x machine! HELP!!!!!

 
Reply With Quote
 
 
 
 
ValeX
Guest
Posts: n/a

 
      04-13-2006, 12:57 PM
No one can help me?

 
Reply With Quote
 
Harry
Guest
Posts: n/a

 
      04-13-2006, 06:27 PM
I haven't used routing before. So, you can take my comments or not.

It sounds like you must set routing mode to 'router.' Then, you must
configure your router to do the router you require. I suspect that you
may require static routing, but am not certain. Instructions from
RV042 user manual follow. Sorry can't be more helpful -- as with
actual experience with this issue. I began to set up routing once, but
found a way around it before I had it working.

Static Routing
You will need to configure Static Routing if there are multiple routers
installed on your network. The static routing function determines the
path that data follows over your network before and after it passes
through the Router.
You can use static routing to allow different IP domain users to access
the Internet through this device. This is an advanced feature. Please
proceed with caution.
This Router is also capable of dynamic routing (see the Dynamic Routing
tab). In many cases, it is better to use dynamic routing because the
function will allow the Router to automatically adjust to physical
changes in the network's layout. In order to use static routing, the
Router's DHCP settings must be disabled.
To set up static routing, you should add routing entries in the
Router's table that tell the device where to send all incoming packets.
All of your network routers should direct the default route entry to
the Linksys Router.
Enter the following data to create a static route entry:
1. Destination IP: Enter the network address of the remote LAN segment.
For a standard Class C IP domain, the network address is the first
three fields of the Destination LAN IP, while the last field should be
zero.
2. Subnet Mask: Enter the Subnet Mask used on the destination LAN IP
domain. For Class C IP domains, the Subnet Mask is 255.255.255.0.
3. Default Gateway: If this Router is used to connect your network to
the Internet, then your gateway IP is the Router's IP Address. If you
have another router handling your network's Internet connection, enter
the IP Address of that router instead.
4. Hop Count (max. 15): This value gives the number of nodes that a
data packet passes through before reaching
its destination. A node is any device on the network, such as switches,
PCs, etc.
5. Interface: (LAN, WAN1, WAN2/DMZ) Interface tells you whether your
network is on the LAN or the WAN, or the Internet. If you're
connecting to a sub-network, select LAN. If you're connecting to
another network through the Internet, select WAN.
Click Add to list to add a route entry or click Delete Selected IP to
delete the static route entry.
Click the Save Settings button to save the Routing settings, click the
Cancel Changes button to undo your changes or click the Show Routing
Table button to view the current routing table.

 
Reply With Quote
 
RP
Guest
Posts: n/a

 
      04-14-2006, 08:36 PM
ValeX wrote:

> Ok, so im somewhat new at this.. I'll try to explain what im doing..
>
> Internet(65.x.x.x) -> Firewall (192.168.1.x) -> (192.168.1.4) internal
> Router (192.168.4.x)
>
> Does this make sense?
> Basically, we have a 192.168.1.x network here, and I am trying to add
> an internal router (linkysys RV042). The WAN of the router is
> 192.168.1.4 and the lan is 192.168.4.x
>
> I have had some success, but its weird. If I set the router in
> 'gateway' mode, I can get internet on a computer on the 4.x network
> just fine. BUT, the 192.168.1.x network cannot see the 192.168.4.x
> computer. If i set the router to 'router' mode, I can now see the
> 192.168.4.x computer from the 192.168.1.xcomputer (there is a route
> that was setup for me in the managed firewall....). BUT I cannot now
> get internet from a 192.168.4.x machine! HELP!!!!!


Sounds like your Firewall (192.168.1.1?) address has the wrong netmask
on it. It shouldn't be able to see the 4.X network in bridge mode,
if it has the correct netmask.

RP
 
Reply With Quote
 
ValeX
Guest
Posts: n/a

 
      04-17-2006, 06:28 PM
Well.. New problem...

So, I talked to the firewall managers, and they said that they only
allow 192.168.1.x addresses access to internet, so I got them to open
that up for the 4.x machines. So now, in 'router' mode (no nat) I can
get out to the internet!! and the internet can get to me!! yay!

BUT!!! I still cannot ping a 192.168.1.x machine from the 4.x
machines. When I ping it, it gets to the 1.x machine, but it never gets
back to the 4.x machine, any idea why?

 
Reply With Quote
 
RP
Guest
Posts: n/a

 
      04-18-2006, 04:52 AM
ValeX wrote:
> Well.. New problem...
>
> So, I talked to the firewall managers, and they said that they only
> allow 192.168.1.x addresses access to internet, so I got them to open
> that up for the 4.x machines. So now, in 'router' mode (no nat) I can
> get out to the internet!! and the internet can get to me!! yay!
>
> BUT!!! I still cannot ping a 192.168.1.x machine from the 4.x
> machines. When I ping it, it gets to the 1.x machine, but it never gets
> back to the 4.x machine, any idea why?
>


The 1.x machines need to have a static route pointing at the
4.x network, because the default route is the opposite direction.

RP
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
No logon server available - Windows 2003 Trust Issue? NS Issue? newsgroups.jd@gmail.com Windows Networking 15 08-21-2006 07:38 PM
Senao 2611CB3+Deluxe setup issue, network configuration issue, orboth? RWM Wireless Internet 0 01-27-2006 06:00 PM
3 NIC IP routing issue & local dhp client issue Grimmo' Windows Networking 6 05-04-2005 10:19 AM
Alright, here's a FECN question for you guys... Dood Network Routers 0 12-20-2004 10:51 PM
1. Redhat linux 7.2 issue 2. Redhat enterprise linux issue Moo Linux Networking 0 08-26-2004 10:02 AM



1 2 3 4 5 6 7 8 9 10 11