In preparation for a possible connection to broadband
I shut down the server, opened the lid, added a second
ethernet card and rebooted.
No problem, card was recognised, redhat-config-network
let me create eth1, and all looked ready.
But now my pppd dialup is broken. Up to now I've had a
perfectly working pppd call utvip which dials out, makes
the connection, and sets the default route, and it all
Now I got some weird message in /var/log/messages that the
tty was not a console (pppd is normally called from a CGI
script so that anyone on the local net can bring up the connection
via a web interface). Sure enough, if I type pppd call utvip
in a real terminal, wvdial tries to send its ATZ and stuff to
the terminal I typed the pppd command in! I actually get an ATZ
appearing on the screen. wvdial.conf is correct, identifying
/dev/modem, and that is correctly symlinked to /dev/ttyS0.
If I run wvdial utvip from the terminal manually it dials
and connects fine (which is how I'm sending this).
So WTF should it suddenly decide to pretend the console is a
modem when it's triggered from the pppd command?
I took out the ethernet card in case there was an IRQ conflict
but that doesn't change anything.
Anyone got any suggestions?
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!