Unless you typed that, it looks like the client or client modem is sending
garbarge into the link when the connection is made. I is extraordinarily
improbable that the PM-3 is generating that - I've not seen it and it
shouldn't with the architecture.
>There are also several entries where the denied user is just a bunch of
>garbage such as these couple:
>Jan 13 16:25:46 garcia radius[20132]: auth: access-request from
>ginsberg.ballcom.com (208.4.243.3) denied for unknown user @Xa]I.hby{u#"uL4z
>Jan 13 16:25:46 garcia radius[20133]: auth: access-request from
>ginsberg.ballcom.com (208.4.243.3) denied for unknown user |9wwd%%+V~]2 gj9
>Ne('JueBAc2e@h`f>A(
This looks like it sent text to start which causes us to stop autodetecting
PPP and wait for a text login - then they sent PPP packets. That would
happen if we saw that 'aaat...' junk. Since it is text and doesn't match
a PPP packet we expect a prompt login. Then if PPP data fills the prompt
you see trash logged.
-MZ
-- Lucent Remote Access Division - Chair, Department of Interstitial Affairs Phone: 800-458-9966 510-737-2100 FAX: 510-737-2110 megazone@livingston.com For support requests: support@livingston.com <http://www.livingston.com/> Snail mail: 4464 Willow Road, Pleasanton, CA 94588 - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message.