ipmasq: losing packets for a while after connecting with diald

[Daniel Barclay <dsb@smart.net>]

Since I installed the Debian ipmasq package, I've been having trouble 
with network connectivity for a little while after auto-dialing with diald.  

If I do something like "ping -c 12 -i 10 x.y.x.w" to bring up a connection,
diald gets triggered and brings up a connection, but the ping command's 
output says:

  ping: sendto: Operation not permitted
  ping: wrote x.y.z.w 64 chars, ret=-1

several times before working right.

If I trigger auto-dialing with my browser, I have to try several times
before the browser is able to resolve host names and get data.


Note that the symptoms are not the same as the lost-first-packet problem 
that /proc/sys/net/ipv4/ip_dynaddr fixes.  (I had already set that when
I set up diald.)  It's not just packets sent before diald brings up the
connection, but seems to be packets sent even after the connection is
brought up (for maybe 10 or 20 seconds).

Before I installed ipmasq, diald and ppp seemed to be working fine.

When I installed ipmasq, I did remember to add calls to ipmasq in 
/etc/diald/addroute and /etc/diald/delroute.



Any ideas or pointers?

Thanks.

Daniel
-- 
Daniel Barclay
dsb@smart.net



-- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org