ADSL RFC1483 RBE 7200 2024 private link



Can anyone tell me if this is possible;

I run a 7200 router with an ATM interface that is used for ADSL
subscriber aggregation.
The subscribers run ADSL modems in RFC1483 bridge mode, and each
ADSL/ATM PVC is bridged to a loopback interface on the 7200 with RBE,
as follows;

interface ATM4/0.38 point-to-point
ip unnumbered Loopback0
atm route-bridged ip
pvc 1/38
encapsulation aal5snap

The 7200 is connected to a Catalyst 2924 switch via ethernet. 802.1Q
VLAN trunking is being used between the 7200 and 2924 with multiple
VLANs.

I would like to bridge 1 ADSL subscriber to 1 port on the 2924 in order
to provide a private link between the network connected to the single
port on the 2924 (via another router, 3620) and the network connected
to the remote ADSL modem (another 3620).

The full path looks like this

Subscriber LAN_1 <> 3620 <> ADSL modem in bridge mode <> Carrier ATM
network <> 7200 ATM interface <> 2924 switch <> 3620 <> Subscriber
LAN_2

I have managment access to all network elements with the exception of
the carrier ATM netword (the DSLAM and ATM switch).

The 2 3620s do not have IPSEC IOS images, and there is one application
that does like packets fragmented, so a VPN tunnel is not a good
option.

Is there any way to build a "private link" where the other hosts routed
via the 7200 can not access either of the subscriber LANs, and the
subscriber LANs can not access any networks other than the 2 connected
networks?

.



Relevant Pages

  • Re: Newbie to Replication Subscriptions
    ... (even though on the network share in question "Everyone" had full rights) ... they'd get in that way but not with the localsystem account that is used by ... > publisher reads the files and bcp's them to the subscriber. ... > you are using NT authentication, the SQL Server agent ...
    (microsoft.public.sqlserver.replication)
  • Re: Merge replication error
    ... > The connectivity is fine - which is proven by 4 databases on this same server replicating just fine to the same subscriber. ... >> Looks like a networking issue; when the error occurs, please try pinging the>> distributor from the subscriber, to test your network connectivity and name>> resolution. ... >> Paul Ibison ...
    (microsoft.public.sqlserver.replication)
  • Re: New here... with a problem of course.
    ... I was recently working on some ADSL systems. ... if every subscriber were trying to download large files at the ... the DSLAM shelves. ...
    (comp.dcom.modems.cable)
  • Re: BN Cost saving
    ... The "local loop" IS the subscriber distribution system. ... subscriber lines that include fibre. ... > You also seem to be getting confused between NTL's DSL and BT ADSL, ... > exchange and the subscribers master BT socket. ...
    (uk.rec.naturist)
  • Re: Merge replication data loss
    ... general network error means your network hic cupped. ... Merge replication refreshes the data on the subscriber when you send the ... This could account for the data loss. ...
    (microsoft.public.sqlserver.replication)