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 <[email protected]> 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 <[email protected]> > 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 <[email protected]> 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 <[email protected]> > >> 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.. > >> > > > > > >
_______________________________________________ Voyage-linux mailing list [email protected] http://list.voyage.hk/mailman/listinfo/voyage-linux
