Networking Issues...

4 posts / 0 new
Last post
Offline
Last seen: 12 years 2 weeks ago
Joined: Dec 20 2003 - 10:38
Posts: 10
Networking Issues...

Well, I'm having routing problems that I can't seem to alleviate. Simply put, I am able to ping all devices on one side of the network, but the other side of the network can ping none of the devices on the other side of the network except the two ethernet ports on the router itself.

I am using two linksys wireless routers in this project, one is a Linksys BEFW11S4 running firmware version 1.52.02 from Linksys and the other is a Linksys WRT54G running Firmware Version: Alchemy-V1.0 v3.37.6.8sv from SveaSoft.

The BEF11S4 will be refered to as "Linksys" and the WRT54G refered to as "SveaSoft" respectively.

The Linksys router is connected to the internet via the WAN port and the routes outside traffic to the private network on the inside (192.168.1.0 network). The SveaSoft router is connecting wirelessly to the Linksys router. The wireless link is part of the 192.168.1.0 network and is then routing traffic to the 192.168.2.0 network.

All devices on the 192.168.2.0 network are able to communicate with all devices on the 192.168.1.0 network via a static route. The devices on the 192.168.1.0 network attempt to ping devices on the 192.168.2.0 network they get destination unreachable responses. Both routers have static routes to each other which is what is confusing me about this situation. I can ping both addresses on my SveaSoft router, 192.168.1.2 and 192.168.2.1, from the 192.168.1.0 network, but that is it.

My goal is to be able to do port forwarding so that my servers here on the 192.168.2.0 network can be reached from the outside world, but I'm running into this roadblock that is killing me.

Any help would be greatly appreciated.

Offline
Last seen: 6 years 2 months ago
Joined: Sep 16 2004 - 02:44
Posts: 274
Have you tried turning dhcp o

Have you tried turning dhcp off on the 192.168.2 network and keeping the whole network on the .1 subnet?

cwsmith's picture
Offline
Last seen: 9 months 2 weeks ago
Joined: Oct 13 2005 - 08:23
Posts: 699
I agree -- two routers trying

I agree -- two routers trying to assign DHCP addresses are probably conflicting. Turn off DHCP on one router and let it take assignments from the first (the one connected closest to the Internet source).

Any reason you couldn't just use a 10/100 switch in place of the second router? It won't try to assign DHCP, and you can probably get one with more ports than the routers have anyway.

Offline
Last seen: 12 years 2 weeks ago
Joined: Dec 20 2003 - 10:38
Posts: 10
Re: I agree -- two routers trying

cwsmith wrote:
I agree -- two routers trying to assign DHCP addresses are probably conflicting. Turn off DHCP on one router and let it take assignments from the first (the one connected closest to the Internet source).

Any reason you couldn't just use a 10/100 switch in place of the second router? It won't try to assign DHCP, and you can probably get one with more ports than the routers have anyway.

I'm doing wireless routing between two buildings. The building on the .1 subnet has the internet connection, the building with the .2 subnet is getting connectivity to the internet via the .1 subnet. I need the .1 side of things to be able to do port forwarding to the .2 side of the network for servers in this building that need to be seen by the outside world. DHCP isn't the problem, the problem is in the routing itself. .2 can see all .1 addresses, but .1 can only see the router's .2 address.

Log in or register to post comments