[Voyage-linux] Static IP on Alix

[Gustin Johnson]

No need to recompile, everything should be there already.  I recently
built a 3 WAN load balancer with Voyage using the included kernel with
an ALIX SBC.  The hardest part was coming up with the load balancing
script.

Instead of two IP addresses on the same network, just bridge the
interfaces together and assign a single IP to the logical bridge
interface that gets created as a result.  As an example, eth0 and
wlan0 are physical interfaces, but neither gets an IP.  Instead you
assign the IP to the bridge interface which is arbitrarily named by
you, usually use something like br_lan01 or br_wan01 to make it easier
to keep track of.  There are examples of this sort of thing right in
the /etc/network/interfaces file that ships with Voyage.

Just as an aside, the examples in that file have served me very well
over the years.

On Sun, Sep 4, 2011 at 2:58 PM, John Schultz <jschultz0614 at gmail.com> wrote:
> I know that :-p
>
> Im more afraid of recompiling the kernel :-p (and that doesn't even phase
> me)
>
> On Sun, Sep 4, 2011 at 14:56, Gustin Johnson <gustin at meganerd.ca> wrote:
>>
>> Nothing to be a afraid of, just think of it as networking 201.  Once
>> you get the basics of a single interface under control, the next step
>> is to work with multipath situations.  The good news is that this is
>> well supported by the Linux kernel and the userspace utilities.
>>
>> You may want to look at http://lartc.org for some pretty good
>> documentation of more advanced networking concepts and techniques.
>>
>> On Sun, Sep 4, 2011 at 1:49 PM, John Schultz <jschultz0614 at gmail.com>
>> wrote:
>> > That is ultimately what I was afraid of.
>> >
>> > I tried several months ago (before I started working on the PXE and UDEV
>> > issues)  with no luck.
>> >
>> > It eventually destabilized the node and then the networking  died.
>> >
>> > On Sun, Sep 4, 2011 at 12:56, Gustin Johnson <gustin at meganerd.ca> wrote:
>> >>
>> >> In that case, you need to be careful about your routing table,
>> >> especially if dhcp is involved.  Either one of you may wish to change
>> >> your DHCP client to something else, like the ISC one and then
>> >> configure which aspects get configured.
>> >>
>> >>
>> >> On Sun, Sep 4, 2011 at 12:24 PM, John Schultz <jschultz0614 at gmail.com>
>> >> wrote:
>> >> > Actually, not at all...
>> >> >
>> >> > Roberto's and ultimately my situation are completely different.
>> >> > Roberto's
>> >> > situation sounds like a segmentation issue. Mine will be similar,
>> >> > however I
>> >> > am using one wireless network for a backhual, the second wireless
>> >> > network or
>> >> > client connectitivity and the hardwire ethernet as a uplink to the
>> >> > internet
>> >> > or another network..
>> >> >
>> >
>> >
>
>