Thread: where ifconfig setup/init files?

Somehwere in init.d there is a network setup shell-script. Modify that so that it sets the correct MTU. [It may call some other script which may be what you want to modify - but the principle is that the network start is done via a shell-script somewhere init.d].

--
Mats

And that init.d script will be configurable using some configuration file.

For example:
- Gentoo's /etc/init.d/net.* scripts are configured by /etc/conf.d/net and /etc/conf.d/wireless.
- ArchLinux's /etc/rc.d/network script is configured by /etc/rc.conf.

Files in /proc are not real files. Those are interfaces to the OS to supply information out of the OS without adding new API functions - instead, the OS pretends to have files in the /proc tree which provides text information to the applications that want it.

--
Mats

Good reading: http://www.debian.org/doc/manuals/re...ateway.en.html

Maybe you want this.

10.8.1 Triggering network configuration at boot time
On boot the /etc/rcS.d/S40networking init script runs the command ifup -a. This brings up all physical interfaces listed in auto stanzas in /etc/network/interfaces.

These days it is often better to handle network configuration using dynamic methods. Once mechanisms for supporting dynamically changing hardware are in place it becomes simplest to treat static hardware as if it were dynamic too. Booting can then be treated as just another hotplug event. (See Triggering network configuration – hotplug, Section 10.8.2.)

However, in almost all cases one wants at least the loopback interface lo to be brought up on boot. Therefore, make sure that /etc/network/interfaces includes the following stanzas.

auto lo

iface lo inet loopback
You can list additional physical interface names in auto stanzas if you want them to be brought up on boot too. Never list PCMCIA interfaces in auto stanzas. The PCMCIA cardmgr is started later in the boot sequence than when /etc/rcS.d/S40networking runs.