Comment 9 for bug 12507

Carlos, actually, there're a few more things I need to set for it to work for
me. I can manually change it in network.pl or profiles.xml, but that's obviously
not the best solution.

I don't see any GUI option to choose whether remote peer needs to authenticate
(when connecting to ISP, it most usually doesn't, since I'm the one who is
authenticating, so I should use "noauth" instead of "auth"). I also add "user
ssegan" to pppd command line, and remove "ogin:"/"assword:" detection from the
chatscript (as above). Of course, you'd need to append '"username" *
"password"' line to /etc/ppp/pap-secrets and /etc/ppp/chap-secrets, for it to
work (I have it already in there, put by pppconfig).

The final problem is handling of volume settings: my ISDN modem doesn't accept
AT&FH0M0 command, and what follows it in the chatscript is "OK-AT-OK-ATDT...",
which fails for me, because ATM0 fails (it gives out "ERROR" instead of "OK",
and ABORT ERROR is set).

All these changes finally made it possible for me to connect via network-admin
"Activate" button on "Modem connection". "Deactivate" doesn't work yet (you
ought to shut down "pppd" which was started, instead of only "ifconfig down
ppp0"), and neither does the modem applet from gnome-applets (I get "ppp0" not
found from chat program in the syslog).

On Debian and Ubuntu, I'd prefer if configuration was done a bit differently.
I.e. there would be one chatscript per connection, and for connecting you'd call
"pppd call ppp0", "pppd call ppp1", etc.

Though, I should definitely open up a bug on bugzilla.gnome.org for all of this
(I first thought it was only Ubuntu integration problem).