RE: Customers in the same PVC Bridge ?

> On Thu, 20 Mar 2003, Eric Kagan wrote:
>
> > I somewhat recall a discussion about customers in the same
> bridge not being
> > able to see each other ? I have tried to look it up but searching for
> > bridge anything produces just a few trillion results.
> Basically I have 2
> > customer on the same PVC from Verizon that can't see each other. We are
> > using RFC 1483 Bridging with IP LLC Encaps. I can access the
> main customer
>
> What are you using on the router side ? With RBE they should be able to
see each other. Maybe.

We are using RBE. Both customers are on PVC 301 and cannot see WAN/LAN or
each other. We tested from PVC 321 and we can access both WAN and LAN.

>
> Oh -- wait, I know. If the WAN IP's on your DSL bridge are in the (say)
> 192.168.10.x net block, you will need a route in the CPE for
> 192.168.100.0/24 back to your router.

DId you mean for both of these to be the same subnet 100.x ? We do use a
Multipoint interface for WAN and they are part of the same subnet.
>
> Otherwise, if the WAN port on the CPE has a 255.255.255.0 netmask, it will
> send the trafic to the other DSL line out the port and expect it to go
> directly to it's destination, instead of to the router.

Here is the setup - we have tried multiple options and it doesn't work
still.

Main Site - GreatSpeed 1530 Router - RFC 1483 Bridgeing IP LLC - No NAT
WAN: 66.203.77.79 /24
LAN: 66.203.74.33 /29
There is a secure site at 74.34 that everyone in the world can access except
the remote site

Remote Site - GreatSpeed 1530 Router - RFC 1483 Bridgeing IP LLC - NATP Mode
WAN: 66.203.77.78 /24
LAN: 192.168.0.x

When the remote site tried to access the Main Site routes would get
automatically added to the Great Speed as shown below. I didn't belive it
until I deleted the routes myself, rebooted the router, checked the routing
table and then had them access the App and recheck the route table.

Here is what used to happen -

Destination Netmask Gateway Interface
0.0.0.0 0.0.0.0 66.203.77.1 ss0
66.203.74.32 255.255.255.255 66.203.77.79 ss0
66.203.74.33 255.255.255.255 6 6.203.77.79 ss0
66.203.77.0 255.255.255.0 66.203.77.78 ss0
192.168.0.0 255.255.255.0 192.168.0.254 br0
127.0.0.1 255.0.0.0 127.0.0.1 lo0

Above didn't work. We deleted the 74.x routes and put a static route as per
the suggestion above (I believe this is how it was meant)

This is what we added -

Destination Netmask Gateway Interface
0.0.0.0 0.0.0.0 66.203.77.1 ss0
66.203.74.32 255.255.255.248 66.203.77.78 ss0
66.203.77.0 255.255.255.0 66.203.77.78 ss0
192.168.0.0 255.255.255.0 192.168.0.254 br0
127.0.0.1 255.0.0.0 127.0.0.1 lo0

Neither scenario works and we can't figure it out. We have changed routers,
firewalls, etc. Both sites can access anything on the internet in the world
expect this App at the main site. Any other ideas or info would be
appreciated.

Thanks
Eric

Recent archives of the list can be found at
http://www.westnet.com/verizonisp/
Send 'unsubscribe' in the body to verizonisp-request@westnet.com to leave.
Received on Tue Mar 25 11:15:41 2003