[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Getting runparts if-up.d, etc to execute

On Monday 30 Kislev 5772 04:18:08 debian-user-digest-request@lists.debian.org 
> > Somehow, the scripts in the if-up.d, if-down.d directories are net being 
> > executed.
> Very unexpected.
> > I have a farely standard interfaces for a router. What am I missing?
> >
> > 
> >
> > # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
> >
> > 
> >
> > # The loopback interface
> > # automatically added when upgrading
> > iface lo inet loopback
> In addition to the above there should be a line for the loopback
> driver like this one:
>   auto lo
> They usually appear like this:
>   auto lo
>   iface lo inet loopback
> > iface eth2 inet static
> >       address
> >       netmask
> >       network
> >       broadcast
> >       gateway
> You have a very common but undesired inclusion of both netmask and
> broadcast and network.  This is due to the documentation including all
> as an example and then many people followed the example.  This has
> gotten cleaned up most places but the cleanup is continuing.  The
> program can calculate the broadcast and network from the netmask.  The
> netmask is the most desirable source for all of the rest and it would
> be very unusual to need to include all three. It is much more desired
> to list only netmask in the file and let the program calculate the
> rest because it eliminates a source of human data entry error.
> Then at the minimum you want 'allow-hotplug eth2' on the interface
> too.  Additionally 'auto eth2' is also useful for old timers such as
> myself that want to have the network cycle when running 'service
> networking restart'.
>   auto eth2
>   allow-hotplug eth2
>   iface eth2 inet static
>         address
>         netmask
>         gateway
> I think that the missing 'allow-hotplug eth2' line might be your
> problem with scripts.  Because it was probably more than simply
> scripts that was not being configured.
> The above is documented here:
>   http://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_basi
> c_syntax_of_etc_network_interfaces
> And here:
>   http://wiki.debian.org/NetworkConfiguration

OK! This and a reboot (with a series of iptables temporarily unavailable 
messages) got it working and I saw the text that expected to see. The network 
was working correctly on startup. BTW, the netcardconfig utility asks for and 
places all three lines, not just the netmask, and also removes/omits the 
other, auto and allow lines. So replacing this very very old utility is part 
of the cleanup.

The scripts are run fine. I still cannot get my imap server from outside 
(formerly corrected by (re-)running the rc.firewall script (from guarddog) but 
that may be another problem. I do have port 143 forwarded in the router.

Reply to: