some comments / questions below: -----Original Message----- From: Ben Hockenhull [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 18, 2001 6:46 PM To: Chuck Larrieu Cc: [EMAIL PROTECTED] Subject: RE: ADSL config [7:23456]
At 6:22 PM -0700 10/18/01, Chuck Larrieu wrote: >the following was taken from a working configuration. I do not have the >bridging configuration handy, but I have bridged using DSL successfully. > >to bridge you need to configure IRB and create a BVI that will have your >public IP address. It will also be the interface for NAT outside. The DSL >link will be part of the bridge-group. Do I need to bridge, though? It seems to me, and maybe I'm being dumb, that I should be able to configure the pertinent details on the interface, bring it up, and things should work. I'm not clear on why I'd need to use CRB or IRB at all. CL: the DSL device should bridge - yes. what would you do if you were using the carrier DSL bridge? You would plug the Ethernet output into a hub or switch, plug your other end stations into that hub or switch, and number everything according to the IP scheme your carrier provides. You should be doing the same on your Cisco box. I can only speak to what I have done personally, but my understanding is that you would bridge on the DSL link, and the public IP address would either go on the ethernet link or the BVI. >I also notice that you do not have your encapsulation set. I've never been >clear when or where this is required, so I always throw it in there. I went ahead and set the encap: interface ATM0/0 mtu 1500 no ip address atm vc-per-vp 256 no atm ilmi-keepalive bundle-enable dsl operating-mode auto ! interface ATM0/0.1 point-to-point mtu 1500 ip address 216.162.122.26 255.255.255.248 pvc valuenet 0/35 encapsulation aal5snap ! ! And debug output remains the same. It's also interesting that if I ping the IP I assigned to the interface from an outside host, I get debug output, so the packets are making it to the interface. However, the ping never sees replies. >also - your debug output is showing VPI 0 and VCI 23. is your telco of any >help providing you with the proper pvc info? VPI is 0, VCI is 35. The debug output shows 0x23 for the VCI, which is hex, and converts to decimal 35. CL: DOH! Here's the output of a sho int, in case that reveals anything useful: CL: your ATM/DSL side is working fine. I believe the problem will be corrected at the very least by making the DSL link part of a bridge group and putting the public IP on the ethernet. My preference would be to use a BVI, but that's just me ;-> ATM0/0 is up, line protocol is up Hardware is DSLSAR (with Alcatel ADSL Module) MTU 1500 bytes, sub MTU 1500, BW 160 Kbit, DLY 12800 usec, reliability 248/255, txload 1/255, rxload 1/255 Encapsulation ATM, loopback not set Encapsulation(s): AAL5 AAL2, PVC mode 23 maximum active VCs, 256 VCs per VP, 1 current VCCs VC idle disconnect time: 300 seconds Last input 00:03:51, output 00:07:32, output hang never Last clearing of "show interface" counters 04:39:53 Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: None 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 100 packets input, 10932 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 59 packets output, 4782 bytes, 0 underruns 0 output errors, 0 collisions, 4 interface resets 0 output buffer failures, 0 output buffers swapped out ATM0/0.1 is up, line protocol is up Hardware is DSLSAR (with Alcatel ADSL Module) Internet address is 216.162.122.26/29 MTU 1500 bytes, BW 160 Kbit, DLY 12800 usec, reliability 248/255, txload 1/255, rxload 1/255 Encapsulation ATM 100 packets input, 10932 bytes 34 packets output,2152 bytes 0 OAM cells input, 0 OAM cells output Thanks Ben Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=23468&t=23456 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]