> > I have diald working, but what happens is that i loose the initial
> > packets.
> This seems to be the fundamental problem with diald. I have seen this
> question over and over (and have it myself) without seeing any answer.
From the Diald FAQ:
2.15 Diald is dropping the first few packets when the link comes up! Why?
You must be runing diald with the buffer-packets option turned off. Turn
this option on if you don't want to drop packets (it is on by default).
Note that if you are using diald with a dynamic IP address, then you might
as well leave the buffer-packets option off, since any packets sent before
the address gets changed can't be replied to anyway.
It's an interesting problem--when the initial packets go out (and
you have a dynamic IP address), then those packets are going out without a
real "source" IP address (because you haven't connected to your ISP yet,
and your computer doesn't know what your IP address is yet). How can a
DNS server reply to an IP address that is either incorrect or else
invalid?
Note that this problem does happen with a static IP (or at least,
it's not supposed to).
I think one possible solution would be for diald to rewrite the
packet headers before sending them out the "real" interface, once the IP
address is actually known. This would basically be like IP Masquerading
the sl0 interface. Chalk that up to the next big feature addition...
--Derek
P.S.> Where is the diald maintainer? I'd like to hear his feedback on
this.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
