-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tammo Block wrote: > Hello ! > > > I did the following : > > 1.) login with wrong username (19:32:15) > 2.) Choose mirror -> fails (19:32:42) > 3.) main-menu -> choose ppp again (19:33:39) > 4.) enter correct values and try again (19:34:16) > 5.) Success (19:34:21)
I see :-/ > Jan 25 19:32:08 DEBUG:ppp-udeb: setting pppoe connection on eth0 > Jan 25 19:32:14 kernel: CSLIP: code copyright 1989 Regents of the University > of California > Jan 25 19:32:14 kernel: PPP generic driver version 2.4.2 > Jan 25 19:32:14 kernel: NET: Registered protocol family 24 > Jan 25 19:32:14 pppd[4963]: Plugin rp-pppoe.so loaded. > Jan 25 19:32:14 ppp-udeb: Plugin rp-pppoe.so loaded. > Jan 25 19:32:14 pppd[4964]: pppd 2.4.4 started by (unknown), uid 0 > Jan 25 19:32:14 pppd[4964]: PPP session is 1833 > Jan 25 19:32:14 net/hw-detect.hotplug: Detected hotpluggable network > interface ppp0 > Jan 25 19:32:14 pppd[4964]: Using interface ppp0 > Jan 25 19:32:14 pppd[4964]: Connect: ppp0 <--> eth0 > Jan 25 19:32:15 pppd[4964]: CHAP authentication succeeded: CHAP > authentication success, unit 9510 > Jan 25 19:32:15 pppd[4964]: CHAP authentication succeeded > Jan 25 19:32:15 pppd[4964]: peer from calling number 00:30:88:01:D9:F4 > authorized It seems the setup in the case of your ISP's server is broken. Indeed, it accepts bad logins without giving any clues that the login info might be bad (compare to messages below). I suspect this is done intentionally by your ISP and all http traffic is redirected to a page that explains how to contact the ISP if the login info is bad. (Needless to say that the assumption that the mostly/only/first used protocol is stupid, but, anyhow, is their choice). As far as I am concerned, I think the best solution is to warn in the installation guide about such abnormal behaviour/setups. > Jan 25 19:33:50 DEBUG:ppp-udeb: setting pppoe connection on eth0 > Jan 25 19:34:15 pppd[5432]: Plugin rp-pppoe.so loaded. > Jan 25 19:34:15 ppp-udeb: Plugin rp-pppoe.so loaded. > Jan 25 19:34:15 pppd[5433]: pppd 2.4.4 started by (unknown), uid 0 > Jan 25 19:34:15 pppd[5433]: PPP session is 5395 > Jan 25 19:34:15 net/hw-detect.hotplug: Detected hotpluggable network > interface ppp0 > Jan 25 19:34:15 pppd[5433]: Using interface ppp0 > Jan 25 19:34:15 pppd[5433]: Connect: ppp0 <--> eth0 > Jan 25 19:34:16 pppd[5433]: CHAP authentication succeeded: CHAP > authentication success, unit 19106 > Jan 25 19:34:16 pppd[5433]: CHAP authentication succeeded > Jan 25 19:34:16 pppd[5433]: peer from calling number 00:30:88:01:D9:F4 > authorized Tammo, Frans, what do you think about this approach? - -- Regards, EddyP ============================================= "Imagination is more important than knowledge" A.Einstein -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFvbrRY8Chqv3NRNoRAs96AJ9rVt7mc6O8aXXbyV/0yuCmn7pRjgCfb+mQ E/7MYVQWWmp2Q/DBHwl6los= =yVDV -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
