22 Feb
2012
22 Feb
'12
3:14 a.m.
On Wed, 2012-02-22 at 09:55 +0200, Heikki Hannikainen wrote:
On Wed, 22 Feb 2012, Marius Petrescu wrote:
Do keep in mind that /etc/network/interfaces is debian-centric and only
works on debian-derived systems. I am a debian guy, and this is what I
use, but I know there are Other Ways of doing things. IMHO, rip44d
should not assume /etc/network/interfaces is the One True Way until
redhat, suse and *bsd also adopt it.
bash + iproute2 is a pretty good bet on most modern linux-based distros
sh + ifconfig is pretty common across most linux, freebsd, OS X, solaris
and openbsd setups.
cmd + netsh might work on windows
I post my working setup () with step by step
instructions... Could be wrong
(but it works)
That's pretty good, especially how it uses the standard
/etc/network/interfaces file for configuration. Marius, do you mind if I
convert that to Wiki format on http://wiki.ampr-gateways.org/ ? I'd make a
separate page for the /etc/network/interfaces config and tune the Rip44d
install guide a bit based on that.
Brian, the rip44d guide currently does contain all of the necessary bits
to get amprnet routing up, the only downside is that it does everything in
/etc/rc.local instead of a proper init script or /etc/network/interfaces
usage. /etc/network/interfaces configuration allows ifup/ifdown usage for
bringing the interface up or down.
http://wiki.ampr-gateways.org/index.php?title=Rip44d
- Hessu