dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
20
share rss forum feed

phardacre

join:2004-01-19
UK
reply to stoz

Re: [Config] Setup Cisco 877 to work with Bt Infinity

Hi Stoz,

I'm assuming you're using the OpenReach VDSL modem.. I've done this on a couple of our lines as they're low traffic and I couldn't justify forking out for a new router for them - we just upgraded all our DSL circuits to Infinity as the ADSL2 signal was a bit ropey whereas Infinity has been rock solid. It's not ideal as the router really can't handle the speeds very well. Ours runs an IPSEC VPN tunnel to another site and that's it, no NAT or anything else too taxing so YMMV.

On your WAN VLAN i/f you don't need an IP, you just need to configure PPPoE client. If you've regraded from ADSL(2+) then you can use the same Dialer i/f you used for that..

Here's a sanitised config:

interface ATM0
 no ip address
 shutdown
 no atm ilmi-keepalive
 pvc 0/38 
  encapsulation aal5mux ppp dialer
 
interface FastEthernet3
 switchport access vlan 10
 
interface Vlan10
 description WAN Interface
 no ip address
 no ip redirects
 no ip unreachables
 no ip proxy-arp
 ip virtual-reassembly
 pppoe enable group global
 pppoe-client dial-pool-number 1
 
interface Dialer0
 description BT PPPoE Link
 mtu 1492
 ip address negotiated
 ip virtual-reassembly
 encapsulation ppp
 ip tcp adjust-mss 1452
 dialer pool 1
 dialer-group 1
 ppp chap hostname <username>@<hg x>.btclick.com
 ppp chap password <password>
 ppp ipcp route default
 

Should do what you want.. I'm using Fa3 for the WAN.. It's not a perfect solution by any means as you'll only get a max of around 30Mb/s downstream before the CPU pegs and your console session turns to treacle but it'll work. Definitely make sure you're not process switching everything otherwise you'll max out at around 15Mb/s.

If you're on a single static IP then you should get that through IPCP based on your PPP username/password. If you've got a /29 then you'll get a dynamic IP through IPCP which will have your /29 routed to it so you have to create a loopback or another VLAN i/f with the router IP address to use it.

Hope that helps,

Paul

stoz

join:2012-03-13

Ok thanks for the help I'll give that a go Paul. We weren't using the router for ADSL before hand, we've got it because we need it for security reasons. I imagine it's better for that reason than the 2wire router.

However, we won't get speeds above 30Mb/s if we do get it working? That wouldn't be great as speedtest tells us we currently get about 38Mb/s and BT have informed us that the speed will be increasing in the future. Are we better off with a Cisco VDSL router?

Edit: also we have a static IP from BT. Do I need to make allowance for this in the config, or will it be assigned to us based on our username / password?


phardacre

join:2004-01-19
UK

No worries Stoz, the 2Wire doesn't do VPN as far as I know so if you need it for that then yes, the 877 is better. Just out of curiosity, why not pick the 871 if it was for Infinity (unless it was one you had laying around)? Firstly, it's cheaper as you don't have the integrated ADSL modem and second it's got a dedicated WAN port which you could run the PPPoE over..

The 877 is designed for ADSL(2+) so didn't need to do anything over 24Mb/s WAN-to-LAN.. We have another one running NAT and that gets about 33 - 34Mb/s on a speed test whereas our 1841s get around 39Mb/s. Obviously, the choice is yours - you have the equipment that will do 30ish Mb/s as it stands or you can get a more expensive model that will handle the extra speed. You only need the VDSL router if you don't want the OpenReach modem as per the 1941 and HWIC-1VDSL thread.

Yeah, I covered the static IP.. It's handled by the "ip address negotiated" command for a single static IP assuming you put in your BT provided username and password rather than a generic "hub" login. If you had "5 static IPs" then you need another VLAN or a Loopback interface with the static IP (and you still need to use the BT username and password I believe) - This is what we have.

Let us know how you get on.

Cheers,

Paul


stoz

join:2012-03-13

Hi Paul,

We checked with an IT support company for a router that would do all we required (after first checking that it met EAL4 certification, which we may require in the future). They assured us that 877 would be fine with VDSL so we went ahead and got it hoping to config it ourselves using SDM. So far I massively prefer using telnet to configure it through the console though!

I didn't realise that it'd be so tricky to get it up and running (well, it's probably fairly straight forward if you're familiar with Cisco, but I'm new to it!) It has been tough finding other people who've done it, and re-creating their success.

Actually the only thing I can't seem to do is get any feedback from the router on where I'm going wrong - logging, debugging etc any idea how I can check why it's not working as currently I just plug it in, hope for the best but I'm literally stumbling in the dark with no idea where it's going wrong.

Many thanks for all your help so far I'll let you know how I get on.


phardacre

join:2004-01-19
UK

Remind me not to use that IT support company then! Yes, I (and I'm sure many others) prefer the command line too. SDM has been superseded by Configuration Professional now I think (see »www.cisco.com/en/US/products/ps9···dex.html) which is a bit better but still can't do everything you can do on the command line.

For logging, look into syslog - very useful if combined with something like splunk. If you're on telnet/SSH, use the "terminal monitor" command to have the logging pumped to your telnet/SSH session ("term no mon" turns it off again).

On the troubleshooting side, there's a lot of debug commands that will help - there's also a lot of useful info on Cisco's website, samples with verification checks that show you that what you just did worked.

Good luck with it, hopefully that config will at least get you up and running - you'll have to set up PAT against the dialer interface too but there's plenty of info on doing that out there.

Cheers,

Paul



OVERKILL

join:2010-04-05
Peterborough, ON
reply to stoz

said by stoz:

Hi Paul,

We checked with an IT support company for a router that would do all we required (after first checking that it met EAL4 certification, which we may require in the future). They assured us that 877 would be fine with VDSL so we went ahead and got it hoping to config it ourselves using SDM. So far I massively prefer using telnet to configure it through the console though!

I didn't realise that it'd be so tricky to get it up and running (well, it's probably fairly straight forward if you're familiar with Cisco, but I'm new to it!) It has been tough finding other people who've done it, and re-creating their success.

Actually the only thing I can't seem to do is get any feedback from the router on where I'm going wrong - logging, debugging etc any idea how I can check why it's not working as currently I just plug it in, hope for the best but I'm literally stumbling in the dark with no idea where it's going wrong.

Many thanks for all your help so far I'll let you know how I get on.

How long have you had this router? The 877 is EOL:
»www.cisco.com/en/US/prod/collate···144.html

(and so is basically its entire obsolete family), so I'm quite surprised somebody recommended it to you. 881, 891 or a 1921/1941 should have been what was pushed your way as far as recommendations go.

cramer
Premium
join:2007-04-10
Raleigh, NC
kudos:8

Indeed. It doesn't even support VDSL. If you're going to have to use an external VDSL modem, there are a lot of better options. (a cisco device with native VDSL will not be cheap... 886VA or 887VA approx. $500(US))