Red Hat Bugzilla – Bug 58577
Dialup local IP address = LAN hostname address
Last modified: 2007-04-18 12:39:06 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.9-13 i586)
Description of problem:
When using the normal (menu "dialup configuration") setups for dialing an ISP,
pppd often negotiates the hostname's LAN address (192.168.0.x) for the local IP
address. This results in several dialup attempts required before successful
Note: Adding "noipdefault" to /etc/ppp/options seems to have fixed this.
Perhaps this should be done automatically when using dynamic address assignment?
Also note: Happens only after setting up a LAN. Didn't happen before this,
when the host address was only 127.0.0.1.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure system for use in a LAN, using an ethernet connection.
2. Set up a dialup network connection.
3. Attempt to make the dialup connection several times.
Actual Results: pppd often successfully negotiates my hostname's LAN address as
the local IP address for the ppp connection, resulting in no communication.
Expected Results: pppd should have allowed the ISP to dynamically assign the
local IP address.
I am having this problem too. After connecting, /sbin/ifconfig shows my ppp
connection's local ip address as 192.168.0.2, which is my eth0's address on my
Perhaps rp3 should have an option to get the connection's local IP from the
remote host? I've constructed two patches that address this problem (one for
rp3, one for initscripts). Since they seem to work well I'll attach them to this
Created attachment 43635 [details]
Provide option to retrieve local ip from remote host
Created attachment 43636 [details]
Use "noipdefault" pppd option when retrieving local IP from remote host
Please verify this with a newer version of Red Hat Enterprise Linux or
Fedora Core and reopen it against the new version if it still occurs.
Closing as "not a bug" for now.