First of all, pppd command is passed a "connect" using *backticks* instead of
the regular quotes for calling chat program. This is basically the following
line in network.pl:
The other problem I'm having is that the connect script is insisting on matching
on "ogin:" and "password:" prompts, whereas I use PAP authentication (and most
ISPs use PAP or CHAP these days). If I get some time, I'll write a patch for
g-s-t, but I first need to clean up my hard-drive so I can put my Gnome CVS
check-out on it.
It would also be nice to have ports other than /dev/modem, /dev/ttyS[0-3]
auto-detected (perhaps doing a "dmesg |egrep tty[A-Za-z]+[0-9]+" would work out
for GNU/Linux systems?).
Ok, I've identified a few problems.
First of all, pppd command is passed a "connect" using *backticks* instead of
the regular quotes for calling chat program. This is basically the following
line in network.pl:
$command .= " connect `$command_chat -f $chat_file`";
The other problem I'm having is that the connect script is insisting on matching
on "ogin:" and "password:" prompts, whereas I use PAP authentication (and most
ISPs use PAP or CHAP these days). If I get some time, I'll write a patch for
g-s-t, but I first need to clean up my hard-drive so I can put my Gnome CVS
check-out on it.
It would also be nice to have ports other than /dev/modem, /dev/ttyS[0-3]
auto-detected (perhaps doing a "dmesg |egrep tty[A-Za-z]+[0-9]+" would work out
for GNU/Linux systems?).