diald-0.99.1, dialmon-0.7, linux kernel 2.0.33 libc5 All works ok for modem/ppp connections. Now I'm trying to set up the connection through an isdn-router in place of the modem; I want to keep diald because it gives me more granular control over the packets and timeouts. I replaced all the routing script with the ifsetup script. linux is 10.0.0.2 isdn-router is 10.0.0.20 A) When diald is started these are the routes: 10.0.0.20 0.0.0.0 255.255.255.255 UH 0 0 0 sl0 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 108 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 70 lo 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 sl0 B) when the connections goes up these are the routes: 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 109 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 70 lo 0.0.0.0 10.0.0.20 0.0.0.0 UG 0 0 0 eth0 When the connection is down again the routes are A) again. All works fine (all workstations can access the internet through linux; linux is their gateway, not the router itself) but the monitoring: when I'm in A) and debug1 I can see the packet ignored and accepted in the log; when I'm in B) everyone can surf the internet but diald stop monitoring (no more accepted/ignored packets with debug1), so even dialmon can't show the load. This has the side effect that diald drop the connection very soon as it doesn't SEE any traffic. This is what I see when the link goes up: Sep 4 15:40:56 b diald[30833]: Calling site 10.0.0.20 Sep 4 15:40:56 b diald[30833]: Connected to site 10.0.0.20 Sep 4 15:40:56 b diald[30833]: Open device eth0 Sep 4 15:40:56 b diald[30833]: Changed snoop device to eth0 Sep 4 15:40:59 b diald[30833]: FIFO: changing debug flags to 0x1 Maybe diald gets confused as it snoops on eth0? Should I use an alias (as eth0:1) so that eth0:1 would be dedicated to the connection with the router? Or it is so (no monitoring with dev interfaces) by design? Thanks. -- [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-diald" in the body of a message to [EMAIL PROTECTED]
