[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
I'll attach a log file below.
gabriel rosenkoetter wrote:
All the nasty things you say about DSLAMs is true, but Paul's
talking about the box with the blinky lights in his house. And he's
right, it's not a modem, properly, but a bridge (probably; some SDSL
lines bear full-fledged routers, depending on the protocol that goes
upstream to the DSLAM). It's not doing its own analog signalling,
it's converting between two kind of Ethernet; PPPoE or ATM on one
side and regular 802.3 (or .2, or .11, or whatever) on the other
side.
WAN Type: PPP over Ethernet (2.60 build 6a , Tue,Oct 8 2002) Display time: Mon 10 Feb 2003 09:31:09 PM EST Mon 10 Feb 2003 08:42:04 PM EST PPPoE start to dial-up *PADI sent *PADI sent *PADI sent *DOD:TCP trigger from 192.168.32.2:3980 to 66.237.117.10:80 Mon 10 Feb 2003 08:42:13 PM EST PPPoE start to dial-up *PADI sent *PADI sent *PADI sent *DOD:TCP trigger from 192.168.32.2:3981 to 66.237.117.10:80 Mon 10 Feb 2003 08:42:29 PM EST PPPoE start to dial-up *PADI sent *PADI sent *PADI sent *DOD:TCP trigger from 192.168.32.2:3981 to 66.237.117.10:80 Mon 10 Feb 2003 08:42:38 PM EST PPPoE start to dial-up *PADI sent *PADO recv 0016 PSKN-6400-2-NRP3 *PADR sent *PADS recv 8003 6150 *PAP3: OK *IPCP3: IP is 151.204.214.217 *IPCP3: DNS0 is 151.204.0.84 *IPCP3: DNS1 is 151.197.0.39 Mon 10 Feb 2003 09:23:47 PM EST Connection is broken Mon 10 Feb 2003 09:23:47 PM EST PPPoE start to hang-up *PADT sent *DOD:TCP trigger from 192.168.32.2:4044 to 66.237.117.10:80 Mon 10 Feb 2003 09:23:52 PM EST PPPoE start to dial-up *PADI sent *PADI sent *PADI sent *DOD:192.168.32.2 query DNS for mail.dpagin.net Mon 10 Feb 2003 09:23:56 PM EST PPPoE start to dial-up *PADI sent *PADO recv 0016 PSKN-6400-2-NRP3 *PADR sent *PADS recv 8003 6C52 *PAP3: OK *IPCP3: IP is 151.204.214.217 *IPCP3: DNS0 is 151.204.0.84 *IPCP3: DNS1 is 151.197.0.39 Mon 10 Feb 2003 09:29:19 PM EST Connection is broken Mon 10 Feb 2003 09:29:19 PM EST PPPoE start to hang-up Mon 10 Feb 2003 09:29:20 PM EST 192.168.32.2 login successful *PADT sent *DOD:triggered internally Mon 10 Feb 2003 09:29:29 PM EST PPPoE start to dial-up *PADI sent *PADI sent *PADI sent *DOD:triggered internally Mon 10 Feb 2003 09:29:36 PM EST PPPoE start to dial-up *PADI sent *PADI sent *PADI sent *DOD:TCP trigger from 192.168.32.2:4087 to 66.237.117.10:80 Mon 10 Feb 2003 09:29:41 PM EST PPPoE start to dial-up *PADI sent *PADI sent *PADI sent *DOD:TCP trigger from 192.168.32.2:4087 to 66.237.117.10:80 Mon 10 Feb 2003 09:29:47 PM EST PPPoE start to dial-up *PADI sent *PADI sent *PADI sent *DOD:TCP trigger from 192.168.32.2:4088 to 66.237.117.10:80 Mon 10 Feb 2003 09:30:03 PM EST PPPoE start to dial-up *PADI sent *PADI sent *PADI sent *DOD:TCP trigger from 192.168.32.2:4088 to 66.237.117.10:80 Mon 10 Feb 2003 09:30:12 PM EST PPPoE start to dial-up *PADI sent *PADI sent *PADI sent *DOD:prot 1 trigger from 192.168.32.2 to 64.58.79.230 Mon 10 Feb 2003 09:30:18 PM EST PPPoE start to dial-up *PADI sent *PADI sent *PADI sent *DOD:TCP trigger from 192.168.32.2:4089 to 66.237.117.10:80 Mon 10 Feb 2003 09:30:28 PM EST PPPoE start to dial-up *PADI sent *PADI sent *PADI sent *DOD:TCP trigger from 192.168.32.2:4089 to 66.237.117.10:80 Mon 10 Feb 2003 09:30:37 PM EST PPPoE start to dial-up *PADI sent *PADI sent *PADI sent *DOD:prot 1 trigger from 192.168.32.2 to 64.58.79.230 Mon 10 Feb 2003 09:30:45 PM EST PPPoE start to dial-up *PADI sent *PADI sent *PADI sent *DOD:TCP trigger from 192.168.32.2:4090 to 66.237.117.10:80 Mon 10 Feb 2003 09:30:53 PM EST PPPoE start to dial-up *PADI sent *PADI sent *PADI sent *DOD:TCP trigger from 192.168.32.2:4090 to 66.237.117.10:80 Mon 10 Feb 2003 09:31:02 PM EST PPPoE start to dial-up *PADI sent *PADI sent *PADI sent