Change Details

This assumes we already have D50241 available but I still consider this the "hard way": jail -i -c name=demo host.hostname=demo.example.net vnet persist kldload ng_eiface echo -e "mkpeer eiface e ether\nname .:e ngeth0a" | ngctl -f - echo -e "mkpeer eiface e ether\nname .:e ngeth0b" | ngctl -j demo -f - ngctl mkpeer ngeth0a: wormhole ether evthorizon ngctl msg ngeth0a:ether open '"demo"' We still have one connection to make, but here we need to examine our current wormhole: ngctl show ngeth0a:ether Name: <unnamed> Type: wormhole ID: 00000018 Num hooks: 2 Local hook Peer name Peer type Peer ID Peer hook ---------- --------- --------- ------- --------- jid=1 <unnamed> wormhole 0000000d jid=0 evthorizon ngeth0a eiface 0000000c ether That is intentional trickery in that we name the `warp` hook after the JIDs on either side. This matters because you need to know how to get to "the far side". In this case jail "demo" is JID 1 and the wormhole has ID 0000000d (these are unique per vnet!). Ok assuming you adjust for your IDs you finally connect in the jail with: ngctl -j 1 connect ngeth0b: [0000000d]: ether evthorizon Just to be sure it actually works though lets do something trivial: ifn=$(ngctl msg ngeth0a: getifname | sed '1d' | cut -d\" -f2) ifconfig $ifn name ngeth0a ifn=$(ngctl -j 1 msg ngeth0b: getifname | sed '1d' | cut -d\" -f2) ifconfig -j 1 $ifn name ngeth0b ifconfig ngeth0a inet 192.168.128.1/30 up ifconfig -j 1 ngeth0b inet 192.168.128.2/30 up ping 192.168.128.2 jexec demo ping 192.168.128.1 Lets clean all of that up now: jail -r demo ngctl shutdown ngeth0a: Ok that is not showing off everything a wormhole can do but that is because I have a separate utility that makes using it easier and I will add tests that use it once that review is up. So there will be more! In particular we will be making this: {F116551352} But until then please feel free to start looking at the code, particularly interested in knowing if there is a better way than pulling in `ng_rmnode`. Also `HK_COLLAPSE` should probably be with other flags. That's the non-standard bit I definitely want more knowledgeable folks to look at but I appreciate everything being looked at as even if this never gets merged I use it!

This assumes we already have D50241 available but I still consider this the "hard way": jail -i -c name=demo host.hostname=demo.example.net vnet persist kldload ng_eiface echo -e "mkpeer eiface e ether\nname .:e ngeth0a" | ngctl -f - echo -e "mkpeer eiface e ether\nname .:e ngeth0b" | ngctl -j demo -f - ngctl mkpeer ngeth0a: wormhole ether evthorizon ngctl msg ngeth0a:ether open '"demo"' We still have one connection to make, but here we need to examine our current wormhole: ngctl show ngeth0a:ether Name: <unnamed> Type: wormhole ID: 00000018 Num hooks: 2 Local hook Peer name Peer type Peer ID Peer hook ---------- --------- --------- ------- --------- jid=1 <unnamed> wormhole 0000000d jid=0 evthorizon ngeth0a eiface 0000000c ether That is intentional trickery in that we name the `warp` hook after the JIDs on either side. This matters because you need to know how to get to "the far side". In this case jail "demo" is JID 1 and the wormhole has ID 0000000d (these are unique per vnet!). Ok assuming you adjust for your IDs you finally connect in the jail with: ngctl -j 1 connect ngeth0b: [0000000d]: ether evthorizon Just to be sure it actually works though lets do something trivial: ifn=$(ngctl msg ngeth0a: getifname | sed '1d' | cut -d\" -f2) ifconfig $ifn name ngeth0a ifn=$(ngctl -j 1 msg ngeth0b: getifname | sed '1d' | cut -d\" -f2) ifconfig -j 1 $ifn name ngeth0b ifconfig ngeth0a inet 192.168.128.1/30 up ifconfig -j 1 ngeth0b inet 192.168.128.2/30 up ping 192.168.128.2 jexec demo ping 192.168.128.1 Lets clean all of that up now: jail -r demo ngctl shutdown ngeth0a: Ok that is not showing off everything a wormhole can do but that is because I have a separate utility that makes using it easier and I will add tests that use it once that review is up. So there will be more! In particular we will be making this (in D50245): {F116551352} But until then please feel free to start looking at the code, particularly interested in knowing if there is a better way than pulling in `ng_rmnode`. Also `HK_COLLAPSE` should probably be with other flags. That's the non-standard bit I definitely want more knowledgeable folks to look at but I appreciate everything being looked at as even if this never gets merged I use it!

This assumes we already have D50241 available but I still consider this the "hard way": jail -i -c name=demo host.hostname=demo.example.net vnet persist kldload ng_eiface echo -e "mkpeer eiface e ether\nname .:e ngeth0a" | ngctl -f - echo -e "mkpeer eiface e ether\nname .:e ngeth0b" | ngctl -j demo -f - ngctl mkpeer ngeth0a: wormhole ether evthorizon ngctl msg ngeth0a:ether open '"demo"' We still have one connection to make, but here we need to examine our current wormhole: ngctl show ngeth0a:ether Name: <unnamed> Type: wormhole ID: 00000018 Num hooks: 2 Local hook Peer name Peer type Peer ID Peer hook ---------- --------- --------- ------- --------- jid=1 <unnamed> wormhole 0000000d jid=0 evthorizon ngeth0a eiface 0000000c ether That is intentional trickery in that we name the `warp` hook after the JIDs on either side. This matters because you need to know how to get to "the far side". In this case jail "demo" is JID 1 and the wormhole has ID 0000000d (these are unique per vnet!). Ok assuming you adjust for your IDs you finally connect in the jail with: ngctl -j 1 connect ngeth0b: [0000000d]: ether evthorizon Just to be sure it actually works though lets do something trivial: ifn=$(ngctl msg ngeth0a: getifname | sed '1d' | cut -d\" -f2) ifconfig $ifn name ngeth0a ifn=$(ngctl -j 1 msg ngeth0b: getifname | sed '1d' | cut -d\" -f2) ifconfig -j 1 $ifn name ngeth0b ifconfig ngeth0a inet 192.168.128.1/30 up ifconfig -j 1 ngeth0b inet 192.168.128.2/30 up ping 192.168.128.2 jexec demo ping 192.168.128.1 Lets clean all of that up now: jail -r demo ngctl shutdown ngeth0a: Ok that is not showing off everything a wormhole can do but that is because I have a separate utility that makes using it easier and I will add tests that use it once that review is up. So there will be more! In particular we will be making this (in D50245): {F116551352} But until then please feel free to start looking at the code, particularly interested in knowing if there is a better way than pulling in `ng_rmnode`. Also `HK_COLLAPSE` should probably be with other flags. That's the non-standard bit I definitely want more knowledgeable folks to look at but I appreciate everything being looked at as even if this never gets merged I use it!