Lourdes Jones wrote:
> I'm assuming you are pointing the finger at diald because you've already
> tested these settings on a normal (manual) connection from this same machine
> and everything works as expected.
Yes that's right... :-)
> If you open end masq (everything thing from your local network and don't
> specify the interface) then when you use diald traffic now has the address
> of the slip link and that is used to determine what goes in and out of the
> ppp link (cable modem).
well...that's not a ppp link, but a SLIP link....
> Please verify that you are only masquerading traffic that goes comes from
> your local network and goes out your cable modem. This often solves strange
> problems and should speed things up a bit since the kernel does not have to
> masquerade the packet more than once.
In that case my problems should be solved after a simple ipchains -F, so
I tried that, no luck however, problem persists.
I forgot to mention one thing in my initial message though: I understand
that diald should bring up two connections, one SLIP proxy, and one
physical link (also SLIP in my case). I'm only seeing the second link,
sl1, but in my messages log I see that diald tries to do something with
sl0 (it displays the "usual" SIOCSIMETRIC errors, since I'm using
2.2.12)
Kick Glorie
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
