pppoe config for 1841

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

mmark751969 - 28 Sep 2008 00:23 GMT

I am trying to get an at&t sticky ip dsl config to work for my
business class client. I have a motorola dsl modem in front of a
cisco 1841 router. The motorola is in bridged mode. Here is the
config pppoe config for the 1841.
Current configuration : 2655 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname
!
boot-start-marker
boot-end-marker
!
logging buffered 52000 debugging
!
no aaa new-model
!
resource policy
!
mmi polling-interval 60
no mmi auto-configure
no mmi pvc
mmi snmp-timeout 180
ip subnet-zero
ip cef
!
!
!
!
ip domain name yourdomain.com
vpdn enable
!
!
username admin privilege 15 secret 5 $1$3Jz9$xEGxyD38I721pyMsGjG2s0
!
!
!
interface FastEthernet0/0
description $ETH-SW-LAUNCH$$INTF-INFO-FE 0$$ETH-LAN$
ip address 192.168.0.1 255.255.255.0
ip nat inside
duplex auto
speed auto
!
interface FastEthernet0/1
description ADSL WAN interface PPOE
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat outside
no ip mroute-cache
duplex auto
speed auto
pppoe enable
no cdp enable
!
interface Dialer1
description ADS Wan Dialer
ip address negotiated
no ip unreachables
ip nat outside
encapsulation ppp
no ip mroute-cache
dialer pool 1
dialer-group 1
no cdp enable
ppp authentication chap callin
ppp chap hostname {sbc email address here}
ppp chap password {password here}
ppp pap sent-username {sbc email address} password {password}
ppp ipcp route default
!
ip classless
ip route 0.0.0.0 0.0.0.0 Dialer1
!
ip http server
ip http authentication local
ip http timeout-policy idle 60 life 86400 requests 10000
ip nat inside source list 10 interface Dialer1 overload
!
access-list 1 remark SDM_ACL Category=2
access-list 1 permit 192.168.0.0 0.0.0.255
access-list 10 permit 10.10.10.0 0.0.0.255
access-list 10 permit 192.168.0.0 0.0.0.255
no cdp run
!
control-plane
!
line con 0
login local
line aux 0
line con 0
login local
line aux 0
line vty 0 4
privilege level 15
login local
transport input telnet
line vty 5 15
privilege level 15
login local
transport input telnet
!
end

Currently this is not working. Wondering if this is an acceptable
pppoe config. Also the adsl interface shows that the ip is
spoofed(when viewing a sh int). Is this a normal occurance.

Reply to this Message

Doug McIntyre - 28 Sep 2008 07:45 GMT

>I am trying to get an at&t sticky ip dsl config to work for my
>business class client. I have a motorola dsl modem in front of a
>cisco 1841 router. The motorola is in bridged mode. Here is the
>config pppoe config for the 1841.

You seem to be missing something..

You either need more here..

>vpdn enable
>!

Or more here, tying this PPPoE instance to use Dialer1..

>interface FastEthernet0/1
> pppoe enable
[quoted text clipped - 4 lines]
> dialer pool 1
> dialer-group 1

> ppp chap hostname {sbc email address here}
> ppp chap password {password here}

And are you sure they are doing CHAP? ISPs typically don't like CHAP,
that means they have to store the passwords in cleartext on their side.
What's a more likely security paydirt, somebody sniffing over the DSL
wire? Or somebody breaching the ISP's database and getting thousands
and thousands of cleartext passwords? They are probably doing PAP.

Easiest to start with is the vpdn-group
vpdn-group 1
request-dialin
protocol pppoe

And
int Fa 0/1
pppoe-client dial-pool-number 1

Reply to this Message

mmark751969 - 29 Sep 2008 10:35 GMT

> >I am trying to get an at&t sticky ip dsl config to work for my
> >business class client. I have a motorola dsl modem in front of a
[quoted text clipped - 35 lines]
> int Fa 0/1
> pppoe-client dial-pool-number 1

Ok - Thanks. How about this:

Current configuration : 2655 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname

boot-start-marker
boot-end-marker
!
logging buffered 52000 debugging
!
no aaa new-model
!
resource policy
!
mmi polling-interval 60
no mmi auto-configure
no mmi pvc
mmi snmp-timeout 180
ip subnet-zero
ip cef
!
!
!
!
ip domain name yourdomain.com
vpdn enable

vpdn-group office
request-dialin
protocol pppoe

!
!
username admin privilege 15 secret 5 $1$3Jz9$xEGxyD38I721pyMsGjG2s0
!
!
!
interface FastEthernet0/0
description $ETH-SW-LAUNCH$$INTF-INFO-FE 0$$ETH-LAN$
ip address 192.168.0.1 255.255.255.0
ip nat inside
duplex auto
speed auto
!
interface FastEthernet0/1
description ADSL WAN interface PPOE
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat outside
no ip mroute-cache
duplex auto
speed auto
pppoe enable
pppoe-client dial-pool-number 1
no cdp enable
!
interface Dialer1
description ADS Wan Dialer
ip address negotiated
no ip unreachables
ip nat outside
encapsulation ppp
no ip mroute-cache
dialer pool 1
dialer-group 1
no cdp enable
ppp authentication pap callin
ppp pap sent-username password 7
ppp ipcp route default
!
ip classless
ip route 0.0.0.0 0.0.0.0 Dialer1
!
ip http server
ip http authentication local
ip http timeout-policy idle 60 life 86400 requests 10000
ip nat inside source list 10 interface Dialer1 overload
!
access-list 1 remark SDM_ACL Category=2
access-list 1 permit 192.168.0.0 0.0.0.255
access-list 10 permit 10.10.10.0 0.0.0.255
access-list 10 permit 192.168.0.0 0.0.0.255
no cdp run
!
control-plane
!
line con 0
login local
line aux 0
line con 0
login local
line aux 0
line vty 0 4
privilege level 15
login local
transport input telnet
line vty 5 15
privilege level 15
login local
transport input telnet
!
end

Reply to this Message

Doug McIntyre - 29 Sep 2008 20:34 GMT

>Ok - Thanks. How about this:
>interface Dialer1
> ppp authentication pap callin
> ppp pap sent-username password 7
> ppp ipcp route default

I don't know how much of this was managled for posting..

ppp authentication chap pap callin
ppp pap sent-username bobuser password bobpass

But otherwise is looking like what it should.

If you have further issues, then you'd want to start debugging PPPoE events
and ppp negotiations.

Reply to this Message