I've been running diald on my linux box for a year now, with absolutely no
problems (dialup to school modem server, receive dynamically allocated IP,
using SLIP protocol).
The trouble started recently when I purchased a second computer and hooked
them both up via Ethernet.
I've done everything by the book, picked a local network address - 192.168.27,
local IP numbers for both computers (192.168.27.5 and 192.168.27.10), and
set up everything else exactly how the manuals say...
The problem is, whenever diald is started on the "server" (i.e., the one with
the modem), it renders the local network unusable - i.e. I can't ping, telnet,
ftp, or traceroute, or anything else between the two (192.168.27.5 and
192.168.27.10) computers.
When I kill the diald process, everything works perfectly. I even started
dip manually, started IP masquerading, and I can reach out from both computers
anywhere to the Internet...
Does anybody have an idea why diald would cause the local network to freeze up?
Thanks in advance,
Gabriel
P.S. If you think you can help me, or if this has happened to you, let me know
and I can post my config files and stuff...
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
