Hi John, did you ever try out my version?

Julian

On 7/1/18 4:06 am, Julian Elischer wrote:
On 7/1/18 4:02 am, John Lyon wrote:
Thanks for the clarification and all the help.

After Marko clarified that that edges/hooks are bidirectional, I was able to get it working WAN to LAN and LAN to WAN by using a pair of one2many and ETF nodes.

The commands were (from memory):

#Create Unfiltered WAN Path
ngctl mkpeer igb0: one2many lower one
ngctl name igb0:lower wanmux
ngctl mkpeer wanmux: etf many0 downstream
ngctl name wanmux:many0 wanfilter
ngctl connect wanfilter: igb0: nomatch upper

#Create Unfilter LAN Path
ngctl mkpeer igb1: one2many lower one
ngctl name igb1:lower lanmux
ngctl mkpeer lanmux: etf many0 downstream
ngctl name lanmux:many0 lanfilter
ngctl connect lanfilter: igb1 nomatch upper

#Cross Connect Two Paths
ngctl connect wanfilter wanmux waneapout many1
ngctl connect lanfilter lanmux laneapout many1

#Filter Cross Connections
ngctl msg wanfilter: 'setfilter { matchhook="waneapout" ethertype=0x888e }' ngctl msg lanfilter: 'setfilter { matchhook="laneapout" ethertype=0x888e }'

The graph looks like this:

igb0] <----> [mux0] <---> [etf0] <----> [igb0
                               \       /
                                  X
                               /      \
igb1] <----> [mux1] <---> [etf1] <----> [igb1


It was conceptually easier for me to wrap my head around and it appears to work (somewhat).  But if I can get it to work, I like Julian's approach better as it is simpler and uses fewer nodes.

etf includes a mux/demux..  the link is bidirectional.



Thanks again for all the help!

--------------------------------
John L. Lyon
PGP Key Available At:
https://www.dropbox.com/s/skmedtscs0tgex7/02150BFE.asc

On Sat, Jan 6, 2018 at 2:39 PM, Julian Elischer <jul...@freebsd.org <mailto:jul...@freebsd.org>> wrote:


_______________________________________________
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Reply via email to