You should be close to the explanation.
When I installed the new slackware 3.4 version I noticed that the
route behaviour was different. The former version gave route information
without a delay. The current route does something extra.
Route and also netstate call to the internet:
This happens after netstat -r:
First there is a default route sl0 (the slip line)
Then there is no default route for some while
Thereafter the ppp0 default route comes up
artemis:/var/log# diald
artemis:/var/log# netstat -r
Kernel IP routing table
Destination Gateway
Genmask Flags
MSS Window irtt Iface
192.168.0.2 *
255.255.255.255 UH 1500 0
0 sl0
localnet
*
255.255.255.0 U 1500 0
0 eth0
loopback
*
255.0.0.0 U
3584 0 0 lo
default
*
0.0.0.0 U
1500 0 0 sl0
artemis:/var/log# netstat -r
Kernel IP routing table
Destination Gateway
Genmask Flags
MSS Window irtt Iface
192.168.0.2 *
255.255.255.255 UH 1500 0
0 sl0
localnet
*
255.255.255.0 U 1500 0
0 eth0
loopback
*
255.0.0.0 U
3584 0 0 lo
artemis:/var/log# netstat -r
Kernel IP routing table
Destination Gateway
Genmask Flags
MSS Window irtt Iface
192.168.0.2 *
255.255.255.255 UH 1500 0
0 sl0
localnet
*
255.255.255.0 U 1500 0
0 eth0
loopback
*
255.0.0.0 U
3584 0 0 lo
artemis:/var/log# netstat -r
Kernel IP routing table
Destination Gateway
Genmask Flags
MSS Window irtt Iface
192.168.0.2 *
255.255.255.255 UH 1500 0
0 sl0
speed.xs4all.ne *
255.255.255.255 UH 1500 0
0 ppp0
localnet
*
255.255.255.0 U 1500 0
0 eth0
loopback
*
255.0.0.0 U
3584 0 0 lo
default
*
0.0.0.0 U
1500 0 0 ppp0
Either the sl0 default route or the missing one might be the cause.
Jaap
Dan Cyr wrote:
Most likely you have a defaultroute to eth0route del default eth0 should do it.
I'm not sure where in slackware you can remove it on bootup. In redhat it's /etc/sysconfig/network so try find / -iname network to see if slackware uses the same file ( /etc/sysconfig doesn't exist in slackware though).
Of course you could put the route del command in /etc/rc.d/rc.local
Then again maybe this isn't your problem.....if it isn't then I don't know what is.
Dan
At 01:06 PM 6/6/98 +0200, Dr.J.C.Woestenburg wrote:
>>>>Diald lookup failures on linux only
Hi,
I'm using Slackware Linux 3.4 on a Pentium II 233 and diald 1.6.5 patch.
Diald has worked OK on Slackware version 3.1, however migrating to 3.4 from
scratch on has caused lookup failures slightly before the moment of
dialing.Prior to dialing up to the moment that the ppp-connection is made,
lookup failures are reported by netscape, ftp, telnet etc.
This only occurs for programs launched from the linux station.Par example: ftp returns
Hostname lookup failure
When I retry after the connection has been made, the world is connected.I'm using a local network with a firewall, masquerade and Samba.
On the local net are windows NT 3.51 and NT 4.0 as main workstations.Firing up netscape, ftp, telnet, etc from the NT stations works fine.
Here, there are no problems with lookup of names or IP-numbers.It looks as if diald works correct and that the problem should be in
some of the Slackware programs, however, it might be that procedures
are different for linux and NT.Is there a conflict in procedures between diald and new linux functions?
Does somebody knows the solution.
Thanks in advance,
Jaap Woestenburg
-- ------------------------------ *TALO bv, Lijsterlaan 379, 1403 AZ Bussum,The Netherlands tel/fax +31-35-69 32 801 tel +31-65 46 83 544 e-mail [EMAIL PROTECTED] <http://www.xs4all.nl/~talo/>http://www.xs4all.nl/~talo/ ------------------------------- To unsubscribe from this list: send the line "unsubscribe linux-diald" in the body of a message to [EMAIL PROTECTED]
-- ------------------------------ *TALO bv, Lijsterlaan 379, 1403 AZ Bussum,The Netherlands tel/fax +31-35-69 32 801 tel +31-65 46 83 544 e-mail [EMAIL PROTECTED] http://www.xs4all.nl/~talo/ ------------------------------
