Re: Network configuration file
Johan Ehnberg wrote:
>
> Russell wrote:
> > I found that "dpkg-reconfigure etherconf" fills the "interface" file.
> > However, even tho there's entries for "iface lo inet loopback", this
> > loopback (127.0.0.0) doesn't appear when i type "route -nv" (after
> > restarting the pc). Is there an easy way to bypass the 'interface'
> > method for bootup? Are the old conventional files such as
> > /etc/init.d/network still used?
>
> Route -nv need not show a route for lo. That's the default and should
> work fine. Try ifconfig to see if lo is working.
ifconfig shows lo working, but "route -nv" doesn't show the 127.0.0.0
loopback route. From what i've seen in various books and on the net,
this is *not* ok as a default. I'm a nuts-n-bolts person. I like to
know why its different/changed.
> Bypassing is possible, but I really don't think that's a good idea, as
> you get some extra protection for free :) if you use the default script.
>
> The way debian loads the network during startup is:
>
> Init starts, and looks for /etc/rcS.d/(everything) and finds
> S40networking (symlink to /etc/init.d/networking).
> It then knows to run '/etc/init.d/networking restart'.
> 'networking' runs ifup.
> ifup reads /etc/networking/interfaces, and starts all interfaces
> specified as 'auto'.
I found something about local loopback being implicit in 2.2 kernels:
http://216.239.33.100/search?q=cache:LHy9EOUURewC:www.openresources.com/pub/magazine/linux-kernel-22.ps.gz+loopback+debian+implicit+kernel+interface&hl=en&ie=UTF-8
This is the text version of the file
http://www.openresources.com/pub/magazine/linux-kernel-22.ps.gz.
Current books on linux networking don't mention
things on implicit loopbacks. It's really annoying.
I'd like to get an answer: (A)the books are now wrong, or
(B)ifupdown isn't adding a loopback (127.0.0.0) route when
it should.
Reply to: