On 14 November 2014 17:26, Rafael Zalamena <rzalam...@gmail.com> wrote: > On Sun, Sep 14, 2014 at 11:48:11PM -0300, Rafael Zalamena wrote: >> The following mails will contain patchs that implement the VPLS datapath >> in OpenBSD. Applying all patchs should allow people to configure a >> network using VPLS manually. >> >> --- snipped diffs descriptions --- >> >> How to use: >> * Create a MPLS network. >> Example: http://2011.eurobsdcon.org/papers/jeker/MPLS.pdf >> * Create a pseudowire in both ends of your network (PEs) >> # ifconfig wire<number> encap ethernet wirelabel <local label> \ >> <remote label> neighbor <other PE address> <controlword> up >> >> # ifconfig wire0 encap ethernet wirelabel 500 500 neighbor 1.2.3.4 up >> or >> # ifconfig wire0 encap ethernet wirelabel 500 500 neighbor 1.2.3.4 \ >> controlword up >> * Create a bridge between the interface facing your customer (CE) and >> your wireX, also in both PEs you are configuring the VPN. >> >> --- more comments snipped --- >> >> TODO list: >> * interface configuration code - SIOCSETWIRECFG / SIOCGETWIRECFG (DONE) >> * add / remove wire label (DONE) >> * add / remove wire control label (DONE) >> * ethernet-vlan support (WIP) > > Ethernet-tagged support almost complete, it's not working in the case when > you have packets coming with 2 or more tags. I'm having problems to test > this since 5.6 and -current doesn't do QinQ properly. (I'll be sending > proposal diffs to fix this soon) > >> * ifconfig(8) integration >> ** show wire configuration (DONE) >> ** configure wire (DONE) >> * man page: >> ** wire(4) (TODO) >> ** ifconfig(8) (TODO) > > wire(4) is depending on some other diffs now that are unrelated to this, > please see: > > (update mpe to use rt_ifa, wire will use that too) > http://marc.info/?l=openbsd-tech&m=141280528700615&w=2 > > (fix bridge + vlan, bridge expects the complete packet) > http://marc.info/?l=openbsd-tech&m=141575896420071&w=2 >
is it possible to call it something other than just wire(4)? vpls maybe?
