| 00:38.25 | *** join/#utah josephscott (~josephsco@74.114.153.251) |
| 01:00.39 | *** join/#utah goozbach (~goozbach@c-24-10-216-228.hsd1.ut.comcast.net) |
| 01:00.39 | *** join/#utah goozbach (~goozbach@fedora/goozbach) |
| 01:00.39 | *** mode/#utah [+v goozbach] by ChanServ |
| 02:51.59 | *** join/#utah goozbach (~goozbach@c-24-10-216-228.hsd1.ut.comcast.net) |
| 02:51.59 | *** join/#utah goozbach (~goozbach@fedora/goozbach) |
| 02:51.59 | *** mode/#utah [+v goozbach] by ChanServ |
| 03:03.25 | *** join/#utah tiwula (~lane@174-23-79-168.slkc.qwest.net) |
| 11:25.21 | *** join/#utah emcnabb (~emcnabb@hs-nc-1fff767f54-29977-1.tingfiber.com) |
| 13:23.04 | *** join/#utah tiwula (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 14:52.59 | *** join/#utah goozbach (~goozbach@c-24-10-216-228.hsd1.ut.comcast.net) |
| 14:52.59 | *** join/#utah goozbach (~goozbach@fedora/goozbach) |
| 14:52.59 | *** mode/#utah [+v goozbach] by ChanServ |
| 15:18.04 | *** join/#utah josephscott (~josephsco@proxy.automattic.com) |
| 15:25.34 | *** join/#utah braxtron (~braxtron@216.160.248.178) |
| 16:11.13 | *** join/#utah legreathambino (~braxtron@216.160.248.178) |
| 16:14.48 | *** join/#utah goozbach (~goozbach@fedora/goozbach) |
| 16:14.48 | *** mode/#utah [+v goozbach] by ChanServ |
| 16:23.56 | goozbach | <PROTECTED> |
| 16:54.01 | goozbach | https://gitlab.com/goozbach-presentation/vault/blob/master/blurb.adoc |
| 16:54.07 | goozbach | blurb for next week's meeting |
| 16:55.56 | *** join/#utah braxtron (~braxtron@216.160.248.178) |
| 19:34.47 | frostyfrog | issa blurb! |
| 19:35.30 | frostyfrog | I wonder if there are and birbs. Afterall, a plurb's gotta soar to a much higher potential |
| 20:14.09 | *** join/#utah josephscott (~josephsco@192.0.80.201) |
| 20:14.14 | *** join/#utah youtah_ (~youtah@67.139.187.132) |
| 20:18.38 | joshh | what meeting is that for |
| 20:25.45 | *** join/#utah youtah (~youtah@67.139.187.132) |
| 20:39.10 | *** join/#utah youtah (~youtah@67.139.187.132) |
| 21:27.02 | goozbach | plug meeting next Tuesday |
| 21:27.10 | goozbach | 7:30 at UVU business resource center |
| 21:27.19 | goozbach | presenting on HashiCorp Vault |
| 21:27.23 | goozbach | how and when to use it |
| 21:27.55 | joshh | ah ok, a lug |
| 21:29.33 | goozbach | come watch |
| 21:30.03 | jlp_znc | plug is still a thing? |
| 21:30.41 | joshh | i went to a couple plug and sllug meetings a super long time ago |
| 21:30.48 | joshh | like 13 years ago or so |
| 21:30.56 | joshh | time flies so much |
| 21:34.47 | goozbach | yup |
| 21:34.52 | goozbach | still going strong'ish |
| 21:35.00 | goozbach | jlp_znc: you should come too! |
| 21:35.11 | goozbach | no time like the present to come back! |
| 21:35.18 | joshh | vault is cool though, i like it |
| 22:00.10 | jlp_znc | in the evening? and in orem? yeah, nah. |
| 22:55.06 | goozbach | jlp_znc: would you attend in SL Valley around lunch? |
| 22:55.19 | goozbach | Iv'e been wanting to start a lunch meeting |
| 23:07.28 | jlp_znc | well, since my company moved to Lehi, that would be problematic now. when I was in South Jordan I'd have said sure. |
| 23:20.32 | jfindlay | plug and sllug user group meetings were the compost from which my career sprang |
| 23:21.30 | jlp_znc | I think I went to sllug once |
| 23:21.31 | joshh | maybe your future boss will be a young kid at the meeting tonight |
| 23:21.58 | jfindlay | is it possible to translate the traffic to/from a pure IPv6 host and have it go out onto a v4 network? |
| 23:22.14 | jfindlay | or can you only tunnel v6 across v4? |
| 23:22.54 | jlp_znc | surely you can still NAT an IPv6 host |
| 23:23.05 | jfindlay | what does that mean? |
| 23:23.13 | joshh | why would a 6 only host be on a 4 only network? |
| 23:23.28 | jfindlay | why not? |
| 23:23.28 | goozbach | you calling these meetings crap? :P |
| 23:23.41 | jfindlay | goozbach: good grap |
| 23:23.43 | jfindlay | crap |
| 23:23.56 | jlp_znc | say you had an internal IPv6 infrastructure, but your up link was IPv4 only. you would run network address translation (NAT) on the gateway between the two networks. |
| 23:24.28 | jfindlay | jlp_znc: so a v6 to v4 NAT translates v6 traffic to/from v4 traffic? |
| 23:25.06 | jlp_znc | sure... it doesn't care. it's operating at layer 3/4 anyway. |
| 23:25.10 | jfindlay | joshh: this is for setting up a test scenario, but our team does not control the other endpoint |
| 23:25.52 | jlp_znc | to the target on the outside, all it would see would be IPv4 packets on a particular port. the NAT gateway would be maintaining a table of connections <-> the IPv6 host/port |
| 23:27.56 | jlp_znc | https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipaddr_nat/configuration/15-mt/nat-15-mt-book/ip6-natpt.html |
| 23:34.16 | joshh | it is possible to tunnel v4 cross v6, but if your host is really 6 only on a 4 only network, it won't be able to talk to any other tunnel endpoint, or anything else |
| 23:34.55 | joshh | it sounds like you want a dual stack host from your description so far |
| 23:35.31 | joshh | or maybe a 6 only VM that talks to a dual stack host? |
| 23:35.48 | jfindlay | the remote host is v4 only |
| 23:36.42 | joshh | what is the test for |
| 23:44.55 | jfindlay | testing the softwares |
| 23:52.57 | joshh | something like a unit test that tries to do a real v6 connection to a service on another host that doesn't have v6? you might be able to add a little local proxy that can handle the switch |
| 23:55.11 | joshh | like haproxy with the v6 frontend and v4 backend |
| 23:55.58 | joshh | http://www.koopman.me/2011/02/haproxy-for-ipv6-translation-to-ipv4-only-website/ |
| 23:56.25 | jfindlay | cool |
| 23:56.44 | jfindlay | how likely is it that network hardware is going to be dual stack enabled? |
| 23:57.04 | joshh | not sure but it won't matter in that case |
| 23:57.12 | joshh | you would connect to localhost on the haproxy port |
| 23:57.17 | joshh | instead of the remote end directly |
| 23:57.29 | joshh | but it does require your pure v6 host to have v4 as well |
| 23:57.35 | jfindlay | right, but if you do something 6to4, would it 'just work'? |
| 23:58.33 | joshh | 6to4 just works from v4 only networks, as long as the network team doesn't ban IP "protocol 41" on the gear |
| 23:59.18 | joshh | but they don't need to explicitly support routing it or anything |