This has been discussed to death on the mailing list and is also covered in
the diald FAQ.
I believe there may be some work arounds based on posting over recent
months and you should look up old postings in order to determine if this is
the case.
I myself don't worry about it because my link is only for my own use and as
long as I know what is happening it's OK also most of the time I use the
same IP even though it is being allocated dynamically it never changes
since I dial through a server at work which I control.
In short the most likely reason your first packet fails is because you use
dynamic IP allocation. This requires you to "guess" an initial IP for
setting up the proxy ppp device and to put this is your diald.conf. The
first packet has this FALSE IP as it's source address. Once you connect you
get a new authentic and also different IP and so amazingly you can't get a
reply to your first packet since it is going to some other address rather
than the one your ISP has allocated.
An analogy of this is:
imagine you send a letter to someone with your return address as your
current address. Soon after you move to a new residence and some time later
the recipient of your letter writes back. Clearly unless they have
additional information they will send the reply to your old address and
unless the normal routing of mail is circumvented (ie. you request old mail
to be redirected) you will never get the return letter.
The only way to fix this is to "hold" the first packet and then once th
econnection is established for diald to change the source IP to that which
has just been allocated. As I said I believe this can be done and there
have been discussions about it in the past
If it turns out that it isn't possible in the current diald then maybe Mike
could explain why not and maybe I could tackle the task of writing
something to fix it but as I said I think there is already a solution.
Wilson Fletcher
----------
From: Kenward Vaughan[SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, 20 June 2000 9:56
To: [EMAIL PROTECTED]
Subject: diald doesn't forward original message
Hi!
I've been struggling to get diald working on my system (not having a
computer science background, much less Linux... :). I use Debian, and
finally got a connection to work under pap authentication by setting the
name option for pppd and toying with the pap-secrets file.
The problem I have at this point is figuring out why diald does not
properly
forward the original signal which triggers it in the first place. I've
been
using fetchmail with a regular account to test things. Whenever this is
done, it simply sits forever after the connection has been established. If
I cancel it with a ^C then resend, it works as expected.
My ipchains rules are 1) completely open on the internal net prior to
connection (i.e. input, forward, and output are all ACCEPT), then 2) are
changed using Ian Hall-Beyer's script (can forward if desired) from ip-up.
A "complete" syslog with debugging set in diald and pppd is attached. Does
anyone see what the issue is? Would appreciate any help!
TIA,
Kenward Vaughan
--
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
<<File: dialdLog.txt>>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
