RV120W PPPOE Failure
Hi I've had this setup working for 6 months with an Orange Siemens SE572 adsl modem set to PPPOE Passthrough and the RV120w using pppoe to connect the ADSL
But 3 days ago it stopped working nothing has changed on either device.
Here are the logs can anyone help me out??
[router][System][NIMF] nimfAdvOptSetWrap: NIMF table is NimfTrigger
[router][System][PLATFORM] pppoeMgmtTblHandler: pppoe enable failed
[router][System][PLATFORM] pppoeMgmtDBUpdateHandler: error in executing database update handler
[router][System][NIMF] nimfAdvOptSetWrap: NIMF table is NimfTrigger
I have factory reset the rv120w and redone the config but still get this error.
Thanks
It would be a good idea for you to place a call to our Cisco Small Busiiness Support Center and open up a case for
this issue that youare having. The number is 1-866-606-1866.
THANKS
Similar Messages
-
Rp-pppoe problem (probability of the dialing's failure)
network environment: adsl
i use rp-pppoe to dial. sometimes the 'pppoe-start' was 'TimeOut'. In the process of 'pppoe-start', there was any signal of dialing on my modem(the 'data indicator light' of the modem is always off).
And i have to reboot my computer and try 'pppoe-start' again, there's a chance that 'connected'.
error.log:
pppoe: Timeout waiting for PADO packets
pppoe: Timeout waiting for PADO packets
pppoe: Timeout waiting for PADO packets
message.log:
pppd[2558]: pppd 2.4.4 started by root, uid 0
pppd: Using interface ppp0
pppd: Connect: ppp0 <--> /dev/pts/0
pppd: LCP: timeout sending Config-Requests
pppd: Connection terminated.
pppd: Modem hangup
pppd: Exit.
pppoe-connect: PPPoE connection lost; attempting re-connection.
any sugesstion, please?x33a wrote:
could be a line problem, modem problem or server side problem.
log into your modem, and post your line stats (snr, attenuation, etc.)
but i had tried to dial in my XP os , there was not any problem. So i believe the line and the modem are ok. and thanks for your reply -
Error message pops up saying "Network Connection could not find a PPPoe Server.
I am trying to update my wife's iBook, 2,1 for my mom to use. It is running OS 10.6.8. Every time I wake up the computer an error message pops up saying "Network Connection could not find a PPPoe Server." It does it periodically when the computer is on. It will drive my mom nuts and worry her. Can anyone help me stop this from happening?
Thanks,
KCHello kevinfromwauwatosa,
Thanks for the question. The following article provides the most relevant information to your issue:
Troubleshooting "A connection failure has occurred", "The specified server could not be found" or similar messages
http://support.apple.com/kb/TS1843
For additional information see this resource:
Mac OS X: Troubleshooting a PPPoE Internet Connection
http://support.apple.com/kb/TS1871
Thanks,
Matt M. -
RVL200 won't auto-reconnect to Internet after power loss (PPPoE)
My RVL200 firmware 1.1.7 is configured for PPPoE. The connection to the Internet is via an ATT (SBC) DSL line using a Siemens Slipstream 4100 modem. The 4100 is configured to allow the PPPoE connection to be managed by the router. The RVL200's PPPoE fails to automatically reconnect to the Internet after a power loss (or if I click Disconnect on the RVL200's web page). This is true for both the Connect on Demand and Keep Alive PPPoE alternatives. In either case, I have to go to the router's web screen and manually click "Connect" to force a reconnection. The LAN is populated by Win XP SP2 systems.
Is there some special configuration needed on the LAN, in the RVL200's routing table, or in the modem to allow automatic reconnection to occur? Obviously it is undersirable to have to give out the RVL200 password to everyone who might need to force a reconnect after a power loss.
Neither the RVL200 Admin Guide not the Users Guide has any useful information on this issue.I have to manually reconnect it. This issue came up when testing what would happen with an RVL200 in a power failure - whether it would automatically reconnect. I don't expect a lot of power failures, but I do want the network to reconnect automatically rather than have to count on someone knowing how to do it and having the apssword.
Am I correct that it is supposed to automatically re-establish the PPPoE connection?
What triggers the reconnection? -
Connecting a modem, problem solving PPPOA
Hi everyone,
I've purchased the Airport Extreme (dual) and I've also got a new Broadband Package on the way due to my last ISP being a failure!
The ISP is PPPOA, as was my last one, and as far as I can see the Airport Extreme has no support for this. Only PPPOE.
I also have a Netgear DG834G, which I was planning to use as a modem, but since the airport can't support PPPOA, that's out of the window, right?
1. Will using the Airport as a bridge and connecting to it cause any problems (speed decreases etc) with the internet?
2. Is is best if I purchase a Vigor 120 which will provide a PPPOA to PPPOE bridge, therefore solving the problem? Or is this not needed and will provide no advantage?
Any ideas welcome, got a few days to get it solved!
Thanks,
Ste.The ISP is PPPOA, as was my last one, and as far as I can see the Airport Extreme has no support for this. Only PPPOE.
That is correct. The AirPorts do not support PPPoA to provide user credentials to the ISP. You would require another device: modem, another router, or your computer that support PPPoA to provide these.
I also have a Netgear DG834G, which I was planning to use as a modem, but since the airport can't support PPPOA, that's out of the window, right?
Not necessarily. You could connect the AirPort Extreme Base Station (AEBS) directly to one of the Netgear's LAN ports with the AEBS configured as a bridge. This would allow the Netgear to provide both NAT & DHCP services for the entire network.
1. Will using the Airport as a bridge and connecting to it cause any problems (speed decreases etc) with the internet?
No, as a bridge, the AEBS would become a "passive" device. -
hi folks
after the recent upgrade to rp-pppoe, a few issues have cropped up.
firstly, i have the following entries in my crontab:
56 07 * * * /usr/sbin/pppoe-stop
57 07 * * * /usr/sbin/pppoe-start
pppoe-stop works fine, but after 1 minute, pppoe-start fails to connect, and i get
Timeout waiting for PADS packets
if i manually use pppoe-start, it connects fine.
secondly, i see these in my log (only started showing after the upgrade)
pppd[2756]: Couldn't increase MTU to 1500
pppd[2756]: Couldn't increase MRU to 1500
though it doesn't seem to affect the connection.
one thing i noted is that previously, on pppoe-stop, there was this entry in the log
pppoe[1937]: Sent PADT
but since the upgrade, PADT isn't being sent anymore. could it be the reason for the reconnect failure?
could someone please help me out.@ ise,
just tried that and it worked. now it is exhibiting the older behaviour (which is good).
here's a comparison of the logs:
with rp-pppoe 3.10-1
pppd[1915]:pppd[1915]: pppd 2.4.4 started by root, uid 0
pppd[1915]: Using interface ppp0
pppd[1915]: Connect: ppp0 <--> /dev/pts/4
pppoe[1918]: PADS: Service-Name: ''
pppoe[1918]: PPP session is 15471 (0x3c6f)
pppd[1915]: CHAP authenication succeeded: CHAP authentication success, unit 399
pppd[1915]: CHAP authentication succeeded
kernel: PPP BSD Compression module registered
pppd[1915]: Cannot determine ethernet address for proxy ARP
pppd[1915]: local IP address xxx.xxx.xxx.xxx
pppd[1915]: remote IP address xxx.xxx.xxx.xxx
with rp-pppoe 3.10-2 with LINUX_PLUGIN=/usr/lib/rp-pppoe/rp-pppoe.so set:
kernel: PPP generic driver version 2.4.2
kernel: NET: Registered protocol family 24
pppd[1916]: Plugin /usr/lib/rp-pppoe/rp-pppoe.so loaded.pppd[1916]: RP-PPPoE plugin version 3.10 compiled against pppd 2.4.4
kernel: NET: Registered protocol family 10
kernel: lo: Disabled Privacy Extensions
pppd[1916]: pppd 2.4.4 started by root, uid 0
pppd[1916]: PPP session is 4386 (0x1122)
pppd[1916]: Connected to xx:xx:xx:xx:xx:xx via interface eth0
pppd[1916]: Using interface ppp0
pppd[1916]: Connect: ppp0 <--> eth0
pppd[1916]: Couldn't increase MTU to 1500
pppd[1916]: Couldn't increase MRU to 1500
pppd[1916]: CHAP authentication succeeded: CHAP authentication success, unit 137
pppd[1916]: CHAP authentication succeeded
pppd[1916]: peer from calling number xx:xx:xx:xx:xx:xx authorized
pppd[1916]: Cannot determine ethernet address for proxy ARP
pppd[1916]: local IP address xxx.xxx.xxx.xxx
pppd[1916]: remote IP address xxx.xxx.xxx.xxx
and finally with LINUX_PLUGIN=/usr/lib/rp-pppoe/rp-pppoe.so not set:
pppd[2251]: pppd 2.4.4 started by root, uid 0
pppd[2251]: Using interface ppp0
pppd[2251]: Connect: ppp0 <--> /dev/pts/4
pppoe[2252]: PADS: Service-Name: ''
pppoe[2252]: PPP session is 17062 (0x42a6)
pppd[2251]: CHAP authentication succeeded: CHAP authentication success, unit 421
pppd[2251]: CHAP authentication succeeded
pppd[2251]: Cannot determine ethernet address for proxy ARP
pppd[2251]: local IP address xxx.xxx.xxx.xxx
pppd[2251]: remote IP address xxx.xxx.xxx.xxx
Last edited by x33a (2010-01-19 00:50:27) -
ASR 1002 PPPoE/A Virtual-Access subinterface problem
Hi Guys,
i try to configure a BRAS solution for PPPoE/A termination.
When try to connect a client i receive the following error:
*May 3 00:51:25.043: %LINK-3-UPDOWN: Interface Virtual-Access4, changed state to up
*May 3 00:51:25.046: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access4, changed state to up
*May 3 00:51:25.093: %FMANRP_ESS-4-FULLVAI: Session creation failed due to Full Virtual-Access Interfaces not being supported. Check that all applied Virtual-Template and RADIUS features support Virtual-Access sub-interfaces. swidb= 0x40A8D2CC, ifnum= 29
*May 3 00:51:25.098: %LINK-3-UPDOWN: Interface Virtual-Access4, changed state to down
The problem is related to Virtual-Access subinterface, usually, on standard IOS, i work on full mode
In the Cisco DOC i found this:
"If the subinterface is not configured, the following error message is displayed when creating a session with one of the RADIUS attributes:
*Mar 13 22:04:03.358: %FMANRP_ESS-4-FULLVAI: Session creation failed due to Full
Virtual-Access Interfaces not being supported. Check that all applied Virtual-Template and
RADIUS features support Virtual-Access sub-interfaces. swidb= 0x7FA35A42F218, ifnum= 30
To enhance the scalability of per-user configurations, in many cases, different Cisco AV-pairs are available to place the subscriber interface in a Virtual Routing and Forwarding (VRF) instance or to apply a policy map to the session. For example, use the ip:vrf-id and ip:ip-unnumbered VSAs to reconfigure a user's VRF. For information about enhancing scalability see, "Enhancing the Scalability of Per-User Configurations" section."
Ok i try to pass in radreply the following attribute :
test Cisco-AVPair += ip:vrf-id=RACC_ULL
test Cisco-AVPair += ip:ip-unnumbered=Loopback 199
Nothing don't work same error ....
If remove a "ip-unnumbered" attribute the Virtual-Access coming up but no ip address is assigned
Any ideas ?
Many thx
show ver
Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Version 15.1(3)S2, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Mon 12-Dec-11 15:15 by mcpre
Cisco IOS-XE software, Copyright (c) 2005-2011 by cisco Systems, Inc.
All rights reserved. Certain components of Cisco IOS-XE software are
licensed under the GNU General Public License ("GPL") Version 2.0. The
software code licensed under GPL Version 2.0 is free software that comes
with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such
GPL code under the terms of GPL Version 2.0. For more details, see the
documentation or "License Notice" file accompanying the IOS-XE software,
or the applicable URL provided on the flyer accompanying the IOS-XE
software.
ROM: IOS-XE ROMMON
ASR-01-BS uptime is 6 days, 18 hours, 6 minutes
Uptime for this control processor is 6 days, 18 hours, 8 minutes
System returned to ROM by reload at 22:08:16 UTC Sat Mar 31 2012
System image file is "bootflash:asr1000rp1-adventerprisek9.03.04.02.S.151-3.S2.bin"
Last reload reason: PowerOn
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco ASR1002 (2RU) processor with 1700062K/6147K bytes of memory.
4 Gigabit Ethernet interfaces
1 ATM interface
32768K bytes of non-volatile configuration memory.
4194304K bytes of physical memory.
7757823K bytes of eUSB flash at bootflash:.
Configuration register is 0x2102
show run
aaa new-model
aaa group server radius AAA_RACC_ULL
server-private xx.xx.xx.xx auth-port 1812 acct-port 1813 key xxxxxxx
server-private xx.xx.xx.xx auth-port 1812 acct-port 1813 key xxxxxxx
ip vrf forwarding RACC_ULL
aaa authentication login local_auth local
aaa authentication ppp default group AAA_RACC_ULL
aaa authorization network default group AAA_RACC_ULL
aaa accounting send stop-record authentication failure
aaa accounting update newinfo periodic 60
aaa accounting network default start-stop group AAA_RACC_ULL
aaa accounting connection default start-stop group AAA_RACC_ULL
aaa accounting resource default start-stop group AAA_RACC_ULL
aaa session-id common
aaa policy interface-config allow-subinterface
ip vrf RACC_ULL
description *** VRF Raccolta TEST ***
rd 1:1
vpdn enable
no virtual-template snmp
bba-group pppoe xDSL_PPPoE_ADSL
virtual-template 199
vendor-tag circuit-id service
sessions auto cleanup
interface Loopback199
description *** GW RACCOLTA IP ADSL ***
ip vrf forwarding RACC_ULL
ip address 10.0.0.1 255.255.255.255
interface GigabitEthernet0/0/0
description *** ***
no ip address
no ip proxy-arp
load-interval 30
negotiation auto
interface GigabitEthernet0/0/3.20
description *** DOWNLINK TO DSLAM VLAN ADSL ***
encapsulation dot1Q 20
ip vrf forwarding RACC_ULL
no ip proxy-arp
pppoe enable group xDSL_PPPoE_ADSL
interface Virtual-Template199
description *** PPPoE AUTH ADSL ***
mtu 1488
ip unnumbered Loopback199
peer default ip address pool DYNAMIC_ADSL
ppp authentication chap pap callin
ip local pool DYNAMIC_ADSL 192.168.20.2 192.168.20.254
ip forward-protocol nd
no ip http server
no ip http secure-server
ip route vrf RACC_ULL 0.0.0.0 0.0.0.0 192.168.254.1
ip radius source-interface GigabitEthernet0/0/0.999 vrf RACC_ULL
radius-server vsa send accounting
radius-server vsa send authenticationHi Manuel,
thanks for your answer.
Below the other attribute send from radius to ASR
Framed-MTU := 1488
MS-Primary-DNS-Server := 62.97.32.21
MS-Secondary-DNS-Server := 62.97.33.21
Framed-Protocol := PPP
Service-Type := Framed-User
Framed-Compression := Van-Jacobsen-TCP-IP
If possible i prefer to work using only virtual-template mode without per-user VRF.
I try con configure VT using ip vrf forwarding RACC_ULL and ip unnumbered ( in the same VRF domain ) without success. -
Slow ADSL speed since power failure during trainin...
Hi all,
When our BT total broadband was installed, we had a power failure during the 10 day training period (back in June).
At the start of the training period, we had a speed of 3936 kbps downstream:
16:32:27, 28 Jun. ( 76.590000) DSL noise margin: 20.00 dB upstream, 6.00 dB downstream
16:32:27, 28 Jun. ( 76.520000) DSL line rate: 448 Kbps upstream, 3936 Kbps downstream
which was within the speeds we expected prior to installation (from the BT website for our phoneline):
You can choose BT Broadband now offering:
3Mb *
Estimate download speed
1.5Mb-5.5Mb
Download speed range
However, since the power failure during training (June 2013) we have never managed to get close to that speed, even after consecutive weeks of the HH4 being connected. Our current ADSL stats are pretty representative of what we have achieved ever since:
DSL noise margin: 21.00 dB upstream, 6.10 dB downstream
DSL line rate: 448 Kbps upstream, 1344 Kbps downstream
The connection sometimes holds for weeks on end - other times it cuts out without any cause (from our end at least). For example, earlier today (after an uptime of 11680 mins):
12:11:13, 27 Oct.
(3862269.900000) DSL noise margin: 21.00 dB upstream, 6.10 dB downstream
12:11:13, 27 Oct.
(3862269.830000) DSL line rate: 448 Kbps upstream, 1344 Kbps downstream
12:10:42, 27 Oct.
(3862239.140000) DSL is down after 11680 minutes uptime
12:10:42, 27 Oct.
(3862239.140000) ETHoA is down after 11680 minutes uptime
12:10:41, 27 Oct.
(3862238.020000) PPPoA is down after 11680 minutes uptime [Waiting for Underlying Connection (WAN DSL - Up)]
12:10:39, 27 Oct.
(3862235.790000) PPP LCP Send Termination Request [User request]
We have an external NTE box outside the house so no 'master' socket inside the house.
Any help you can offer would be much appreciated - the internet literally crawls along sometimes!
RichResults from the BTW speedtest:
Download speedachieved during the test was - 1.13 Mbps
For your connection, the acceptable range of speeds is 0.8 Mbps-2 Mbps.
IP Profile for your line is - 1.16 Mbps
Upload speed achieved during the test was - 0.37Mbps
Additional Information:
Upstream Rate IP profile on your line is - 0.45 Mbps -
RV120W WAN interface doesn't automatically re-enable after WAN connection is restored
I found that RV120W WAN interface doesn't automatically re-enable after a cable pull and re-plug. I have to go into the Status->System Summary and click the "Enable" button. Is this normal on this router? Can I prevent that from happening? I would hope this is NOT normal as this would mean that I would have to be on-site and login to the web interface to re-enable it after a power failure or WAN link loss.
Tekliu,
Thanks for the response. But, as I mentioned in my prior post, this is, unfortunately, the designed behavior for this device, at least with a static IP and no ISP login. Cisco Small Business Customer Support was clear on this and didn't even open a ticket. I asked that they submit a feature request to change this behavior in a future release. Of course, they couldn't make any promises.
One possible source of confusion is the different circumstances that can occur. In my testing, the interface does come back up automatically on a soft reboot. It also comes back up automatically if both the RV120W and the upstream (WAN) device are power cycled together. I believe this is because the upstream device comes up much faster and is up before the RV120W. The case we are talking about is when the upstream device is cycled or the cable is pulled while the RV120W stays up. In this case, the WAN port remains disabled until you manually select the button on the status page.
Thanks again for following up on this. -
Hi all,
hoping someone can shed some light on this,
i have an 887va configured to connect to my isp on my test bed. I have configured the router to connect using PPPoA as usual but i am getting LCP TERMREQ packets from my ISP in response to my CHAP responses. no other errors, just a termreq.
Strange thing is , from time to time it does connect but can take hours. I know the username and password are correct as they work straight away when i use a little netgear adsl modem i have here so clearly something else is wrong, i suspect the ISP end but thought i would check here first.
I am not getting any clue as to the reason why im getting termreq back from the ISP , sh ppp stats shows the disconnect reasons as entirely due to '17 received LCP TERMREQ from peer'. Its almost like it doesnt understand my response rather than it being incorrect. i wondered if the secret is being hashed correctly but i cant think of a reason why it wouldnt be I have a crypto map confiured buy not applied as yet..
here is the debug output for the failed session (debug ppp auth, neg and errors)
*Jul 2 06:50:59.837: PPP: Alloc Context [86E2C804]
*Jul 2 06:50:59.837: ppp975 PPP: Phase is ESTABLISHING
*Jul 2 06:50:59.837: Vi2 PPP: Using dialer call direction
*Jul 2 06:50:59.837: Vi2 PPP: Treating connection as a callout
*Jul 2 06:50:59.837: Vi2 PPP: Session handle[F3000030] Session id[975]
*Jul 2 06:50:59.837: Vi2 LCP: Event[OPEN] State[Initial to Starting]
*Jul 2 06:50:59.837: Vi2 PPP: No remote authentication for call-out
*Jul 2 06:50:59.837: Vi2 LCP: O CONFREQ [Starting] id 1 len 10
*Jul 2 06:50:59.837: Vi2 LCP: MagicNumber 0x14194245 (0x050614194245)
*Jul 2 06:50:59.837: Vi2 LCP: Event[UP] State[Starting to REQsent]
*Jul 2 06:51:00.089: Vi2 LCP: I CONFREQ [REQsent] id 103 len 19
*Jul 2 06:51:00.089: Vi2 LCP: MRU 1500 (0x010405DC)
*Jul 2 06:51:00.089: Vi2 LCP: AuthProto CHAP (0x0305C22305)
*Jul 2 06:51:00.089: Vi2 LCP: MagicNumber 0x23918A01 (0x050623918A01)
*Jul 2 06:51:00.089: Vi2 LCP: O CONFACK [REQsent] id 103 len 19
*Jul 2 06:51:00.089: Vi2 LCP: MRU 1500 (0x010405DC)
*Jul 2 06:51:00.089: Vi2 LCP: AuthProto CHAP (0x0305C22305)
*Jul 2 06:51:00.089: Vi2 LCP: MagicNumber 0x23918A01 (0x050623918A01)
*Jul 2 06:51:00.089: Vi2 LCP: Event[Receive ConfReq+] State[REQsent to ACKsent]
*Jul 2 06:51:00.093: Vi2 LCP: I CONFACK [ACKsent] id 1 len 10
*Jul 2 06:51:00.093: Vi2 LCP: MagicNumber 0x14194245 (0x050614194245)
*Jul 2 06:51:00.093: Vi2 LCP: Event[Receive ConfAck] State[ACKsent to Open]
*Jul 2 06:51:00.097: Vi2 PPP: Queue CHAP code[1] id[1]
*Jul 2 06:51:00.117: Vi2 PPP: No authorization without authentication
*Jul 2 06:51:00.117: Vi2 PPP: Phase is AUTHENTICATING, by the peer
*Jul 2 06:51:00.117: Vi2 CHAP: Redirect packet to Vi2
*Jul 2 06:51:00.117: Vi2 CHAP: I CHALLENGE id 1 len 35 from "bras-xxxxx"
*Jul 2 06:51:00.117: Vi2 PPP: Sent CHAP SENDAUTH Request
*Jul 2 06:51:00.117: Vi2 LCP: State is Open
*Jul 2 06:51:00.117: Vi2 PPP: Received SENDAUTH Response FAIL
*Jul 2 06:51:00.117: Vi2 CHAP: Using hostname from interface CHAP
*Jul 2 06:51:00.117: Vi2 CHAP: Using password from interface CHAP
*Jul 2 06:51:00.117: Vi2 CHAP: O RESPONSE id 1 len 37 from "[email protected]"
*Jul 2 06:51:00.861: Vi2 LCP: I TERMREQ [Open] id 104 len 4
*Jul 2 06:51:00.861: Vi2 PPP DISC: Received LCP TERMREQ from peer
*Jul 2 06:51:00.861: PPP: NET STOP send to AAA.
*Jul 2 06:51:00.861: Vi2 PPP: Phase is TERMINATING
*Jul 2 06:51:00.861: Vi2 LCP: O TERMACK [Open] id 104 len 4
*Jul 2 06:51:00.861: Vi2 LCP: Event[Receive TermReq] State[Open to Stopping]
*Jul 2 06:51:02.869: Vi2 PPP: No remote authentication for call-out
*Jul 2 06:51:02.869: Vi2 LCP: Event[Timeout-] State[Stopping to Stopped]
*Jul 2 06:51:02.869: Vi2 LCP: Event[DOWN] State[Stopped to Starting]
*Jul 2 06:51:02.869: Vi2 PPP: Phase is DOWN
here are the relevant parts of the config, dialer 1 is bound to virtual-access 2
controller VDSL 0
interface Ethernet0
no ip address
shutdown
interface ATM0
description BT-Circuit-No...
no ip address
no atm ilmi-keepalive
interface ATM0.1 point-to-point
pvc 0/38
encapsulation aal5mux ppp dialer
dialer pool-member 1
interface Dialer1
description Connection-To-BT-number-ATM0
ip address negotiated
no ip redirects
ip nat outside
ip virtual-reassembly in
encapsulation ppp
dialer pool 1
dialer-group 1
ppp authentication chap pap callin optional
ppp chap hostname [email protected]
ppp chap password 0 mypassword
ppp pap sent-username [email protected] password 0 mypassword
ppp ipcp dns request accept
ppp ipcp route default
ppp ipcp address accept
no cdp enable
dialer-list 1 protocol ip permit
ip nat inside source list PUBLIC-PAT interface Dialer1 overload
ip route 0.0.0.0 0.0.0.0 Dialer1
any ideas appreciated.
Cheers
ShaunIs it possible that MS-CHAP has a limit on the size of usernames and/or password!? Can't we get a better error code than "CHAP Failure id=0x6f" which doesn't seem to be documented anywhere on the Internet?
-
RV120W VPN Setup - basic help needed
Hi all,
I've recently bought a RV 120W Wireless-N VPN Firewall hoping it would ease me in creating VPN and remote connectivity. But I seems to be struggling with this.
Here is my situation.
When I bought my Cisco router I didn't know it had an ethernet port for WAN. I thought it would have a RJ11 compliant port. So now I am having to put the router behind my modem.
I gave my modem's LAN 192.168.2.1 and to RV120W I gave 192.168.2.2.
All PC's are not connected to internet via RV120W. For RV120W, the local IP network is 192.168.1.0. I've set 192.168.1.1 as the management IP of the Cisco RV120W. All the PC's can get internet from the above layout arrangement.
With frustration, I've portforwared all my ports on the modem (except 1 port) to RV120W i.e to IP 192.168.2.2.
If I enable PPTP on RV120W I can ping its port (1723 i remember) from outside. If I connect to port 80 from outside my network, I can get the managemnt interface of the RV120W.
With the help of the RV120W's userguide I managed to create VPN policy stuff via the 'basic VPN Setup' menu. The guides says to use a wizard but there is no wizard for VPN setup.
With that I have even created users (of every type) but I just can't make the connection.
When I use the QuickVPN to connect... its goes from "Connecting", "Activating Policy" again "Connecting" and then a big error saying a couple of things that might have caused the error.
I want to start from the beginning.
Can somebody please help me.
First... what I am I supposed to put in the fields of the following screenshot. Especially the fields "Remote WAN's IP Address", "Local WAN's IP Address" and "Local LAN IP Address".Once I knew about the bridge mode thing from this discussion, I started reading the manual of the modem in regard to the brigde mode setup.
According to the manual, the 'Data' bulb on the modem would be off if the modem is in bridge mode. and I've successfully put the modem on bridge mode I guess. It was pretty easy. I just deleted all the WAN setup rules/configs and began with the initial setup wizard which basically had the option to set the modem to bridge mode. After so, the 'Data' bulb got off meaning the modem is now in bridge mode. I am happy about that
But... still not done.
I put one ethernet cable into of the LAN ports of the modem and put the other end in RV120W WAN port. Logged into to RV120W, configured new PPPoE profile (I have the user and pass details) and attached it to the WAN internet setup config.
I went back to the dashboard of RV120W to see if WAN was up. It didn't. I gave some time. It didn't work. It says 'connecting' but never connects.
What am I doing wrong? Am I putting the cable between the modem and router the right way?
...and also, when the modem is in bridge mode will it forward all packets from lan to wan and vice versa or is it like forwarding packets to all ports once recieved.
(I am learning so much with this RV120W ) -
Rp-pppoe won't connect at boot; LCP timeout
At my college, we all have our own PPP connection to the main server. To start it at boot, I've put the 'adsl' in the daemons array in rc.conf, and this worked for a long time. Then, some time ago, the service failed to start at boot. However, once I've gotten into X, open xterm and type 'pppoe-connect' or '/etc/rc.d/adsl start', it works fine.
Here's the log of when it fails to start up at boot time:
Oct 18 10:22:44 archie PPP generic driver version 2.4.2
Oct 18 10:22:45 archie pppd[3713]: pppd 2.4.4 started by root, uid 0
Oct 18 10:22:45 archie pppd[3713]: Using interface ppp0
Oct 18 10:22:45 archie pppd[3713]: Connect: ppp0 <--> /dev/pts/0
Oct 18 10:23:16 archie pppd[3713]: LCP: timeout sending Config-Requests
Oct 18 10:23:16 archie pppd[3713]: Connection terminated.
Oct 18 10:23:16 archie pppd[3713]: Modem hangup
Oct 18 10:23:20 archie pppd[3713]: Exit
And then, once I do it manually, it works:
Oct 18 10:24:46 archie pppd[4103]: pppd 2.4.4 started by root, uid 0
Oct 18 10:24:46 archie pppd[4103]: Using interface ppp0
Oct 18 10:24:46 archie pppd[4103]: Connect: ppp0 <--> /dev/pts/1
Oct 18 10:24:46 archie pppoe[4104]: PPP session is 25 (0x19)
Oct 18 10:24:47 archie pppd[4103]: EAP: Identity prompt "Name"
Oct 18 10:24:47 archie pppd[4103]: EAP authentication succeeded
Oct 18 10:24:47 archie PPP BSD Compression module registered
Oct 18 10:24:47 archie pppd[4103]: local IP address xxx.xxx.xxx.xxx
Oct 18 10:24:47 archie pppd[4103]: remote IP address xxx.xxx.xxx.xxx
Oct 18 10:24:47 archie pppd[4103]: primary DNS address xxx.xxx.xxx.xxx
Oct 18 10:24:47 archie pppd[4103]: secondary DNS address xxx.xxx.xxx.xxx
Here's my rc.conf:
lo="lo 127.0.0.1"
eth1="eth1 10.0.0.1"
eth0="eth0 000.000.00.0"
INTERFACES=(lo eth0 eth1)
gateway="default gw 10.0.0.1"
ROUTES=(!gateway)
DAEMONS=(syslog-ng network @hal @cups @alsa adsl)
...and my pppoe.conf:
# Ethernet card connected to DSL modem
ETH='eth0'
# PPPoE user name. You may have to supply "@provider.com" Sympatico
# users in Canada do need to include "@sympatico.ca"
# Sympatico uses PAP authentication. Make sure /etc/ppp/pap-secrets
# contains the right username/password combination.
# For Magma, use [email protected]
USER='room20'
# Bring link up on demand? Default is to leave link up all the time.
# If you want the link to come up on demand, set DEMAND to a number indicating
# the idle time after which the link is brought down.
DEMAND=no
#DEMAND=300
# DNS type: SERVER=obtain from server; SPECIFY=use DNS1 and DNS2;
# NOCHANGE=do not adjust.
DNSTYPE=SERVER
# Obtain DNS server addresses from the peer (recent versions of pppd only)
# In old config files, this used to be called USEPEERDNS. Changed to
# PEERDNS for better Red Hat compatibility
PEERDNS=yes
DNS1=
DNS2=
# Make the PPPoE connection your default route. Set to
# DEFAULTROUTE=no if you don't want this.
DEFAULTROUTE=yes
### ONLY TOUCH THE FOLLOWING SETTINGS IF YOU'RE AN EXPERT
# How long pppoe-start waits for a new PPP interface to appear before
# concluding something went wrong. If you use 0, then pppoe-start
# exits immediately with a successful status and does not wait for the
# link to come up. Time is in seconds.
# WARNING WARNING WARNING:
# If you are using rp-pppoe on a physically-inaccessible host, set
# CONNECT_TIMEOUT to 0. This makes SURE that the machine keeps trying
# to connect forever after pppoe-start is called. Otherwise, it will
# give out after CONNECT_TIMEOUT seconds and will not attempt to
# connect again, making it impossible to reach.
CONNECT_TIMEOUT=30
# How often in seconds pppoe-start polls to check if link is up
CONNECT_POLL=2
# Specific desired AC Name
ACNAME=
# Specific desired service name
SERVICENAME=
# Character to echo at each poll. Use PING="" if you don't want
# anything echoed
PING=".
# File where the pppoe-connect script writes its process-ID.
# Three files are actually used:
# $PIDFILE contains PID of pppoe-connect script
# $PIDFILE.pppoe contains PID of pppoe process
# $PIDFILE.pppd contains PID of pppd process
CF_BASE=`basename $CONFIG`
PIDFILE="/var/run/$CF_BASE-pppoe.pid"
# Do you want to use synchronous PPP? "yes" or "no". "yes" is much
# easier on CPU usage, but may not work for you. It is safer to use
# "no", but you may want to experiment with "yes". "yes" is generally
# safe on Linux machines with the n_hdlc line discipline; unsafe on others.
SYNCHRONOUS=no
# Do you want to clamp the MSS? Here's how to decide:
# - If you have only a SINGLE computer connected to the DSL modem, choose
# "no".
# - If you have a computer acting as a gateway for a LAN, choose "1412".
# The setting of 1412 is safe for either setup, but uses slightly more
# CPU power.
CLAMPMSS=1412
#CLAMPMSS=no
# LCP echo interval and failure count.
LCP_INTERVAL=20
LCP_FAILURE=3
# PPPOE_TIMEOUT should be about 4*LCP_INTERVAL
PPPOE_TIMEOUT=80
# Firewalling: One of NONE, STANDALONE or MASQUERADE
FIREWALL=NONE
# Linux kernel-mode plugin for pppd. If you want to try the kernel-mode
# plugin, use LINUX_PLUGIN=/etc/ppp/plugins/rp-pppoe.so
LINUX_PLUGIN=
# Any extra arguments to pass to pppoe. Normally, use a blank string
# like this:
PPPOE_EXTRA=""
# Rumour has it that "Citizen's Communications" with a 3Com
# HomeConnect DSL Modem DualLink requires these extra options:
# PPPOE_EXTRA="-f 3c12:3c13 -S ISP"
# Any extra arguments to pass to pppd. Normally, use a blank string
# like this:
PPPD_EXTRA=""
########## DON'T CHANGE BELOW UNLESS YOU KNOW WHAT YOU ARE DOING
# If you wish to COMPLETELY overrride the pppd invocation:
# Example:
# OVERRIDE_PPPD_COMMAND="pppd call dsl"
# If you want pppoe-connect to exit when connection drops:
# RETRY_ON_FAILURE=noThat's what I have in mine - it may not be necessary, the wiki is ambiguous on the point. It's certainly necessary if using "net-profiles" but may or may not be for net-auto-wireless. I've always added them just in case (it hasn't stopped it working).
However, you *will* need wpa_actiond installed for net-auto-wireless, if you haven't.
The other thing is, as the wiki says:
Note that wpa-config profiles does not work with net-auto-wireless. Convert them to wpa-configsection instead.
So you will probably need to switch your config profile to a configsection one (again, that's what I use and have no issue automatically connecting to any profile networks). -
Software Update fails repeatedly, loses PPPoE
MacBook Pro, 10.6.8, AirPort Extreme router, AT&T DSL.
Trying to update software in last two days has failed within seconds every time I click "install [x] item[s]". Other internet access is fine, and I've made no changes to my router, modem, or DSL service -- all of which have been in place for many months. Downloading songs from iTunes and PDFs from websites works. My iPod Touch seems fine.
Shortly after I start a download from Software Update, progress on the current file stops, my AirPort "time connected" monitor freezes then disappears, and eventually Software Update says it couldn't complete the download. The AirPort icon shows "Looking for PPPoE host" then "Connected via PPPoE" and the time monitor reappears and starts counting again. However, when I restart the download in Software Update, the same thing happens again.
Using advice on apparently related topics, I tried adding OpenDNS servers in my Network config, but it made no visible difference.
(Note: I also lose the PPPoE connection when waking up the laptop, but that's intermittent and I can recover manually if necessary. This Software Update failure is consistent, completely repeatable, and an apparent dead end.)Downloaded and applied the firmware patch directly - on the second attempt it did actually succeeded.
Not sure why this has been such an issue as all other software applies without issue. Any way if you have this issue search the support site for the firmware download and apply yourself. -
SPA8000 not re-establishing PPPoE Session after extended outage
Hi,
I have an SPA8000 Bridged to a ADSL2+ Modem and the SPA8000 performs PPPoE Authentication. If there is a drop in the service, it will automatically redial back in, however if there is an extended outage (eg. Loss of Line Sync, Carrier Issues) the SPA8000 will refuse to reconnect automatically without intervention (eg. Rebooting).
The SPA8000 is running version 6.1.11, some basic settings:
Under WAN:
WAN Type: PPPoE
DNS Server: Manual
Username and Password are setup as per the PPPoE Account Details.
Everything is default.
Under Voice:
SIP Registry Expires on the Line are set to 600 seconds, Provider SIP Proxy is set along (DNS Based not IP Address) with Username and Password - everything else is left as default.
This is been tested on 3 separate SPA8000 devices experencing the same issue. NAT Keep Alive has been toggled to no success either.
Are you able to provide insight into this? I can supply further information if required.
Thanks
DavidHi Dan,
Apologies for the late reply to this message - I had to setup a test environment to emulate this problem. It appears there is a problem where by the SPA8000 (and this may apply to other models as well) does not try to re-authenticate again after initially retrying 4 Times (in quick 2 second increments) after receiving an Invalid Username/Password Response or Timeout from a PPPoE Server or LNS. It does however work if there it does not respond to a PPPoE discovery (eg. Unplugging the Ethernet Cable between the SPA8000 and the Modem/NTU or there is no communication between the network and Modem/NTU).
Here are the debug logs from where it did not try to re-authenticate and the only requests that I had back on the LNS. In this example the SIP Registry Expiry was set to 600 seconds and I changed the Password that it originally connected with and dropped/cleared the connection from the LNS. I waited the full 600 seconds and the PPPoE did not try again to re-authenticate.
The Logs don't seem to indicate much (and I have changed IP Addresses/Hostnames in the below logs as well):
<134>M2: System started: [email protected], reboot reason:H0
192.168.0.3 23/04 17:10:32.642
<134>M2: System started: [email protected], reboot reason:H0
192.168.0.3 23/04 17:10:32.642
<143>M2: subnet mask: 255.255.255.0
192.168.0.3 23/04 17:10:32.642
<143>M2: gateway ip: 192.168.0.1
192.168.0.3 23/04 17:10:32.642
<143>M2: dns servers(1): 192.168.0.3 23/04 17:10:32.642
<143>M2: 192.168.0.1 192.168.0.3 23/04 17:10:32.642
<143>M2:
192.168.0.3 23/04 17:10:32.642
<159>M0: IDBG: st-0
192.168.0.1 23/04 17:10:32.682
<159>M2: mslink server task up (2)
192.168.0.3 23/04 17:10:34.422
<134>M3: System started: [email protected], reboot reason:H0
192.168.0.4 23/04 17:10:35.793
<134>M3: System started: [email protected], reboot reason:H0
192.168.0.4 23/04 17:10:35.793
<143>M3: subnet mask: 255.255.255.0
192.168.0.4 23/04 17:10:35.793
<143>M3: gateway ip: 192.168.0.1
192.168.0.4 23/04 17:10:35.793
<134>M1: System started: [email protected], reboot reason:H0
192.168.0.2 23/04 17:10:35.793
<143>M3: dns servers(1): 192.168.0.4 23/04 17:10:35.793
<134>M1: System started: [email protected], reboot reason:H0
192.168.0.2 23/04 17:10:35.793
<143>M3: 192.168.0.1 192.168.0.4 23/04 17:10:35.793
<143>M1: subnet mask: 255.255.255.0
192.168.0.2 23/04 17:10:35.793
<143>M3:
192.168.0.4 23/04 17:10:35.793
<143>M1: gateway ip: 192.168.0.1
192.168.0.2 23/04 17:10:35.793
<143>M1: dns servers(1): 192.168.0.2 23/04 17:10:35.793
<143>M1: 192.168.0.1 192.168.0.2 23/04 17:10:35.793
<143>M1:
192.168.0.2 23/04 17:10:35.793
<159>M3: mslink server task up (3)
192.168.0.4 23/04 17:10:37.493
<159>M1: mslink server task up (1)
192.168.0.2 23/04 17:10:37.533
<159>M1: IDBG: st-0
192.168.0.2 23/04 17:10:38.203
<159>M1: fs:008275:008693:131072
192.168.0.2 23/04 17:10:38.303
<159>M1: fls:af:1:0:0
192.168.0.2 23/04 17:10:38.303
<159>M1: fbr:0:3000:3000:03985:0002:0001:6.1.12
192.168.0.2 23/04 17:10:38.303
<159>M1: PLKUP: 8192, 2102, 12, 1.5
192.168.0.2 23/04 17:10:38.333
<159>M1: fu:0:3997, 0003 0001
192.168.0.2 23/04 17:10:38.483
<159>M2: IDBG: st-0
192.168.0.3 23/04 17:10:39.093
<159>M2: fs:008200:008342:131072
192.168.0.3 23/04 17:10:39.193
<159>M2: fls:af:1:0:0
192.168.0.3 23/04 17:10:39.193
<159>M2: fbr:0:3000:3000:0358b:0002:0001:6.1.12
192.168.0.3 23/04 17:10:39.193
<159>M2: PLKUP: 8192, 2102, 12, 1.5
192.168.0.3 23/04 17:10:39.223
<159>M2: fu:0:359d, 0003 0001
192.168.0.3 23/04 17:10:39.373
<159>M2: mslink client task (2) gw=192.168.0.1 ip=192.168.0.3
192.168.0.3 23/04 17:10:39.423
<159>M0: MSLINK module 2 is at 192.168.0.3
192.168.0.1 23/04 17:10:40.164
<159>M3: IDBG: st-0
192.168.0.4 23/04 17:10:40.174
<159>M0: MSLINK code module 2: 0(32) sn:0
192.168.0.1 23/04 17:10:40.214
<159>M3: fs:008200:008351:131072
192.168.0.4 23/04 17:10:40.254
<159>M3: fls:af:1:0:0
192.168.0.4 23/04 17:10:40.264
<159>M3: fbr:0:3000:3000:04219:0002:0001:6.1.12
192.168.0.4 23/04 17:10:40.264
<159>M3: PLKUP: 8192, 2102, 12, 1.5
192.168.0.4 23/04 17:10:40.284
<159>M3: fu:0:422b, 0003 0001
192.168.0.4 23/04 17:10:40.444
<159>M3: mslink client task (3) gw=192.168.0.1 ip=192.168.0.4
192.168.0.4 23/04 17:10:42.484
<159>M1: mslink client task (1) gw=192.168.0.1 ip=192.168.0.2
192.168.0.2 23/04 17:10:42.524
<159>M0: MSLINK module 3 is at 192.168.0.4
192.168.0.1 23/04 17:10:43.234
<159>M0: MSLINK module 1 is at 192.168.0.2
192.168.0.1 23/04 17:10:43.374
<159>M0: MSLINK code module 3: 0(32) sn:0
192.168.0.1 23/04 17:10:43.374
<159>M0: MSLINK code module 1: 0(32) sn:0
192.168.0.1 23/04 17:10:43.864
<159>M0: fs:025125:025125:131072
192.168.0.1 23/04 17:10:47.215
<159>M0: fls:af:1:0:0
192.168.0.1 23/04 17:10:47.215
<159>M0: fbr:1:3000:3000:17329:0004:0005:6.1.12
192.168.0.1 23/04 17:10:47.215
<159>M0: fhs:01:0:0001:upg:app:0:5.1.10
192.168.0.1 23/04 17:10:47.225
<159>M0: fhs:02:0:0002:upg:app:1:5.1.10
192.168.0.1 23/04 17:10:47.275
<159>M0: fhs:03:0:0003:upg:app:2:5.1.10
192.168.0.1 23/04 17:10:47.315
<159>M0: fhs:04:0:0004:upg:app:0:6.1.12
192.168.0.1 23/04 17:10:47.385
<159>M0: fhs:05:0:0005:upg:app:1:6.1.12
192.168.0.1 23/04 17:10:47.405
<159>M0: fhs:06:0:0006:upg:app:2:6.1.12
192.168.0.1 23/04 17:10:47.435
<159>M0: PLKUP: 8192, 2102, 12, 1.5
192.168.0.1 23/04 17:10:47.525
<159>M0: fu:1:733b, 0003 0001
192.168.0.1 23/04 17:10:47.885
<159>M0: mslink P:12831 V:55495
192.168.0.1 23/04 17:11:00.106
<159>M1: CC_init
192.168.0.2 23/04 17:11:02.516
<134>M1: SLIC is si3215
192.168.0.2 23/04 17:11:02.606
<134>M1: SLIC is si3215
192.168.0.2 23/04 17:11:02.606
<159>M1: IDBG[0]:4
192.168.0.2 23/04 17:11:03.107
<159>M1: IDBG[1]:4
192.168.0.2 23/04 17:11:03.107
<159>M2: CC_init
192.168.0.3 23/04 17:11:03.407
<134>M2: SLIC is si3215
192.168.0.3 23/04 17:11:03.487
<134>M2: SLIC is si3215
192.168.0.3 23/04 17:11:03.497
<159>M2: IDBG[0]:4
192.168.0.3 23/04 17:11:03.997
<159>M2: IDBG[1]:4
192.168.0.3 23/04 17:11:03.997
<134>M1: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:11:04.237
<134>M1: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:11:04.237
<134>M1: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:11:04.237
<134>M1: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:11:04.247
<159>M3: CC_init
192.168.0.4 23/04 17:11:04.477
<134>M3: SLIC is si3215
192.168.0.4 23/04 17:11:04.557
<134>M3: SLIC is si3215
192.168.0.4 23/04 17:11:04.567
<159>M3: IDBG[0]:5
192.168.0.4 23/04 17:11:05.057
<159>M3: IDBG[1]:3
192.168.0.4 23/04 17:11:05.057
<159>M0: CC_init
192.168.0.1 23/04 17:11:05.957
<134>M0: SLIC is si3215
192.168.0.1 23/04 17:11:06.517
<134>M0: SLIC is si3215
192.168.0.1 23/04 17:11:06.527
<159>M0: IDBG[0]:6
192.168.0.1 23/04 17:11:07.017
<159>M0: IDBG[1]:4
192.168.0.1 23/04 17:11:07.017
<159>M1: [0]RegFail. Retry in 30
192.168.0.2 23/04 17:11:36.231
<159>M1: [1]RegFail. Retry in 30
192.168.0.2 23/04 17:11:36.241
<151>M1: CID:OSI
192.168.0.2 23/04 17:11:38.231
<151>M1: CID:OSI
192.168.0.2 23/04 17:11:38.241
<151>M1: CID:OnHookTx Pol
192.168.0.2 23/04 17:11:38.491
<151>M1: CID:OnHookTx Pol
192.168.0.2 23/04 17:11:38.501
<151>M1: Start DTMF/FSK
192.168.0.2 23/04 17:11:38.792
<151>M1: Start DTMF/FSK
192.168.0.2 23/04 17:11:38.792
<151>M1: CID:DONE
192.168.0.2 23/04 17:11:39.232
<151>M1: CID:DONE
192.168.0.2 23/04 17:11:39.242
<134>M0: System started: [email protected], reboot reason:H0
192.168.0.1 23/04 17:11:46.632
<134>M0: System started: [email protected], reboot reason:H0
192.168.0.1 23/04 17:11:46.632
<143>M0: subnet mask: 255.255.255.255
192.168.0.1 23/04 17:11:46.632
<143>M0: gateway ip: 10.128.1.254
192.168.0.1 23/04 17:11:46.642
<143>M0: dns servers(2): 192.168.0.1 23/04 17:11:46.642
<143>M0: 4.2.2.1 192.168.0.1 23/04 17:11:46.642
<143>M0: 4.2.2.1 192.168.0.1 23/04 17:11:46.642
<143>M0:
192.168.0.1 23/04 17:11:46.652
<134>M0: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.1 23/04 17:11:46.883
<134>M0: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.1 23/04 17:11:46.883
<134>M0: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.1 23/04 17:11:46.883
<134>M0: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.1 23/04 17:11:46.893
<134>M0: [2]Reg Addr Change(0) 0:0->7dfe3007:5060
192.168.0.1 23/04 17:11:46.933
<134>M0: [2]Reg Addr Change(0) 0:0->7dfe3007:5060
192.168.0.1 23/04 17:11:46.933
<134>M0: [2]->10.10.10.7:5060(577)
192.168.0.1 23/04 17:11:46.933
<134>M0: [2]->10.10.10.7:5060(577)
192.168.0.1 23/04 17:11:46.943
<134>M0:
192.168.0.1 23/04 17:11:46.943
<134>M0:
192.168.0.1 23/04 17:11:46.943
<134>M0: [pxy]<<127.0.0.1:5060(486)
192.168.0.1 23/04 17:11:46.943
<134>M0: [pxy]<<127.0.0.1:5060(486)
192.168.0.1 23/04 17:11:46.953
<134>M0:
192.168.0.1 23/04 17:11:46.953
<134>M0:
192.168.0.1 23/04 17:11:46.953
<134>M0: [pxy]->127.0.0.1:5060(395)
192.168.0.1 23/04 17:11:46.953
<134>M0: [pxy]->127.0.0.1:5060(395)
192.168.0.1 23/04 17:11:46.953
<134>M0:
192.168.0.1 23/04 17:11:46.953
<134>M0:
192.168.0.1 23/04 17:11:46.953
<134>M0: [pxy]<<127.0.0.1:5061(485)
192.168.0.1 23/04 17:11:46.963
<134>M0: [pxy]<<127.0.0.1:5061(485)
192.168.0.1 23/04 17:11:46.963
<134>M0:
192.168.0.1 23/04 17:11:46.963
<134>M0:
192.168.0.1 23/04 17:11:46.963
<134>M0: [pxy]->127.0.0.1:5061(394)
192.168.0.1 23/04 17:11:46.963
<134>M0: [pxy]->127.0.0.1:5061(394)
192.168.0.1 23/04 17:11:46.963
<134>M0:
192.168.0.1 23/04 17:11:46.963
<134>M0:
192.168.0.1 23/04 17:11:46.963
<159>M0: [0]RegOK. NextReg in 2130706430 (1)
192.168.0.1 23/04 17:11:46.963
<159>M0: [1]RegOK. NextReg in 2130706430 (1)
192.168.0.1 23/04 17:11:46.963
<134>M0: [pxy]<<127.0.0.1:5060(426)
192.168.0.1 23/04 17:11:46.973
<134>M0: [pxy]<<127.0.0.1:5060(426)
192.168.0.1 23/04 17:11:46.973
<134>M0:
192.168.0.1 23/04 17:11:46.973
<134>M0:
192.168.0.1 23/04 17:11:46.973
<134>M0: [pxy]->127.0.0.1:5060(363)
192.168.0.1 23/04 17:11:46.973
<134>M0: [pxy]->127.0.0.1:5060(363)
192.168.0.1 23/04 17:11:46.973
<134>M0:
192.168.0.1 23/04 17:11:46.973
<134>M0:
192.168.0.1 23/04 17:11:46.973
<134>M0: [pxy]->10.128.1.4:5060(463)
192.168.0.1 23/04 17:11:46.973
<134>M0: [pxy]->10.128.1.4:5060(463)
192.168.0.1 23/04 17:11:46.973
<134>M0:
192.168.0.1 23/04 17:11:46.983
<134>M0:
192.168.0.1 23/04 17:11:46.983
<134>M0: [pxy]<<127.0.0.1:5061(426)
192.168.0.1 23/04 17:11:46.983
<134>M0: [pxy]<<127.0.0.1:5061(426)
192.168.0.1 23/04 17:11:46.983
<134>M0:
192.168.0.1 23/04 17:11:46.983
<134>M0:
192.168.0.1 23/04 17:11:46.983
<134>M0: [pxy]->127.0.0.1:5061(363)
192.168.0.1 23/04 17:11:46.983
<134>M0: [pxy]->127.0.0.1:5061(363)
192.168.0.1 23/04 17:11:46.983
<134>M0:
192.168.0.1 23/04 17:11:46.983
<134>M0:
192.168.0.1 23/04 17:11:46.983
<134>M0: [pxy]->10.128.1.4:5061(463)
192.168.0.1 23/04 17:11:46.983
<134>M0: [pxy]->10.128.1.4:5061(463)
192.168.0.1 23/04 17:11:46.983
<134>M0:
192.168.0.1 23/04 17:11:46.983
<134>M0:
192.168.0.1 23/04 17:11:46.983
<151>M0: [0]SubOK
192.168.0.1 23/04 17:11:46.983
<151>M0: NextSub in 2147483646 (1)
192.168.0.1 23/04 17:11:46.993
<151>M0: [1]SubOK
192.168.0.1 23/04 17:11:46.993
<151>M0: NextSub in 2147483646 (1)
192.168.0.1 23/04 17:11:46.993
<134>M0: [2]<<10.10.10.7:5060(545)
192.168.0.1 23/04 17:11:46.993
<134>M0: [2]<<10.10.10.7:5060(545)
192.168.0.1 23/04 17:11:46.993
<134>M0:
192.168.0.1 23/04 17:11:46.993
<134>M0:
192.168.0.1 23/04 17:11:46.993
<134>M0: [pxy]<<127.0.0.1:5060(352)
192.168.0.1 23/04 17:11:46.993
<134>M0: [pxy]<<127.0.0.1:5060(352)
192.168.0.1 23/04 17:11:46.993
<134>M0:
192.168.0.1 23/04 17:11:46.993
<134>M0:
192.168.0.1 23/04 17:11:46.993
<134>M0: [pxy]<<127.0.0.1:5061(352)
192.168.0.1 23/04 17:11:46.993
<134>M0: [pxy]<<127.0.0.1:5061(352)
192.168.0.1 23/04 17:11:46.993
<134>M0:
192.168.0.1 23/04 17:11:46.993
<134>M0:
192.168.0.1 23/04 17:11:46.993
<134>M0: [2]->10.10.10.7:5060(745)
192.168.0.1 23/04 17:11:46.993
<134>M0: [2]->10.10.10.7:5060(745)
192.168.0.1 23/04 17:11:46.993
<134>M0:
192.168.0.1 23/04 17:11:47.003
<134>M0:
192.168.0.1 23/04 17:11:47.003
<134>M0: [2]<<10.10.10.7:5060(566)
192.168.0.1 23/04 17:11:47.053
<134>M0: [2]<<10.10.10.7:5060(566)
192.168.0.1 23/04 17:11:47.053
<134>M0:
192.168.0.1 23/04 17:11:47.053
<134>M0:
192.168.0.1 23/04 17:11:47.063
<159>M0: [2]RegOK. NextReg in 594 (1)
192.168.0.1 23/04 17:11:47.063
<151>M0: CID:OSI
192.168.0.1 23/04 17:11:48.973
<151>M0: CID:OSI
192.168.0.1 23/04 17:11:48.983
<151>M0: CID:OnHookTx Pol
192.168.0.1 23/04 17:11:49.233
<151>M0: CID:OnHookTx Pol
192.168.0.1 23/04 17:11:49.243
<151>M0: Start DTMF/FSK
192.168.0.1 23/04 17:11:49.533
<151>M0: Start DTMF/FSK
192.168.0.1 23/04 17:11:49.543
<151>M0: CID:DONE
192.168.0.1 23/04 17:11:49.983
<151>M0: CID:DONE
192.168.0.1 23/04 17:11:49.993
<134>M0: [pxy]<<192.168.0.2:5160(487)
192.168.0.1 23/04 17:12:06.235
<134>M0: [pxy]<<192.168.0.2:5160(487)
192.168.0.1 23/04 17:12:06.235
<134>M0:
192.168.0.1 23/04 17:12:06.235
<134>M0:
192.168.0.1 23/04 17:12:06.235
<134>M0: [pxy]->192.168.0.2:5160(398)
192.168.0.1 23/04 17:12:06.245
<134>M0: [pxy]->192.168.0.2:5160(398)
192.168.0.1 23/04 17:12:06.245
<134>M0:
192.168.0.1 23/04 17:12:06.245
<134>M0:
192.168.0.1 23/04 17:12:06.255
<134>M0: [pxy]<<192.168.0.2:5161(487)
192.168.0.1 23/04 17:12:06.255
<134>M0: [pxy]<<192.168.0.2:5161(487)
192.168.0.1 23/04 17:12:06.255
<134>M0:
192.168.0.1 23/04 17:12:06.255
<134>M0:
192.168.0.1 23/04 17:12:06.265
<159>M1: [0]RegOK. NextReg in 2130706430 (1)
192.168.0.2 23/04 17:12:06.265
<134>M0: [pxy]->192.168.0.2:5161(398)
192.168.0.1 23/04 17:12:06.265
<134>M0: [pxy]->192.168.0.2:5161(398)
192.168.0.1 23/04 17:12:06.275
<134>M0:
192.168.0.1 23/04 17:12:06.275
<134>M0:
192.168.0.1 23/04 17:12:06.275
<134>M0: [pxy]<<192.168.0.2:5160(426)
192.168.0.1 23/04 17:12:06.275
<134>M0: [pxy]<<192.168.0.2:5160(426)
192.168.0.1 23/04 17:12:06.275
<134>M0:
192.168.0.1 23/04 17:12:06.275
<134>M0:
192.168.0.1 23/04 17:12:06.275
<159>M1: [1]RegOK. NextReg in 2130706430 (1)
192.168.0.2 23/04 17:12:06.275
<134>M0: [pxy]->192.168.0.2:5160(363)
192.168.0.1 23/04 17:12:06.275
<134>M0: [pxy]->192.168.0.2:5160(363)
192.168.0.1 23/04 17:12:06.285
<134>M0:
192.168.0.1 23/04 17:12:06.285
<134>M0:
192.168.0.1 23/04 17:12:06.285
<134>M0: [pxy]->10.128.1.4:5160(464)
192.168.0.1 23/04 17:12:06.285
<134>M0: [pxy]->10.128.1.4:5160(464)
192.168.0.1 23/04 17:12:06.285
<134>M0:
192.168.0.1 23/04 17:12:06.285
<134>M0:
192.168.0.1 23/04 17:12:06.285
<151>M1: [0]SubOK
192.168.0.2 23/04 17:12:06.285
<151>M1: NextSub in 2147483646 (1)
192.168.0.2 23/04 17:12:06.285
<134>M0: [pxy]<<192.168.0.2:5161(427)
192.168.0.1 23/04 17:12:06.285
<134>M0: [pxy]<<192.168.0.2:5161(427)
192.168.0.1 23/04 17:12:06.285
<134>M0:
192.168.0.1 23/04 17:12:06.285
<134>M0:
192.168.0.1 23/04 17:12:06.295
<134>M0: [pxy]->192.168.0.2:5161(364)
192.168.0.1 23/04 17:12:06.295
<134>M0: [pxy]->192.168.0.2:5161(364)
192.168.0.1 23/04 17:12:06.295
<134>M0:
192.168.0.1 23/04 17:12:06.295
<134>M0:
192.168.0.1 23/04 17:12:06.295
<151>M1: [1]SubOK
192.168.0.2 23/04 17:12:06.295
<151>M1: NextSub in 2147483646 (1)
192.168.0.2 23/04 17:12:06.295
<134>M0: [pxy]->10.128.1.4:5161(464)
192.168.0.1 23/04 17:12:06.295
<134>M0: [pxy]->10.128.1.4:5161(464)
192.168.0.1 23/04 17:12:06.295
<134>M0:
192.168.0.1 23/04 17:12:06.295
<134>M0:
192.168.0.1 23/04 17:12:06.295
<134>M0: [pxy]<<192.168.0.2:5160(352)
192.168.0.1 23/04 17:12:06.295
<134>M0: [pxy]<<192.168.0.2:5160(352)
192.168.0.1 23/04 17:12:06.295
<134>M0:
192.168.0.1 23/04 17:12:06.295
<134>M0:
192.168.0.1 23/04 17:12:06.295
<134>M0: [pxy]<<192.168.0.2:5161(353)
192.168.0.1 23/04 17:12:06.295
<134>M0: [pxy]<<192.168.0.2:5161(353)
192.168.0.1 23/04 17:12:06.295
<134>M0:
192.168.0.1 23/04 17:12:06.305
<134>M0:
192.168.0.1 23/04 17:12:06.305
<151>M0: IDBG: pppld
192.168.0.1 23/04 17:12:26.798
<151>M0: [2]SIP:ICMP Error -1 (7dfe3007:5060, 8)
192.168.0.1 23/04 17:21:41.045
<134>M0: [2]->10.10.10.7:5060(745)
192.168.0.1 23/04 17:21:41.045
<134>M0: [2]->10.10.10.7:5060(745)
192.168.0.1 23/04 17:21:41.045
<134>M0:
192.168.0.1 23/04 17:21:41.045
<134>M0:
192.168.0.1 23/04 17:21:41.045
<159>M0: RSE_DEBUG: getting alternate from domain:sip.siptest.com
192.168.0.1 23/04 17:21:41.055
<159>M0: [2]RegFail. Retry in 30
192.168.0.1 23/04 17:21:41.055
<151>M0: [2]SIP:ICMP Error -1 (7dfe3007:5060, 8)
192.168.0.1 23/04 17:22:11.049
<134>M0: [2]->10.10.10.7:5060(577)
192.168.0.1 23/04 17:22:11.059
<134>M0: [2]->10.10.10.7:5060(577)
192.168.0.1 23/04 17:22:11.069
<134>M0:
192.168.0.1 23/04 17:22:11.069
<134>M0:
192.168.0.1 23/04 17:22:11.069
<159>M0: RSE_DEBUG: getting alternate from domain:sip.siptest.com
192.168.0.1 23/04 17:22:11.069
<159>M0: [2]RegFail. Retry in 30
192.168.0.1 23/04 17:22:11.069
core-rtr#
Apr 23 07:12:28.636: %LINK-3-UPDOWN: Interface Virtual-Access78, changed state to down
Apr 23 07:12:29.636: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access78, changed state to down
Apr 23 07:12:33.688: ppp261 PPP: Authorization required
Apr 23 07:12:33.692: ppp261 PPP: Authorization required
Apr 23 07:12:33.732: ppp261 CHAP: O CHALLENGE id 2 len 29 from "core-rtr"
Apr 23 07:12:33.776: ppp261 CHAP: I RESPONSE id 2 len 55 from "[email protected]"
Apr 23 07:12:33.776: ppp261 PPP: Sent CHAP LOGIN Request
Apr 23 07:12:35.776: ppp261 PPP: Received LOGIN Response FAIL
Apr 23 07:12:35.776: ppp261 CHAP: O FAILURE id 2 len 25 msg is "Authentication failed"
Apr 23 07:12:37.788: ppp262 PPP: Authorization required
Apr 23 07:12:37.788: ppp262 PPP: Authorization required
Apr 23 07:12:37.832: ppp262 CHAP: O CHALLENGE id 2 len 29 from "core-rtr"
Apr 23 07:12:37.872: ppp262 CHAP: I RESPONSE id 2 len 55 from "[email protected]"
Apr 23 07:12:37.872: ppp262 PPP: Sent CHAP LOGIN Request
Apr 23 07:12:39.872: ppp262 PPP: Received LOGIN Response FAIL
Apr 23 07:12:39.872: ppp262 CHAP: O FAILURE id 2 len 25 msg is "Authentication failed"
Apr 23 07:12:41.880: ppp263 PPP: Authorization required
Apr 23 07:12:41.880: ppp263 PPP: Authorization required
Apr 23 07:12:41.924: ppp263 CHAP: O CHALLENGE id 2 len 29 from "core-rtr"
Apr 23 07:12:41.964: ppp263 CHAP: I RESPONSE id 2 len 55 from "[email protected]"
Apr 23 07:12:41.964: ppp263 PPP: Sent CHAP LOGIN Request
Apr 23 07:12:43.968: ppp263 PPP: Received LOGIN Response FAIL
Apr 23 07:12:43.968: ppp263 CHAP: O FAILURE id 2 len 25 msg is "Authentication failed"
Apr 23 07:12:45.980: ppp264 PPP: Authorization required
Apr 23 07:12:45.980: ppp264 PPP: Authorization required
Apr 23 07:12:46.020: ppp264 CHAP: O CHALLENGE id 2 len 29 from "core-rtr"
Apr 23 07:12:46.064: ppp264 CHAP: I RESPONSE id 2 len 55 from "[email protected]"
Apr 23 07:12:46.064: ppp264 PPP: Sent CHAP LOGIN Request
Apr 23 07:12:48.064: ppp264 PPP: Received LOGIN Response FAIL
Apr 23 07:12:48.064: ppp264 CHAP: O FAILURE id 2 len 25 msg is "Authentication failed"
core-rtr#
Here is the log from a successful reauthentication AFTER the modem/NTU had lost connectivity to the network:
<134>M1: System started: [email protected], reboot reason:H0
192.168.0.2 23/04 17:26:12.220
<134>M1: System started: [email protected], reboot reason:H0
192.168.0.2 23/04 17:26:12.220
<143>M1: subnet mask: 255.255.255.0
192.168.0.2 23/04 17:26:12.220
<143>M1: gateway ip: 192.168.0.1
192.168.0.2 23/04 17:26:12.220
<143>M1: dns servers(1): 192.168.0.2 23/04 17:26:12.220
<143>M1: 192.168.0.1 192.168.0.2 23/04 17:26:12.220
<143>M1:
192.168.0.2 23/04 17:26:12.220
<159>M1: mslink server task up (1)
192.168.0.2 23/04 17:26:12.290
<159>M0: IDBG: st-0
192.168.0.1 23/04 17:26:12.430
<134>M3: System started: [email protected], reboot reason:H0
192.168.0.4 23/04 17:26:14.390
<134>M3: System started: [email protected], reboot reason:H0
192.168.0.4 23/04 17:26:14.390
<143>M3: subnet mask: 255.255.255.0
192.168.0.4 23/04 17:26:14.390
<143>M3: gateway ip: 192.168.0.1
192.168.0.4 23/04 17:26:14.390
<143>M3: dns servers(1): 192.168.0.4 23/04 17:26:14.400
<143>M3: 192.168.0.1 192.168.0.4 23/04 17:26:14.400
<143>M3:
192.168.0.4 23/04 17:26:14.400
<134>M2: System started: [email protected], reboot reason:H0
192.168.0.3 23/04 17:26:14.400
<134>M2: System started: [email protected], reboot reason:H0
192.168.0.3 23/04 17:26:14.400
<143>M2: subnet mask: 255.255.255.0
192.168.0.3 23/04 17:26:14.400
<143>M2: gateway ip: 192.168.0.1
192.168.0.3 23/04 17:26:14.400
<143>M2: dns servers(1): 192.168.0.3 23/04 17:26:14.400
<143>M2: 192.168.0.1 192.168.0.3 23/04 17:26:14.400
<143>M2:
192.168.0.3 23/04 17:26:14.400
<159>M2: mslink server task up (2)
192.168.0.3 23/04 17:26:16.190
<159>M3: mslink server task up (3)
192.168.0.4 23/04 17:26:16.260
<159>M1: mslink client task (1) gw=192.168.0.1 ip=192.168.0.2
192.168.0.2 23/04 17:26:16.280
<159>M0: MSLINK module 1 is at 192.168.0.2
192.168.0.1 23/04 17:26:17.010
<159>M0: MSLINK code module 1: 0(32) sn:0
192.168.0.1 23/04 17:26:17.060
<159>M1: IDBG: st-0
192.168.0.2 23/04 17:26:18.240
<159>M1: fs:008275:008693:131072
192.168.0.2 23/04 17:26:18.330
<159>M1: fls:af:1:0:0
192.168.0.2 23/04 17:26:18.330
<159>M1: fbr:0:3000:3000:03997:0002:0001:6.1.12
192.168.0.2 23/04 17:26:18.330
<159>M1: PLKUP: 8192, 2102, 12, 1.5
192.168.0.2 23/04 17:26:18.370
<159>M1: fu:0:39a9, 0003 0001
192.168.0.2 23/04 17:26:18.540
<159>M2: IDBG: st-0
192.168.0.3 23/04 17:26:18.860
<159>M2: fs:008200:008342:131072
192.168.0.3 23/04 17:26:18.960
<159>M2: fls:af:1:0:0
192.168.0.3 23/04 17:26:18.960
<159>M2: fbr:0:3000:3000:0359d:0002:0001:6.1.12
192.168.0.3 23/04 17:26:18.960
<159>M2: PLKUP: 8192, 2102, 12, 1.5
192.168.0.3 23/04 17:26:18.990
<159>M2: fu:0:35af, 0003 0001
192.168.0.3 23/04 17:26:19.150
<159>M3: IDBG: st-0
192.168.0.4 23/04 17:26:19.931
<159>M3: fs:008200:008351:131072
192.168.0.4 23/04 17:26:20.021
<159>M3: fls:af:1:0:0
192.168.0.4 23/04 17:26:20.021
<159>M3: fbr:0:3000:3000:0422b:0002:0001:6.1.12
192.168.0.4 23/04 17:26:20.021
<159>M3: PLKUP: 8192, 2102, 12, 1.5
192.168.0.4 23/04 17:26:20.051
<159>M3: fu:0:423d, 0003 0001
192.168.0.4 23/04 17:26:20.211
<159>M3: mslink client task (3) gw=192.168.0.1 ip=192.168.0.4
192.168.0.4 23/04 17:26:20.251
<159>M0: MSLINK module 3 is at 192.168.0.4
192.168.0.1 23/04 17:26:20.991
<159>M0: MSLINK code module 3: 0(32) sn:0
192.168.0.1 23/04 17:26:21.041
<159>M2: mslink client task (2) gw=192.168.0.1 ip=192.168.0.3
192.168.0.3 23/04 17:26:21.181
<159>M0: MSLINK module 2 is at 192.168.0.3
192.168.0.1 23/04 17:26:22.262
<159>M0: MSLINK code module 2: 0(32) sn:0
192.168.0.1 23/04 17:26:22.332
<159>M0: fs:025125:025125:131072
192.168.0.1 23/04 17:26:26.852
<159>M0: fls:af:1:0:0
192.168.0.1 23/04 17:26:26.852
<159>M0: fbr:1:3000:3000:1733b:0004:0005:6.1.12
192.168.0.1 23/04 17:26:26.852
<159>M0: fhs:01:0:0001:upg:app:0:5.1.10
192.168.0.1 23/04 17:26:26.852
<159>M0: fhs:02:0:0002:upg:app:1:5.1.10
192.168.0.1 23/04 17:26:26.882
<159>M0: fhs:03:0:0003:upg:app:2:5.1.10
192.168.0.1 23/04 17:26:26.922
<159>M0: fhs:04:0:0004:upg:app:0:6.1.12
192.168.0.1 23/04 17:26:26.962
<159>M0: fhs:05:0:0005:upg:app:1:6.1.12
192.168.0.1 23/04 17:26:26.992
<159>M0: fhs:06:0:0006:upg:app:2:6.1.12
192.168.0.1 23/04 17:26:27.032
<159>M0: PLKUP: 8192, 2102, 12, 1.5
192.168.0.1 23/04 17:26:27.132
<159>M0: fu:1:734d, 0003 0001
192.168.0.1 23/04 17:26:27.442
<159>M0: mslink P:12222 V:58850
192.168.0.1 23/04 17:26:39.354
<159>M1: CC_init
192.168.0.2 23/04 17:26:42.275
<134>M1: SLIC is si3215
192.168.0.2 23/04 17:26:42.355
<134>M1: SLIC is si3215
192.168.0.2 23/04 17:26:42.355
<159>M1: IDBG[0]:4
192.168.0.2 23/04 17:26:42.845
<159>M1: IDBG[1]:4
192.168.0.2 23/04 17:26:42.845
<159>M2: CC_init
192.168.0.3 23/04 17:26:43.175
<134>M2: SLIC is si3215
192.168.0.3 23/04 17:26:43.255
<134>M2: SLIC is si3215
192.168.0.3 23/04 17:26:43.255
<159>M2: IDBG[0]:4
192.168.0.3 23/04 17:26:43.745
<159>M2: IDBG[1]:3
192.168.0.3 23/04 17:26:43.745
<134>M1: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:26:43.985
<134>M1: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:26:43.985
<134>M1: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:26:43.985
<134>M1: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:26:43.985
<159>M3: CC_init
192.168.0.4 23/04 17:26:44.245
<134>M3: SLIC is si3215
192.168.0.4 23/04 17:26:44.325
<134>M3: SLIC is si3215
192.168.0.4 23/04 17:26:44.325
<159>M3: IDBG[0]:5
192.168.0.4 23/04 17:26:44.815
<159>M3: IDBG[1]:4
192.168.0.4 23/04 17:26:44.815
<159>M0: CC_init
192.168.0.1 23/04 17:26:45.715
<134>M0: SLIC is si3215
192.168.0.1 23/04 17:26:46.275
<134>M0: SLIC is si3215
192.168.0.1 23/04 17:26:46.275
<159>M0: IDBG[0]:6
192.168.0.1 23/04 17:26:46.755
<159>M0: IDBG[1]:4
192.168.0.1 23/04 17:26:46.765
<134>M0: System started: [email protected], reboot reason:H0
192.168.0.1 23/04 17:27:13.110
<134>M0: System started: [email protected], reboot reason:H0
192.168.0.1 23/04 17:27:13.110
<143>M0: subnet mask: 255.255.255.255
192.168.0.1 23/04 17:27:13.120
<143>M0: gateway ip: 125.254.48.254
192.168.0.1 23/04 17:27:13.120
<143>M0: dns servers(2): 192.168.0.1 23/04 17:27:13.120
<143>M0: 4.2.2.1 192.168.0.1 23/04 17:27:13.120
<143>M0: 4.2.2.2 192.168.0.1 23/04 17:27:13.120
<143>M0:
192.168.0.1 23/04 17:27:13.120
<134>M0: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.1 23/04 17:27:13.370
<134>M0: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.1 23/04 17:27:13.370
<134>M0: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.1 23/04 17:27:13.370
<134>M0: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.1 23/04 17:27:13.370
<134>M0: [2]Reg Addr Change(0) 0:0->7dfe3007:5060
192.168.0.1 23/04 17:27:13.420
<134>M0: [2]Reg Addr Change(0) 0:0->7dfe3007:5060
192.168.0.1 23/04 17:27:13.420
<134>M0: [2]->10.10.10.7:5060(577)
192.168.0.1 23/04 17:27:13.420
<134>M0: [2]->10.10.10.7:5060(577)
192.168.0.1 23/04 17:27:13.420
<134>M0:
192.168.0.1 23/04 17:27:13.420
<134>M0:
192.168.0.1 23/04 17:27:13.420
<134>M0: [pxy]<<127.0.0.1:5060(485)
192.168.0.1 23/04 17:27:13.420
<134>M0: [pxy]<<127.0.0.1:5060(485)
192.168.0.1 23/04 17:27:13.420
<134>M0:
192.168.0.1 23/04 17:27:13.420
<134>M0:
192.168.0.1 23/04 17:27:13.420
<134>M0: [pxy]->127.0.0.1:5060(394)
192.168.0.1 23/04 17:27:13.420
<134>M0: [pxy]->127.0.0.1:5060(394)
192.168.0.1 23/04 17:27:13.420
<134>M0:
192.168.0.1 23/04 17:27:13.420
<134>M0:
192.168.0.1 23/04 17:27:13.420
<134>M0: [pxy]<<127.0.0.1:5061(486)
192.168.0.1 23/04 17:27:13.430
<134>M0: [pxy]<<127.0.0.1:5061(486)
192.168.0.1 23/04 17:27:13.430
<134>M0:
192.168.0.1 23/04 17:27:13.430
<134>M0:
192.168.0.1 23/04 17:27:13.430
<134>M0: [pxy]->127.0.0.1:5061(395)
192.168.0.1 23/04 17:27:13.430
<134>M0: [pxy]->127.0.0.1:5061(395)
192.168.0.1 23/04 17:27:13.430
<134>M0:
192.168.0.1 23/04 17:27:13.430
<134>M0:
192.168.0.1 23/04 17:27:13.430
<159>M0: [0]RegOK. NextReg in 2130706430 (1)
192.168.0.1 23/04 17:27:13.430
<159>M0: [1]RegOK. NextReg in 2130706430 (1)
192.168.0.1 23/04 17:27:13.440
<134>M0: [pxy]<<127.0.0.1:5060(433)
192.168.0.1 23/04 17:27:13.440
<134>M0: [pxy]<<127.0.0.1:5060(433)
192.168.0.1 23/04 17:27:13.440
<134>M0:
192.168.0.1 23/04 17:27:13.440
<134>M0:
192.168.0.1 23/04 17:27:13.440
<134>M0: [pxy]->127.0.0.1:5060(363)
192.168.0.1 23/04 17:27:13.450
<134>M0: [pxy]->127.0.0.1:5060(363)
192.168.0.1 23/04 17:27:13.450
<134>M0:
192.168.0.1 23/04 17:27:13.450
<134>M0:
192.168.0.1 23/04 17:27:13.450
<134>M0: [pxy]->10.128.1.4:5060(463)
192.168.0.1 23/04 17:27:13.450
<134>M0: [pxy]->10.128.1.4:5060(463)
192.168.0.1 23/04 17:27:13.450
<134>M0:
192.168.0.1 23/04 17:27:13.450
<134>M0:
192.168.0.1 23/04 17:27:13.450
<134>M0: [pxy]<<127.0.0.1:5061(425)
192.168.0.1 23/04 17:27:13.450
<134>M0: [pxy]<<127.0.0.1:5061(425)
192.168.0.1 23/04 17:27:13.450
<134>M0:
192.168.0.1 23/04 17:27:13.450
<134>M0:
192.168.0.1 23/04 17:27:13.450
<134>M0: [pxy]->127.0.0.1:5061(362)
192.168.0.1 23/04 17:27:13.460
<134>M0: [pxy]->127.0.0.1:5061(362)
192.168.0.1 23/04 17:27:13.460
<134>M0:
192.168.0.1 23/04 17:27:13.460
<134>M0:
192.168.0.1 23/04 17:27:13.460
<134>M0: [pxy]->10.128.1.4:5061(463)
192.168.0.1 23/04 17:27:13.460
<134>M0: [pxy]->10.128.1.4:5061(463)
192.168.0.1 23/04 17:27:13.460
<134>M0:
192.168.0.1 23/04 17:27:13.460
<134>M0:
192.168.0.1 23/04 17:27:13.460
<151>M0: [0]SubOK
192.168.0.1 23/04 17:27:13.460
<151>M0: NextSub in 2147483646 (1)
192.168.0.1 23/04 17:27:13.460
<151>M0: [1]SubOK
192.168.0.1 23/04 17:27:13.470
<151>M0: NextSub in 2147483646 (1)
192.168.0.1 23/04 17:27:13.470
<134>M0: [2]<<10.10.10.7:5060(545)
192.168.0.1 23/04 17:27:13.470
<134>M0: [2]<<10.10.10.7:5060(545)
192.168.0.1 23/04 17:27:13.470
<134>M0:
192.168.0.1 23/04 17:27:13.470
<134>M0:
192.168.0.1 23/04 17:27:13.470
<134>M0: [pxy]<<127.0.0.1:5060(351)
192.168.0.1 23/04 17:27:13.480
<134>M0: [pxy]<<127.0.0.1:5060(351)
192.168.0.1 23/04 17:27:13.480
<134>M0:
192.168.0.1 23/04 17:27:13.480
<134>M0:
192.168.0.1 23/04 17:27:13.480
<134>M0: [pxy]<<127.0.0.1:5061(350)
192.168.0.1 23/04 17:27:13.480
<134>M0: [pxy]<<127.0.0.1:5061(350)
192.168.0.1 23/04 17:27:13.480
<134>M0:
192.168.0.1 23/04 17:27:13.480
<134>M0:
192.168.0.1 23/04 17:27:13.480
<134>M0: [2]->10.10.10.7:5060(745)
192.168.0.1 23/04 17:27:13.480
<134>M0: [2]->10.10.10.7:5060(745)
192.168.0.1 23/04 17:27:13.480
<134>M0:
192.168.0.1 23/04 17:27:13.480
<134>M0:
192.168.0.1 23/04 17:27:13.480
<134>M0: [2]<<10.10.10.7:5060(566)
192.168.0.1 23/04 17:27:13.550
<134>M0: [2]<<10.10.10.7:5060(566)
192.168.0.1 23/04 17:27:13.550
<134>M0:
192.168.0.1 23/04 17:27:13.550
<134>M0:
192.168.0.1 23/04 17:27:13.550
<159>M0: [2]RegOK. NextReg in 594 (1)
192.168.0.1 23/04 17:27:13.550
<151>M0: CID:OSI
192.168.0.1 23/04 17:27:15.460
<151>M0: CID:OSI
192.168.0.1 23/04 17:27:15.460
<134>M0: [pxy]<<192.168.0.2:5160(486)
192.168.0.1 23/04 17:27:15.480
<134>M0: [pxy]<<192.168.0.2:5160(486)
192.168.0.1 23/04 17:27:15.480
<134>M0:
192.168.0.1 23/04 17:27:15.480
<134>M0:
192.168.0.1 23/04 17:27:15.480
<134>M0: [pxy]->192.168.0.2:5160(398)
192.168.0.1 23/04 17:27:15.480
<134>M0: [pxy]->192.168.0.2:5160(398)
192.168.0.1 23/04 17:27:15.480
<134>M0:
192.168.0.1 23/04 17:27:15.480
<134>M0:
192.168.0.1 23/04 17:27:15.480
<134>M0: [pxy]<<192.168.0.2:5161(486)
192.168.0.1 23/04 17:27:15.490
<134>M0: [pxy]<<192.168.0.2:5161(486)
192.168.0.1 23/04 17:27:15.490
<134>M0:
192.168.0.1 23/04 17:27:15.490
<134>M0:
192.168.0.1 23/04 17:27:15.490
<159>M1: [0]RegOK. NextReg in 2130706400 (31)
192.168.0.2 23/04 17:27:15.490
<134>M0: [pxy]->192.168.0.2:5161(398)
192.168.0.1 23/04 17:27:15.490
<134>M0: [pxy]->192.168.0.2:5161(398)
192.168.0.1 23/04 17:27:15.490
<134>M0:
192.168.0.1 23/04 17:27:15.490
<134>M0:
192.168.0.1 23/04 17:27:15.490
<134>M0: [pxy]<<192.168.0.2:5160(427)
192.168.0.1 23/04 17:27:15.500
<134>M0: [pxy]<<192.168.0.2:5160(427)
192.168.0.1 23/04 17:27:15.500
<134>M0:
192.168.0.1 23/04 17:27:15.500
<134>M0:
192.168.0.1 23/04 17:27:15.500
<159>M1: [1]RegOK. NextReg in 2130706400 (31)
192.168.0.2 23/04 17:27:15.500
<134>M0: [pxy]->192.168.0.2:5160(364)
192.168.0.1 23/04 17:27:15.500
<134>M0: [pxy]->192.168.0.2:5160(364)
192.168.0.1 23/04 17:27:15.500
<134>M0:
192.168.0.1 23/04 17:27:15.500
<134>M0:
192.168.0.1 23/04 17:27:15.500
<134>M0: [pxy]->10.128.1.4:5160(463)
192.168.0.1 23/04 17:27:15.500
<134>M0: [pxy]->10.128.1.4:5160(463)
192.168.0.1 23/04 17:27:15.500
<134>M0:
192.168.0.1 23/04 17:27:15.500
<134>M0:
192.168.0.1 23/04 17:27:15.500
<151>M1: [0]SubOK
192.168.0.2 23/04 17:27:15.500
<151>M1: NextSub in 2147483646 (1)
192.168.0.2 23/04 17:27:15.510
<134>M0: [pxy]<<192.168.0.2:5161(426)
192.168.0.1 23/04 17:27:15.510
<134>M0: [pxy]<<192.168.0.2:5161(426)
192.168.0.1 23/04 17:27:15.510
<134>M0:
192.168.0.1 23/04 17:27:15.510
<134>M0:
192.168.0.1 23/04 17:27:15.510
<134>M0: [pxy]->192.168.0.2:5161(363)
192.168.0.1 23/04 17:27:15.510
<134>M0: [pxy]->192.168.0.2:5161(363)
192.168.0.1 23/04 17:27:15.510
<134>M0:
192.168.0.1 23/04 17:27:15.510
<134>M0:
192.168.0.1 23/04 17:27:15.510
<151>M1: [1]SubOK
192.168.0.2 23/04 17:27:15.510
<134>M0: [pxy]->10.128.1.4:5161(463)
192.168.0.1 23/04 17:27:15.510
<151>M1: NextSub in 2147483646 (1)
192.168.0.2 23/04 17:27:15.510
<134>M0: [pxy]->10.128.1.4:5161(463)
192.168.0.1 23/04 17:27:15.510
<134>M0:
192.168.0.1 23/04 17:27:15.520
<134>M0:
192.168.0.1 23/04 17:27:15.520
<134>M0: [pxy]<<192.168.0.2:5160(352)
192.168.0.1 23/04 17:27:15.520
<134>M0: [pxy]<<192.168.0.2:5160(352)
192.168.0.1 23/04 17:27:15.520
<134>M0:
192.168.0.1 23/04 17:27:15.520
<134>M0:
192.168.0.1 23/04 17:27:15.520
<134>M0: [pxy]<<192.168.0.2:5161(352)
192.168.0.1 23/04 17:27:15.520
<134>M0: [pxy]<<192.168.0.2:5161(352)
192.168.0.1 23/04 17:27:15.520
<134>M0:
192.168.0.1 23/04 17:27:15.520
<134>M0:
192.168.0.1 23/04 17:27:15.520
<151>M0: CID:OnHookTx Pol
192.168.0.1 23/04 17:27:15.720
<151>M0: CID:OnHookTx Pol
192.168.0.1 23/04 17:27:15.720
<151>M0: Start DTMF/FSK
192.168.0.1 23/04 17:27:16.020
<151>M0: Start DTMF/FSK
192.168.0.1 23/04 17:27:16.030
<151>M0: CID:DONE
192.168.0.1 23/04 17:27:16.470
<151>M0: CID:DONE
192.168.0.1 23/04 17:27:16.470
<151>M1: CID:OSI
192.168.0.2 23/04 17:27:17.500
<151>M1: CID:OSI
192.168.0.2 23/04 17:27:17.510
<151>M1: CID:OnHookTx Pol
192.168.0.2 23/04 17:27:17.760
<151>M1: CID:OnHookTx Pol
192.168.0.2 23/04 17:27:17.770
<151>M1: Start DTMF/FSK
192.168.0.2 23/04 17:27:18.060
<151>M1: Start DTMF/FSK
192.168.0.2 23/04 17:27:18.070
<151>M1: CID:DONE
192.168.0.2 23/04 17:27:18.510
<151>M1: CID:DONE
192.168.0.2 23/04 17:27:18.520
<159>M0: system request reboot
192.168.0.1 23/04 17:28:04.277
<159>M0: fu:1:7380, 0038 0049 043c 0445 0001
192.168.0.1 23/04 17:28:07.347
<151>M0: IDBG: pppld
192.168.0.1 23/04 17:28:07.357
<159>M0: fu:1:742e, 03e4 05b0 0001
192.168.0.1 23/04 17:28:07.437
<134>M1: System started: [email protected], reboot reason:H0
192.168.0.2 23/04 17:28:22.570
<134>M1: System started: [email protected], reboot reason:H0
192.168.0.2 23/04 17:28:22.570
<143>M1: subnet mask: 255.255.255.0
192.168.0.2 23/04 17:28:22.570
<143>M1: gateway ip: 192.168.0.1
192.168.0.2 23/04 17:28:22.570
<143>M1: dns servers(1): 192.168.0.2 23/04 17:28:22.580
<143>M1: 192.168.0.1 192.168.0.2 23/04 17:28:22.580
<143>M1:
192.168.0.2 23/04 17:28:22.580
<159>M0: IDBG: st-0
192.168.0.1 23/04 17:28:22.690
<159>M1: mslink server task up (1)
192.168.0.2 23/04 17:28:24.560
<134>M2: System started: [email protected], reboot reason:H0
192.168.0.3 23/04 17:28:25.620
<134>M2: System started: [email protected], reboot reason:H0
192.168.0.3 23/04 17:28:25.620
<143>M2: subnet mask: 255.255.255.0
192.168.0.3 23/04 17:28:25.620
<143>M2: gateway ip: 192.168.0.1
192.168.0.3 23/04 17:28:25.620
<143>M2: dns servers(1): 192.168.0.3 23/04 17:28:25.630
<143>M2: 192.168.0.1 192.168.0.3 23/04 17:28:25.630
<143>M2:
192.168.0.3 23/04 17:28:25.630
<134>M3: System started: [email protected], reboot reason:H0
192.168.0.4 23/04 17:28:25.630
<134>M3: System started: [email protected], reboot reason:H0
192.168.0.4 23/04 17:28:25.630
<143>M3: subnet mask: 255.255.255.0
192.168.0.4 23/04 17:28:25.630
<143>M3: gateway ip: 192.168.0.1
192.168.0.4 23/04 17:28:25.630
<143>M3: dns servers(1): 192.168.0.4 23/04 17:28:25.640
<143>M3: 192.168.0.1 192.168.0.4 23/04 17:28:25.640
<143>M3:
192.168.0.4 23/04 17:28:25.640
<159>M2: mslink server task up (2)
192.168.0.3 23/04 17:28:27.451
<159>M3: mslink server task up (3)
192.168.0.4 23/04 17:28:27.521
<159>M1: IDBG: st-0
192.168.0.2 23/04 17:28:28.221
<159>M1: fs:008275:008693:131072
192.168.0.2 23/04 17:28:28.321
<159>M1: fls:af:1:0:0
192.168.0.2 23/04 17:28:28.331
<159>M1: fbr:0:3000:3000:039a9:0002:0001:6.1.12
192.168.0.2 23/04 17:28:28.331
<159>M1: PLKUP: 8192, 2102, 12, 1.5
192.168.0.2 23/04 17:28:28.351
<159>M1: fu:0:39bb, 0003 0001
192.168.0.2 23/04 17:28:28.511
<159>M1: mslink client task (1) gw=192.168.0.1 ip=192.168.0.2
192.168.0.2 23/04 17:28:28.541
<159>M2: IDBG: st-0
192.168.0.3 23/04 17:28:29.121
<159>M2: fs:008200:008342:131072
192.168.0.3 23/04 17:28:29.221
<159>M2: fls:af:1:0:0
192.168.0.3 23/04 17:28:29.221
<159>M2: fbr:0:3000:3000:035af:0002:0001:6.1.12
192.168.0.3 23/04 17:28:29.221
<159>M2: PLKUP: 8192, 2102, 12, 1.5
192.168.0.3 23/04 17:28:29.241
<159>M0: MSLINK module 1 is at 192.168.0.2
192.168.0.1 23/04 17:28:29.291
<159>M0: MSLINK code module 1: 0(32) sn:0
192.168.0.1 23/04 17:28:29.341
<159>M2: fu:0:35c1, 0003 0001
192.168.0.3 23/04 17:28:29.401
<159>M3: IDBG: st-0
192.168.0.4 23/04 17:28:30.191
<159>M3: fs:008200:008351:131072
192.168.0.4 23/04 17:28:30.281
<159>M3: fls:af:1:0:0
192.168.0.4 23/04 17:28:30.291
<159>M3: fbr:0:3000:3000:0423d:0002:0001:6.1.12
192.168.0.4 23/04 17:28:30.291
<159>M3: PLKUP: 8192, 2102, 12, 1.5
192.168.0.4 23/04 17:28:30.311
<159>M3: fu:0:424f, 0003 0001
192.168.0.4 23/04 17:28:30.471
<159>M2: mslink client task (2) gw=192.168.0.1 ip=192.168.0.3
192.168.0.3 23/04 17:28:31.441
<159>M0: MSLINK module 2 is at 192.168.0.3
192.168.0.1 23/04 17:28:32.261
<159>M0: MSLINK code module 2: 0(32) sn:0
192.168.0.1 23/04 17:28:32.461
<159>M3: mslink client task (3) gw=192.168.0.1 ip=192.168.0.4
192.168.0.4 23/04 17:28:32.511
<159>M0: MSLINK module 3 is at 192.168.0.4
192.168.0.1 23/04 17:28:33.431
<159>M0: MSLINK code module 3: 0(32) sn:0
192.168.0.1 23/04 17:28:34.211
<159>M0: fs:025278:025278:131072
192.168.0.1 23/04 17:28:37.382
<159>M0: fls:af:1:0:0
192.168.0.1 23/04 17:28:37.382
<159>M0: fbr:1:3000:3000:1742e:0004:0005:6.1.12
192.168.0.1 23/04 17:28:37.382
<159>M0: fhs:01:0:0001:upg:app:0:5.1.10
192.168.0.1 23/04 17:28:37.382
<159>M0: fhs:02:0:0002:upg:app:1:5.1.10
192.168.0.1 23/04 17:28:37.422
<159>M0: fhs:03:0:0003:upg:app:2:5.1.10
192.168.0.1 23/04 17:28:37.482
<159>M0: fhs:04:0:0004:upg:app:0:6.1.12
192.168.0.1 23/04 17:28:37.542
<159>M0: fhs:05:0:0005:upg:app:1:6.1.12
192.168.0.1 23/04 17:28:37.592
<159>M0: fhs:06:0:0006:upg:app:2:6.1.12
192.168.0.1 23/04 17:28:37.632
<159>M0: PLKUP: 8192, 2102, 12, 1.5
192.168.0.1 23/04 17:28:37.692
<159>M0: fu:1:7440, 0003 0001
192.168.0.1 23/04 17:28:38.182
<159>M0: mslink P:12378 V:53243
192.168.0.1 23/04 17:28:50.064
<159>M1: CC_init
192.168.0.2 23/04 17:28:52.534
<134>M1: SLIC is si3215
192.168.0.2 23/04 17:28:52.614
<134>M1: SLIC is si3215
192.168.0.2 23/04 17:28:52.624
<159>M1: IDBG[0]:4
192.168.0.2 23/04 17:28:53.124
<159>M1: IDBG[1]:3
192.168.0.2 23/04 17:28:53.124
<159>M2: CC_init
192.168.0.3 23/04 17:28:53.434
<134>M2: SLIC is si3215
192.168.0.3 23/04 17:28:53.514
<134>M2: SLIC is si3215
192.168.0.3 23/04 17:28:53.524
<159>M2: IDBG[0]:4
192.168.0.3 23/04 17:28:54.024
<159>M2: IDBG[1]:3
192.168.0.3 23/04 17:28:54.024
<134>M1: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:28:54.254
<134>M1: [0]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:28:54.254
<134>M1: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:28:54.254
<134>M1: [1]Reg Addr Change(0) 0:0->a800104:6060
192.168.0.2 23/04 17:28:54.264
<159>M3: CC_init
192.168.0.4 23/04 17:28:54.504
<134>M3: SLIC is si3215
192.168.0.4 23/04 17:28:54.584
<134>M3: SLIC is si3215
192.168.0.4 23/04 17:28:54.594
<159>M3: IDBG[0]:4
192.168.0.4 23/04 17:28:55.084
<159>M3: IDBG[1]:3
192.168.0.4 23/04 17:28:55.084
<159>M0: CC_init
192.168.0.1 23/04 17:28:55.965
<134>M0: SLIC is si3215
192.168.0.1 23/04 17:28:56.525
<134>M0: SLIC is si3215
192.168.0.1 23/04 17:28:56.525
<159>M0: fu:1:7455, 03e4 05b0 0001
192.168.0.1 23/04 17:28:56.605
<159>M0: IDBG[0]:6
192.168.0.1 23/04 17:28:57.025
<159>M0: IDBG[1]:4
192.168.0.1 23/04 17:28:57.025
<134>M0: System started: [email protected], reboot reason:C200
192.168.0.1 23/04 17:29:23.348
<134>M0: System started: [email protected], reboot reason:C200
192.168.0.1 23/04 17:29:23.348
<143>M0: subnet mask: 255.255.255.255
192.168.0.1 23/04 17:29:23.348
<143>M0: gateway ip: 10.128.1.254
192.168.0.1 23/04 17:29:23.358
<143>M0: dns servers(2): 192.168.0.1 23/04 17:29:23.358
<143>M0: 4.2.2.1 192.168.0.1 23/04 17:29:23.358
<143>M0: 4.2.2.2 192.168.0.1 -
Trying to configure a PPPoE session on a 7206VXR however all the commands such as ppp on an eth interface, vpdn in global config are missing.
The IOS says that its supported:
ROM: System Bootstrap, Version 12.3(4r)T3, RELEASE SOFTWARE (fc1)
BOOTLDR: 7200 Software (C7200-KBOOT-M), Version 12.3(9), RELEASE SOFTWARE (fc2)
System image file is "disk2:c7200-pk9u2-mz.123-14.T3.bin"
which is service provider with ipsec etc..
Am I missing something obvious? I also have a 8000 user license but at the moment in the labs only need a couple of lines and the docs say <1000 no license needs to be enabled.GP, Thanks for that, I have access to the tool and thought I'd run it through, just checked again and got:
Image Name DRAM Flash Life Cycle
c7200-pk9u2-mz.12.3-14.T 128 48 ED
AAA Double Authentication Secured by Absolute Timeout
Accounting server connectivity failure and recovery detection
ACL - Support for Non-Contiguous Port Ranges on an ACE
PPP MLP MRRU negotiation configuration
PPPoE Session Limit per NAS port
So must have seen that PPPoE session Limit per NAS port and registered it as supporting pppoE.
Currently getting the distributor to provide your suggested.
It's current use is only as a B-RAS within an Inter-operability model and so we were trying as many full features northbound into a core of a err chinese router :)
Will let you know how it works.
Craig.
Maybe you are looking for
-
Does Verizon Wireless really care about its customers?
I tried to purchase online the free Ellipsis tablet on Black Friday with the 2 year agreement. The website directed me through the process and then told me I had to change my current plan. I didn't want to change my plan. So I backed out of the pro
-
Hi, can some one please help me, how do i restoe my i cloud if the phone will not connect to Wifi
my Iphones will not work how do i conect ot the icloud and restor my phone
-
Hi I am having 2 files in which one file having 20 records and another file is having 10 records I need to merge two files using BPm how can I merge two files without correlation? Any solution regarding this Regards Krishna
-
Shipping of iPhone 5 and accessories
I ordered my iPhone 5 online, along with Applecare and the adapter with the old iPhone/ipod female charging port and the new iPhone charging port. Yesterday I received my iPhone, but there was no adapter or Applecare included with what was shipped t
-
Receipients missing in Message type ACPJMM ( message B1003)
HI experts, I'm getting a strange error while i try to post a goods receipt or goods issue. the message says receipients missing in Message type ACPJMM ( message B1003) The Idoc is passed through a ALE layer and the message is assigned with three rec