Red Hat Bugzilla – Bug 56382
Kernel 2.4 will not route to 127 block used by diald proxy interfaces
Last modified: 2007-04-18 12:38:19 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.2) Gecko/20010726
Description of problem:
This is actually a problem with the address' used in the PPP/SLIP dialout
module for Linuxconf. It uses 127.0.0.10 and 127.0.0.11 for the local and
remote address entries it creates in the conf files under /var/run. Since
the kernel will not route to these address' diald will not place any calls
when demand dialing is selected. The solution would be to change the
default address' used by Linuxconf to a block that the kernel will route
such as 10.0.0.0. This is not a problem in previous kernels and the change
will not adversely affect previous kernels.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Use PPP/SLIP dialout to setup PPP on demand connection
2.verify routes to SLIP proxy interface, "route", ifconfig
3.open lynx to any web page on the internet that should force diald up.
Actual Results: Diald will not diald. Even enabling debug does not produce
any errors because as far as diald is concerned, it is configured correctly.
Expected Results: If the kernel would route to 127 block, diald should
open the PPP link via dialout.
This should be a simple fix. Just change the address used by Linuxconf to
create the diald proxy sl0 interface and routes.
Closing because we don't ship linuxconf anymore
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.