In my kernel version, 2.2.5, ip_dynaddr.txt says to use:
To enable: echo 1 > /proc/sys/net/ipv4/ip_dynaddr
Verbose mode: echo 2 > /proc/sys/net/ipv4/ip_dynaddr
Disable: echo 0 > /proc/sys/net/ipv4/ip_dynaddr
I have tried diald with the "echo 1" alone, and followed by "echo 2",
but my problems persist. In the meantime, I am using pppd with the
"demand" option. Any idea why diald doesn't refresh the remote IP
address with the one specified in the options file, but instead uses the
remote IP address from the previous call? Also, why would this make the
internet unreachable if new local and remote IP addresses are reassigned
with each new call anyway? I am using Debian 2.1, glibc 2.1.1, and
kernel 2.2.5.
Ben
CL wrote:
>
> Look up /usr/src/linux/Documentation/networking/ip_dynaddr.txt. I believe
> you have to do:
> echo 5 > proc/sys/net/ipv4/ip_dynaddr or
> echo 7 > proc/sys/net/ipv4/ip_dynaddr for verbose
>
> - - -CL
>
> ----------
> : From: Benjamin Diedrich <[EMAIL PROTECTED]>
> : To: [EMAIL PROTECTED]
> : Subject: Remote IP address problem
> : Date: Monday, May 31, 1999 3:21 PM
> :
> : I have a problem that I hope has a fairly straightforward solution. The
> : problem is when a program (telnet, ftp, Netscape, etc.) starts a link
> : with diald (version 0.98.2), the first time it uses a dummy remote IP
> : address given as "remote 194.109.2.10" in my config file, while all
> : successive connections use the remote IP address dynamically assigned by
> : my ISP. This is indicated in /var/log/diald.log. The first connections
> : show up as:
> :
> : Mon May 31 10:53:30 1999 PDT: Calling site 194.109.2.10.
> : Mon May 31 10:53:52 1999 PDT: Connected to site 194.109.2.10.
> : Mon May 31 10:54:45 1999 PDT: Disconnected. Call duration 53 seconds.
> : IP transmitted 2039 bytes and received 2188 bytes.
> :
> : All following connections show up like the following, where the "20" in
> : the "Calling site" IP address varies according to which remote computer
> : I get at my ISP:
> :
> : Mon May 31 10:56:21 1999 PDT: Calling site 199.2.132.20.
> : Mon May 31 10:56:43 1999 PDT: Connected to site 199.2.132.20.
> : Mon May 31 10:57:32 1999 PDT: Disconnected. Call duration 49 seconds.
> : IP transmitted 889 bytes and received 1045 bytes.
> :
> : The result is that no network connections work after diald dials up to
> : my ISP the first time. Using telnet for example, I get the message "Host
> : name lookup failure" when I try connecting to a hostname, and "network
> : unreachable" when I try an IP address. Restarting diald allows me to
> : connect correctly again on the first call. Sometimes though, diald dials
> : and allows telnet to connect to a hostname several times in a row. Any
> : ideas?
> :
> : --
> : _\\||//_____/|\ * * * Benjamin Diedrich
> : -- {} -----/ | \ |\* * [EMAIL PROTECTED]
> : *//||\\ * /__|__\_|_\ * * http://www.ugcs.caltech.edu/~diedrich/
> : //~||~\\~~\_________/~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> :
> : -
> : To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> : the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
