Bridging Two Tunnel Interfaces For ALTQ

[Julian Elischer]

On 6/29/11 11:28 AM, Michael MacLeod wrote:
> I use pf+ALTQ to achieve some pretty decent traffic shaping results at home.
> However, recently signed up to be part of an IPv6 trial with my ISP, and
> they've given me a second (dual-stacked) PPPoE login with which to test
> with. The problem is that the second login lacks my static IP or my routed
> /29. I can have both tunnels up simultaneously, but that becomes a pain to
> traffic shape since I can't have them both assigned to the same ALTQ.
>
> ... unless there is some way for me to turn the ng interfaces (I'm using
> mpd5) into ethernet interfaces that could be assigned to an if_bridge. I
> could easily disable IPv4 on the IPv6 tunnel, which would clean up any
> routing issues, assign both tunnels to the bridge, and put the ALTQ on the
> bridge. It just might have the effect I'm looking for. Bonus points if the
> solution can be extended to allow it to work with a gif tunnel as well, so
> that users of 6in4 tunnels could use it (my ISPs IPv6 beta won't let me do
> rDNS delegation, so I might want to try a tunnel from he.net instead).
>
> I spent some time this morning trying to make netgraph do this with the two
> ng interfaces, but didn't have any luck. Google didn't turn up anyone trying
> to do anything similar that I could find; closest I got was this:
> http://lists.freebsd.org/pipermail/freebsd-net/2004-November/005598.html
>
> This is all assuming that the best way to use ALTQ on multiple outbound
> connections is with a bridge. If there is another or more elegant solution,
> I'd love to hear it.

rather than trying to shoehorn ng into if_bridge, why not use the 
netgraph bridge itility,
or maybe one of the many other netgraph nodes that can split traffic.
fofr example the ng_bpf filter can filter traffic on an almost 
arbitrary manner that you program using
the bpf filter language.
> _______________________________________________
> freebsd-net at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
>