I backed out my `115200' addition to /etc/ppp/options.ttyS0 and instead
put it in /etc/ppp/peers/ppp0 as requested but it only works
intermittently.
This is because there's various ways of going online. Using
network-admin to `Activate the modem connection' I see pppd has been
given all its options on the command line.
/etc/ppp/options{,.ttyS*} seems the right place for the baud rate since
pppd always looks there regardless of how it was started and we can't
guarantee `call' will always be used by everything.
I backed out my `115200' addition to /etc/ppp/ options. ttyS0 and instead
put it in /etc/ppp/peers/ppp0 as requested but it only works
intermittently.
This is because there's various ways of going online. Using
network-admin to `Activate the modem connection' I see pppd has been
given all its options on the command line.
root 8904 ? network-admin
/usr/share/ setup-tool- backends/ scripts/ network- conf
--report
nocrtscts defaultroute usepeerdns user
inputplus. freeserve. co.uk connect /usr/sbin/chat -v
-f /tmp/network- admin-chat- script- 7vrIChYf4
/tmp/network- admin-chat- script- 7vrIChYf4
root 8907 pts/3 perl
root 9055 ttyS0 /usr/sbin/pppd /dev/ttyS0 noauth nopersist
root 9066 ttyS0 /usr/sbin/chat -v -f
Without a `call ppp0' /etc/ppp/peers/ppp0 is ignored.
Going online using modem_applet does use `call' so that works.
root 10274 ttyS0 /usr/sbin/pppd call ppp0 s/ppp0
root 10303 ttyS0 /usr/sbin/chat -v -f /etc/chatscript
As does `ifup ppp0' as root.
/etc/ppp/ options{ ,.ttyS* } seems the right place for the baud rate since
pppd always looks there regardless of how it was started and we can't
guarantee `call' will always be used by everything.