Be and Cisco 877 confusion. Can ping the Be endpoint, but nothing else

growse · 1 Oct 2008 at 11:34

Ok, so my Be line is activated, and I'm trying to get my Cisco 877 working on it. Be seem to have screwed up shipping my BeBox and info to me, so don't have anything to work with. I've asked for 8 static IP addresses and had to phone up the tech support to get what they were.

So, I followed a few guides on the internet about setting up the correct ATM0 and ATM0.1 interface. The interface comes up great, and the sh dsl interface command tells me that I'm synched at 16400 kbps down and 1188kbps up. The problem is getting connectivity. I've been told that the ip addresses I have are 93.97.176.164-171. However, looking at the various subnet calculators, this seems to span across the 93.97.176.160/29 and 93.97.176.168/29 subnets. So is this correct, or has the tech support guy told me wrongness?

If I configure the ATM0.1 interface with the address of 93.97.176.164 255.255.255.248, I can ping the endpoint, which I was told was 93.97.176.1. However, I can't ping anything else on the internet. If I set it to dhcp, I don't get an ip address.

I don't have my exact config to hand (I'm at work, it's at home), but the relevant bits look something like:

Code:

interface ATM0
no ip address
ip virtual-reassembly
no atm ilmi-keepalive
dsl operating-mode auto
!
interface ATM0.1 point-to-point
ip address 93.97.176.164 255.255.255.248
ip nat outside
ip virtual-reassembly
no snmp trap link-status
atm route-bridged ip
pvc BeThere 0/101
no oam-pvc manage
encapsulation aal5snap
!
ip route 0.0.0.0 0.0.0.0 ATM0.1
!
ip nat inside source list 102 interface ATM0.1 overload
!
access-list 102 permit ip 192.168.0.0 0.0.0.255 any

Moley · 1 Oct 2008 at 11:43

I am using a Cisco 837 on a standard ADSL Max line, if you need a hand getting yours set up then post a copy of the config here and I'll check it over for you.

EDIT: I think you need to configure your Ethernet interface to use the address given to you by your ISP and set your atm interface to negotiate an address. My config (the relevant bits) is like this:

interface Ethernet0
ip address 78.32.4.217 255.255.255.248 (Address provided by ISP)

interface ATM0
no ip address
no atm ilmi-keepalive
dsl operating-mode auto
cdp enable
pvc 0/38
encapsulation aal5mux ppp dialer
dialer pool-member 1

interface Virtual-Template1
ip unnumbered Ethernet0
peer default ip address pool DIAL-IN
ppp encrypt mppe auto required
ppp authentication ms-chap ms-chap-v2
!
interface Dialer1
ip unnumbered Ethernet0
encapsulation ppp
dialer pool 1
dialer-group 1
ppp authentication chap callin
ppp chap hostname xxxxxxxxxxxxxxxxxx
ppp chap password 7 yyyyyyyyyyyyyyy
ppp pap sent-username xxxxxxxxxxxxxxxxxxxx password 7 yyyyyyyyyyyy
!
ip local pool DIAL-IN 78.32.4.221
ip route 0.0.0.0 0.0.0.0 Dialer1

Also don't forget to enter the "ip routing" command in configure terminal.

Hope this helps.

growse · 1 Oct 2008 at 12:20

There's no Ethernet0 on the 877, only VLAN1. And I had an 837 before on Zen and it seemed to work just fine negotiating the WAN ip address and setting the Ethernet0 to be the local RFC1918 address of the internal network.

I want to NAT, not to bridge, even though I've got 8 static IPs.

mike1210 · 1 Oct 2008 at 13:28

on mine with Zen I've always had to hardwire it to the IP. DHCP and auto doesn't work for me. I didn't look into it too much as it works fine hardwired but that may help. EDIT: Just read the above yeah seems to be crossing 2 ranges try 93.97.176.166 out of that range or maybe 93.97.176.174 assuming of course the router IP is one below the broadcast (with Zen it is)

iwrox · 1 Oct 2008 at 14:09

Hi there,

Just set my 877W up on Be*

ip route 0.0.0.0 0.0.0.0 ATM0.1 should be ip route 0.0.0.0 0.0.0.0 <GATEWAY IP>

See what happens once youve sorted that

Also for refrence below is my working ATM config.....

interface ATM0
no ip address
no atm ilmi-keepalive
dsl operating-mode auto
!
interface ATM0.1 point-to-point
ip address <myip> 255.255.248.0
ip nat outside
ip virtual-reassembly
atm route-bridged ip
pvc 0/101
oam-pvc manage
encapsulation aal5snap
!
!
interface FastEthernet0
!
interface FastEthernet1
!
interface FastEthernet2
!
interface FastEthernet3
!
interface Dot11Radio0
no ip address
shutdown
speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0 54.0
station-role root
!
interface Vlan1
ip address 192.168.0.100 255.255.255.0
ip nat inside
ip virtual-reassembly
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 93.96.164.1

growse · 1 Oct 2008 at 14:15

iwrox said:
interface ATM0.1 point-to-point
ip address <myip> 255.255.248.0
ip nat outside
ip virtual-reassembly
atm route-bridged ip
pvc 0/101
oam-pvc manage
encapsulation aal5snap

Interesting how you've set the submask of the ip address the submask that I was given for the Be gateway. Seems a bit quirky, unless you really do have a huge subnet

I'll try various options when I get back and find out.

iwrox · 1 Oct 2008 at 14:20

Thats what Be* tell you to use for some reason!

tolien · 1 Oct 2008 at 17:23

Be do some funky stuff with their network. I've only got a single IP with them (for now), and the WAN interface is supposed to be part of a /22.
The relevant bits of my config are more or less identical to iwrox's, except I had to add atm vc-per-vp 128 to ATM0 to get it to accept pvc 0/101.