General discussion

Locked

Wireless Multipoint Link - Help!! (LINKSYS)

By jess ·
I am creating a wireless point-to-multipoint network that will link three buildings across an 8 acre estate. Needless to say, using Linksys devices is not the same as using Cisco routers or switches.

The network diagram is available at http://www.unbelievablepolitics.com/networks/wirelessbridge.jpg

Node #1
Start in the center and shares a cable internet connection from a Motorola SB5100 using a Linksys BEFSX41 VPN Router. This router obtains its IP automatically from the ISP on the WAN Port. And provides the following IP subnet 192.168.1.0/24. I've connected a Linksys WAP11 to a lan port on the back of the BEFSX41 Router. Assigned it the IP 192.168.1.250 for administrative purposes. This WAP11 is configured in point-to-multipoint mode. The WAP11 is connected to an outdoor omni-directional +9dB antenna.

Node #2
On the left. Bridges the connection from Node #1 using another WAP11 which is configured as a point-to-point bridge with the IP 192.168.1.251 for administrative purposes. It then connects the interface from the rear of the WAP11 to a Linksys BEFSR41 Routers WAN Port. The BEFSR41 is assigned the WAN IP 192.168.1.252. The BEFSR41 is set with NAT and DHCP Enabled and manages the 192.168.111.0/24 network.

Node #3
On the right. Bridges the connection from Node #1 using another WAP11 which is configured as a point-to-point bridge with the IP 192.168.1.253 for administrative purposes. It then connects the interface from the rear of the WAP11 to a Linksys BEFSR41 Routers WAN Port. The BEFSR41 is assigned the WAN IP 192.168.1.254. The BEFSR41 is set with NAT and DHCP Enabled and manages the 192.168.112.0/24 network.

Everything works well with one exception. I can't ping backwards from either Node #2 or Node #3 to Node #1. Meaning I can't ping 192.168.111.0/24 computers or 192.168.112.0/24 computers. I get full working internet everywhere. I can ping from Node #2 back to Node #1 (i.e. 192.168.111.100 can ping 192.168.1.1). I can ping from Node #3 back to Node #1 (i.e. 192.168.112.100 can ping 192.168.1.1).

The Problem:
I need for all networks (192.168.1.0/24; 192.168.111.0/24; 192.168.112.0/24) to be able to ping each other in all directions.

I've tried entering routing rules to no avail. If anyone has any suggestions your thoughts and comments would be appreciated.

Routers should route no?

Thanks in advance for your time!
Jess

This conversation is currently closed to new comments.

7 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

wi-fi

by airdog07 In reply to Wireless Multipoint Link ...

if the firewall blocking the ping icmp ?

Collapse -

Can't be done with your equipment

by HowardParr In reply to Wireless Multipoint Link ...

Although you state that the IP address for the WAN port of your router is 192.168.1.0/24, generally the x.x.x.0 address (which used to be illegal) is used to denote the network and not used. And I don't believe that it's being assigned by your ISP.

Here's what I think is happening:

The WAN side of your Motorola SB5100 has your public IP address which is assigned by your ISP. The LAN port which, unless you've reconfigured it, should have the IP address 192.168.0.1. This is generally the default private non-routable IP address that is used by most of these types of devices.

The LAN port on your Motorola SB5100 connects to the WAN port of your BEFSX41 router. The BEFSX41 WAN port should get it's IP address from the SB5100, because the SB5100 should be, by default, acting as a DHCP server; again unless you've reconfigured it. Therefore it should have an IP address of 192.268.0.x (probably 192.168.0.2).

But you state that the BEFSX41 has a address of 192.168.1.0, which leads me to believe that you have reconfigured the SB5100, otherwise these two pieces of equipment will not talk to each other.

Now you do not give the subnet masks for the other devices, so I'm left to assume that you are using the same Class C addressing (/24 or 255.255.255.0).

With the IP scheme provided, WAN side of the BEFSX41 router is on the same network as the LAN side - this is not permissable. The router, which is a device that connects two networks, will not ne able to tell which port is the WAN side and which ports are the LAN side.

