Bug 20798 - pppd takes wrong IP
Summary: pppd takes wrong IP
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ppp
Version: 6.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Thomas Woerner
QA Contact: Aaron Brown
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-11-13 21:08 UTC by Need Real Name
Modified: 2007-04-18 16:29 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2004-08-13 09:25:48 UTC


Attachments (Terms of Use)

Description Need Real Name 2000-11-13 21:08:49 UTC
I've got the following problem running pppd 2.3.10-3 on RedHat 6.1,
Kernel 2.2.12-20 or 2.2.16-21

(Reviewing bugreports I found one more mentioning of the same problem
by peter@luno.org in bug ID6295, but not answered)

So the problem:

There is a host connected to a LAN/WAN via Ethernet having a modem
(ppp server). It's IP is N.
The remote host connecting via modem line has no other connections
and pretend to use IP M. (M is a legal IP on the same subnet as N
known by DNS and not used by any machine) 

So on server side /etc/ppp/options contains addresses N:M.
On the client side - just the reverse M:N.
(no other options files exist, command line options aren't used)
pppd is suid root, so it can and it does read /etc/ppp/options
(I'm sure it does because other options like debug,proxyarp,
noauth are working)

When I start pppd on server as root - everything works fine.

But if I start pppd on server as ordinary user ppp0 interface
on server is getting IP address N+1 (!!!).
And that cause a trouble on the LAN - it's an IP of other running
machine.

What is the reason? Why it ignores an IP given in options file and use
some other of it's own choice?
Even if setting IPs is a priveleged option (which seems not to be the
case according to man page) it's coming from a priveleged source - it
should work...

Comment 1 Thomas Woerner 2004-08-13 09:25:48 UTC
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.



Note You need to log in before you can comment on or make changes to this bug.