rupert
asked on
diald/dynamic IP: problem persists
Hmmm... Don't know why the question vanished...
Well, it's still not working. :-(
My diald config by now:
mode slip
mtu 1006
local 192.168.1.7 # fake IP
remote 152.158.4.33 # remote IP is known
dynamic
dlip-mode local
-reroute # tried reroute, as well
buffer-packets
defaultroute
device /dev/modem
lock
modem
connect '...
speed 57600
crtscts
-f /etc/...
fifo ...
upgraded kernel to 2.0.29,
diald 0.16
net-tools 1.32 alpha
it seems that diald *does* send the first packets, but still with the fake IP as source address. So I never get an answer.
What's the trick?
I've been thinking about modifying diald to correct the IP in buffered packets before they get send out. (Looked at code, seems pretty easy).
Would that make sense? Or would whichever program sent that packet be confused, because it expected to be using the fake IP?
Thanks a lot for your assistance,
Rupert
Well, it's still not working. :-(
My diald config by now:
mode slip
mtu 1006
local 192.168.1.7 # fake IP
remote 152.158.4.33 # remote IP is known
dynamic
dlip-mode local
-reroute # tried reroute, as well
buffer-packets
defaultroute
device /dev/modem
lock
modem
connect '...
speed 57600
crtscts
-f /etc/...
fifo ...
upgraded kernel to 2.0.29,
diald 0.16
net-tools 1.32 alpha
it seems that diald *does* send the first packets, but still with the fake IP as source address. So I never get an answer.
What's the trick?
I've been thinking about modifying diald to correct the IP in buffered packets before they get send out. (Looked at code, seems pretty easy).
Would that make sense? Or would whichever program sent that packet be confused, because it expected to be using the fake IP?
Thanks a lot for your assistance,
Rupert
Ever thought about using ppp via diald?
ASKER
Not an option, neither is static IP. :(
Rupert
Rupert
Tried 'noipdefault' and using 0.0.0.0 as your locIP ?
ASKER
noipdefault is a pppd-option, though. I use SLIP.
ASKER
Adjusted points to 147
ASKER
ok, I got a ppp connection now, still with dynamic IP address.
It still doesn't work!
It still doesn't work!
ASKER
Quite some experts here...
I've got the problem solved now. It required a change to the kernel if one didn't want to rewrite ip-masquerading - which I almost did.
So much for 'I got it working' from whoever cashed in the points when I asked the question the first time.
I'm out of here...
I've got the problem solved now. It required a change to the kernel if one didn't want to rewrite ip-masquerading - which I almost did.
So much for 'I got it working' from whoever cashed in the points when I asked the question the first time.
I'm out of here...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.