12-09-2010 09:41 AM - edited 03-04-2019 10:44 AM
I'm hoping someone can look over my config and tell me if there is anything wrong with it or that would cause my ISP's Network to suddenly "crash" as they put it. What is happening is, it will connect just fine but my ISP keeps shutting off my port because they're saying other people on their network (customers) are suddenly looking to our router for PPPOE Authentication thus causing them down time. I have told them over and over again there is nothing in my config that is causing this and it is a problem on their side but they just shut off my port until I make "proper changes" so this doesn't happen anymore.
I have NEVER seen or heard of such a problem in me entire 12 years in IT. Anyways, thanks for any input anyone can give me.
gaspaso#show run
Building configuration...
Current configuration : 2986 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname gaspaso
!
boot-start-marker
boot-end-marker
!
enable password 7 052F5E5D1758540101083D
!
no aaa new-model
!
!
dot11 syslog
!
!
ip cef
!
!
!
no ip domain lookup
!
multilink bundle-name authenticated
vpdn enable
!
vpdn-group 1
request-dialin
protocol pppoe
!
chat-script MYCHAT ABORT ERROR "" "AT X0\n"
!
!
username gaspaso password 7 1536535E323E312C303E1F
!
!
crypto isakmp policy 1
encr aes 256
authentication pre-share
group 5
crypto isakmp key <REMOVED> address 65.121.182.2
crypto isakmp keepalive 600 5 periodic
!
!
crypto ipsec transform-set VPNSET esp-aes 256 esp-sha-hmac
!
crypto map VPNMAP 1 ipsec-isakmp
set peer <REMOVED>
set transform-set VPNSET
match address 115
!
archive
log config
hidekeys
!
!
!
!
bba-group pppoe global
!
!
interface FastEthernet0
description Fibre Network PPPOE
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
ip virtual-reassembly
ip route-cache flow
no ip mroute-cache
duplex auto
speed auto
pppoe enable group global
pppoe-client dial-pool-number 1
no cdp enable
crypto map VPNMAP
!
interface FastEthernet1
ip address 172.20.44.155 255.255.255.248 secondary
ip address 172.30.14.155 255.255.255.248
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat inside
ip virtual-reassembly
no ip mroute-cache
duplex auto
speed auto
no cdp enable
!
interface FastEthernet2
!
interface FastEthernet3
!
interface FastEthernet4
!
interface FastEthernet5
!
interface FastEthernet6
!
interface FastEthernet7
!
interface FastEthernet8
!
interface FastEthernet9
!
interface Vlan1
no ip address
!
interface Async1
ip address negotiated
encapsulation ppp
async mode interactive
!
interface Dialer1
description fibre network
mtu 1491
ip address negotiated
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat outside
ip virtual-reassembly
encapsulation ppp
ip route-cache flow
no ip mroute-cache
dialer pool 1
dialer-group 1
no cdp enable
ppp authentication pap callin
ppp pap sent-username <REMOVED> password 7 0009120507
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 Dialer1
ip route 65.215.140.0 255.255.252.0 Async1
!
!
ip http server
no ip http secure-server
ip nat inside source list 10 interface Dialer1 overload
!
access-list 10 permit 172.16.253.0 0.0.0.255
access-list 10 permit 172.30.14.0 0.0.0.255
access-list 115 permit ip 172.30.14.152 0.0.0.7 10.240.0.0 0.0.255.255
dialer-list 1 protocol ip permit
no cdp run
!
!
!
!
!
!
control-plane
!
!
line con 0
line 1
script connection MYCHAT
login local
modem InOut
transport input all
autoselect during-login
autoselect ppp
stopbits 1
speed 115200
flowcontrol hardware
line aux 0
line vty 0 4
password 7 072B791E781D030D0F1F21
login
!
!
webvpn context Default_context
ssl authenticate verify all
!
no inservice
!
end
gaspaso#
Solved! Go to Solution.
12-09-2010 10:55 AM
There are few minor adjustments that you should do in your config, eg MTU should be 1492 not 1491, vpd-group is not required, but beside that there is nothing that can cause remote equipment to crash.
It seems to me that they are using poor or buggy equipment (could also be Cisco, of course), and do not want to take responsibility in something that really is a problem by their side, as you correctly pointed out.
My recommendation would be to still spend a reasonable amount of time on this, maybe you can take a "debug PPP negotiation" trace, then if they continue to refuse to update their system, switch to a different ISP.
12-09-2010 10:55 AM
There are few minor adjustments that you should do in your config, eg MTU should be 1492 not 1491, vpd-group is not required, but beside that there is nothing that can cause remote equipment to crash.
It seems to me that they are using poor or buggy equipment (could also be Cisco, of course), and do not want to take responsibility in something that really is a problem by their side, as you correctly pointed out.
My recommendation would be to still spend a reasonable amount of time on this, maybe you can take a "debug PPP negotiation" trace, then if they continue to refuse to update their system, switch to a different ISP.
12-09-2010 11:31 AM
Thank you Paolo for your resopnse. I corrected my typo and removed the group. As it turns out, the ISP has given up and just assigned me a straight static. There was clearly something wrong on their side. Again thank you for your response.
- James
12-09-2010 01:14 PM
You're welcome, thank you for the nice rating and good luck!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide