Re: Multi Active Devices
On Sat, Dec 20, 2008 at 16:32, Etienne Zind wrote: > I'm using the NetworkManager shipped in the last Ubuntu distro (0.7). I've > been > able to connect few devices in the same time as expected (eth0, ppp0, wan0). > As > expected too, although all three ISPs are connected only one (eth0) is > actually > used (default route). The way NM updates the route table prevents any packet > to > be routed by another device than the default one even if specified on > software: > > $ wget --bind-address=$IP_WAN0 http://foo.bar/index.html # fails > $ wget --bind-address=$IP_PPP0 http://foo.bar/index.html # fails > $ wget --bind-address=$IP_ETH0 http://foo.bar/index.html # OK > > So I had a look at the "Linux Advanced Routing & Traffic Control HOWTO" by > Bert Hubert [1] and implemeted the setup [2] described in the "Routing for > multiple uplinks/providers" and it did work perfectly (even with a trivial > load > balancing over the 3 ISPs with the multipath default route). I seriously doubt people want load balancing in general (for example, in case of active ethernet and modem devices). There are many possibilities for setting up routing in case of multiple active devices (like split access, load balancing, failsafe/backup, ...) and we have no way of configuring that with NM right now. We have data structures for connections (one per active device), but we don't have defined relations between them. > The basic idea is to use many routing tables together, and some rules to > define > which table to use. I implemented it in a perl script that I execute manualy > everytime something change in the NM environement (how to do that > automaticaly ?) Whenever a device is activated/deactivated, the dispatcher scripts are called from /etc/NetworkManager/dispatcher.d/ directory, so you should put your script there and test how your script is called. The first argument passed to the scripts is the device interface name, the second is "up" or "down". > I would love to get my fingers dirty in your elegantr GObj C code, although I > might need some "emlightment" from you guys to be sure it worth it. > Please have a look at my shell script (working). Any comment will be > welcome. I couldn't see it, it kept timing out for me, but it would be a good start to convert it to C and use libnl so that it would be easy to add to NM when it's ready. Tambet > > [1] http://lartc.org/howto/index.html > [2] http://parad0x.org/~barbu/dev/mad/mad-setup.pl > > -- > Regards, > Etienne Zind > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Fwd: Multi Active Devices
Hi All, I'm using the NetworkManager shipped in the last Ubuntu distro (0.7). I've been able to connect few devices in the same time as expected (eth0, ppp0, wan0). As expected too, although all three ISPs are connected only one (eth0) is actually used (default route). The way NM updates the route table prevents any packet to be routed by another device than the default one even if specified on software: $ wget --bind-address=$IP_WAN0 http://foo.bar/index.html # fails $ wget --bind-address=$IP_PPP0 http://foo.bar/index.html # fails $ wget --bind-address=$IP_ETH0 http://foo.bar/index.html # OK So I had a look at the "Linux Advanced Routing & Traffic Control HOWTO" by Bert Hubert [1] and implemeted the setup [2] described in the "Routing for multiple uplinks/providers" and it did work perfectly (even with a trivial load balancing over the 3 ISPs with the multipath default route). The basic idea is to use many routing tables together, and some rules to define which table to use. I implemented it in a perl script that I execute manualy everytime something change in the NM environement (how to do that automaticaly ?) I would love to get my fingers dirty in your elegantr GObj C code, although I might need some "emlightment" from you guys to be sure it worth it. Please have a look at my shell script (working). Any comment will be welcome. [1] http://lartc.org/howto/index.html [2] http://parad0x.org/~barbu/dev/mad/mad-setup.pl -- Regards, Etienne Zind ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Multi Active Devices
Hi All, I'm using the NetworkManager shipped in the last Ubuntu distro (0.7). I've been able to connect few devices in the same time as expected (eth0, ppp0, wan0). As expected too, although all three ISPs are connected only one (eth0) is actually used (default route). The way NM updates the route table prevents any packet to be routed by another device than the default one even if specified on software: $ wget --bind-address=$IP_WAN0 http://foo.bar/index.html # fails $ wget --bind-address=$IP_PPP0 http://foo.bar/index.html # fails $ wget --bind-address=$IP_ETH0 http://foo.bar/index.html # OK So I had a look at the "Linux Advanced Routing & Traffic Control HOWTO" by Bert Hubert [1] and implemeted the setup [2] described in the "Routing for multiple uplinks/providers" and it did work perfectly (even with a trivial load balancing over the 3 ISPs with the multipath default route). The basic idea is to use many routing tables together, and some rules to define which table to use. I implemented it in a perl script that I execute manualy everytime something change in the NM environement (how to do that automaticaly ?) I would love to get my fingers dirty in your elegantr GObj C code, although I might need some "emlightment" from you guys to be sure it worth it. Please have a look at my shell script (working). Any comment will be welcome. [1] http://lartc.org/howto/index.html [2] http://parad0x.org/~barbu/dev/mad/mad-setup.pl -- Regards, Etienne Zind mad-setup.pl Description: Perl program ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Multi-active devices
On Mon, Mar 10, 2008 at 10:08 AM, Dan Williams <[EMAIL PROTECTED]> wrote: > active device support to NM SVN trunk this weekend; each device is now > independent and can be active/inactive irrespective of any other device. ya! :-) ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Multi-active devices
On Sat, 2008-03-08 at 18:44 -0600, Jerry Vonau wrote: > Hi All: > > What support is planned for multiple gateways? I build firewalls > that don't run X (so no runlevel 5 here), with the recent CLI support, I > might just try to use NM in the future. I setup multi-gateway (2+ ISPs) > support using my own scripts or Shorewall's built-in support. I have had > a small hand in the development of Shorewall's multi-isp support, and > the supporting of the same on Shorewall's mailing list. In past have > submitted patches to initscripts for this support (BZ171763), I have > working experence with iproute and what is needed to make this work in > real life, is there any interest in having NM support this? What sort of configuration setup do you need? I committed the multiple active device support to NM SVN trunk this weekend; each device is now independent and can be active/inactive irrespective of any other device. Do you need complicated routing setup or other interface-specific parameters? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Multi-active devices
Hi All: What support is planned for multiple gateways? I build firewalls that don't run X (so no runlevel 5 here), with the recent CLI support, I might just try to use NM in the future. I setup multi-gateway (2+ ISPs) support using my own scripts or Shorewall's built-in support. I have had a small hand in the development of Shorewall's multi-isp support, and the supporting of the same on Shorewall's mailing list. In past have submitted patches to initscripts for this support (BZ171763), I have working experence with iproute and what is needed to make this work in real life, is there any interest in having NM support this? Jerry ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
