[EMAIL PROTECTED] wrote:
> Yes, I tried a myriad of "logical" and "illogical" options. The end result
> was that I once could get both machines to understand their IP and the
> peer IP. BUT, it didn't make the connection work.
Hi,
Instead of banging my head, I did some other stuff. I compiled new
kernels (2.2.13), upgraded hardware on the other machine and started
from scratch.
And,
the ifconfig problem went away !
typing:
ifconfig sl0 133.x.x.x pointopoint 192.168.1.2
worked as it was supposed to be ie I'd get the line
inet addr:133.x.x.x P-t-P:192.168.1.2 Mask:255.255.255.255
by typing ifconfig sl0:
I suspect that ipchains had something to do with this. I heard that there
is a delay before commands are in effect. This because, when forwarding
was on, I'd often get the peer to behave correctly (the one behind the
serial link).
This doesn't make any sense does it ? Or is there a possible conflict
soomewhere ?
Anyhow it works ok now.
Thanks for all suggestions.
Tnx
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