So, assuming that the WAN port of the BEFSX41 router is actually on the 192.168.0.x network and that the LAN side is on the 192.168.1.x newtork (usually defaults to the 192.168.0.1 IP address, therfore you will have to change it to 192.168.1.1), we can continue.

Back to the WAN port of the BEFSX41 router: IP address of 192168.0.2 (or whatever was supplied by the SB5100), subnet mask of 255.255.255.0, the default gateway IP address should have been set to the IP address of the LAN port of the SB5100 so that it directs all packets destined for the Internet to the SB5100.

Since the BEFSX41 is also the gateway device for the 192.168.1.x network, all devices on that network need to be configured to send all packets, not destined for someplace on the 192.168.1.x network to the BEFSX41 for transmission out it's WAN port. Here's where the crux of your problem is at, which I'll explain later.

All three of the WAP11's are on the same 192.168.1.x network, which is fine. They can have dynamic addresses assigned by the BEFSX41 router or static IP addresses assigned by you. However, since this is a backbone network with no workstations on it I suggest using static IP addresses. It makes it simpler to access the devices if they need to be reconfigured. They will have the same 255.255.255.0 subnet mask and have a default gateway address of 192.168.1.1, the IP address of the LAN side of the BEFSX41 router.

The WAN side of the two BEFSR41 routers are also on the 192.168.1.x network with a 255.255.255.0 subnet mask and a gateway IP address of 192.168.1.1 (Here's the other part of your problem. I'll put them together shortly.)

The LAN side of one of the BEFSR41 is on the 192.168.111.x network (should have an IP address of 192.168.111.1) and the LAN side of the other BEFSR41 router is on the 192.168.112.x network (should have an IP address of 192.168.112.1)

OK...to your problem.

When you ping an address on the 192.168.112.x network from the 192.168.111.x network, the BEFSR41 routers LAN port receives the ping packets on the 192.168.111.x network port and transmits them out the WAN port on the 192.168.1.x network.

BUT the destination IP address is NOT on the 192.168.1.x network so instead of sending the packet to the other BEFSR41 router the packet is sent to the default gateway, the BEFSX41 router which sends it to the SB5100 which tries to pass it out to the internet.

The routers are not TRUE router. In a true router all ports are configured to be on a different network. These devices are hybrid Bridge/Switches. The bridge has the WAN and LAN side IP Address with the WAN side conneted to the WAN port. The LAN side of the bridge is internally connected to the switched ports (generally 4 of them).

If you replace the BEFSX41 with a true router, then it should work, if you address the network segments correctly.

I share my satellite internet access with my neighbors and have run into the same problem. I have another solution to the problem that I will share with you if you would like to write me.

Howard Parr
HowardParr@lycos.com

Collapse -

I'm only an amateur...

by rickydoo In reply to Can't be done with your e ...

But that was so well written that I understood. I think. I haven't set up a network of that complexity yet, so I don't actually know if you're right of course, but nicely written anyway.

Collapse -

disable NAT's and configure proper routes

by somebozo In reply to Can't be done with your e ...

by default all traffic between then WAN and LAN ports of linksys routers get NAT'ed.. So first you need to disable that all together. If you are using local IP's all over..no need for NAT.

Then configure proper routes and everything should work fine

Collapse -

by info In reply to Wireless Multipoint Link ...

you would need a server or router on the system to do dns or straight routing it seems that when you ping it may not actually know where to route its request in the first place - maybe use a pc or server on one of the segments to route ip adresses and pont everything to that

Collapse -

by silagy In reply to Wireless Multipoint Link ...

One thing i would do is set up a 10.10.10.? ip sceme.when a device is set as a reapter or acess point you cant ping that device anymore because its an acess point. also are you using dhcp?

Collapse -

Trash the routers...

by davew In reply to Wireless Multipoint Link ...

The problem is that you have Multiple NATS inside your network..

Trash both of the BEFSR41's.

Why are you running multiple subnets? Is your concern security?

If Not:
Let the access points at the remote sites be just that Access points that distribute address's from the .1 range and be done with it.

Back to Networks Forum
7 total posts (Page 1 of 1)  

Related Discussions

Related Forums