[Jool-list] Jool and VirtualBox

Mon Jul 30 18:45:33 CDT 2018

Hi Alberto,

The point here is that the "link" between the "students" and the NAT64 box is wireless (as said we can't deploy a wired network for all the students) and this link "among them" is only IPv6.

But we also use that interface to connect the "host2" of Virtualbox with the "CLAT VM1", and of course, that "connection" is using dual-stack (but no RA, no DHCP, to avoid interactions in the shared media).

The alternative to that is option c) using two VMs, but as said, then it works only with Ethernet, not with WiFi ... strange.

By the way one clarification to option c)

    Option c)

    Host2 - Mac OSX with VirtualBox

    VM1 - Ubuntu with Jool as CLAT

Eth0 of VM1 is either Ethernet or WiFi connected to the host1 eth1 for the NAT64

Eth1 of VM1 is intnet

    VM2 - Ubuntu as "client" of the CLAT

Eth0 of VM2 is intnet

    Only one physical interface is used to connect to eth1 in host1

    This interface can be either Ethernet or WiFi

    The connection between VM1 and VM2 is using "intnet" (internal network)

    -> Nothing works if Eth0/VM1 interface is WiFi

    -> Everything works if Eth0/VM1 interface is Ethernet

Regards,

Jordi

-----Mensaje original-----

De: Alberto Leiva Popper <aleiva at nic.mx>

Fecha: lunes, 30 de julio de 2018, 11:41

Para: JORDI PALET MARTINEZ <jordi.palet at consulintel.es>, "jool-list at nic.mx" <jool-list at nic.mx>

Asunto: RE: Jool and VirtualBox

    Ok, this looks like a very likely bug. Sorry for the inconveniences.

    To see if we can reproduce the problem, we're trying to get our hands on a Mac Mini. I have one question, though:

    > IPv4 doesn't work if the interface is WiFi and this is the interface that I really need ...

    Something here seems to be missing. You said that host 1's eth1 interface was IPv6 only. Why is it expected to exchange IPv4 traffic?

    And one more thing:

    The latest commit at the issue267 branch

    (https://github.com/NICMx/Jool/commit/e431a8d271d2427ab449bf839c37ebfc439259c9)

    adds some kernel hack handling that Jool used to lack until now.

    There's a small (but not insignificant) chance that it could solve your problem. Could you test this code in your environment?

Unfortunately, I will not be able to test this for the next 2 weeks or so, because I'm in Lima doing a consultancy work and haven't got here a proper network to test everything ... So hopefully you can setup an equivalent environment.

May be if you can't get a Mac OS X, an instead test using a Linux or Windows host, we can guess if it is only a VirtualBox problem or some Jool issue with is not "happening" with VMware for some reason, or whatever ... or even something broken in the OS X (I doubt it, but you never know!).

    -----Original Message-----

    From: jool-list-bounces at nic.mx [mailto:jool-list-bounces at nic.mx] On Behalf Of JORDI PALET MARTINEZ

    Sent: sábado, 28 de julio de 2018 11:39 a.m.

    To: jool-list at nic.mx

    Subject: [Jool-list] Jool and VirtualBox

    Hi all,

    I've the following setup:

    Host1 - Ubuntu with Jool as NAT64

    eth0 to Internet (dual-stack)

    eth1 to CLAT (IPv6-only)

    eth1 can be ethernet or attached to a WiFi AP

    -> host 1 works fine, no problems here, I've tested that in several ways, including an OpenWRT as the CLAT and dual-stack clients behind it

    Option a)

    Host2 - Mac OSX with VirtualBox

    VM1 - Ubuntu with Jool as CLAT

    Only one physical interface is used to connect to eth1 in host1, so shared (bridge) with the OSX

    This interface can be either Ethernet or WiFi

    -> IPv4 doesn't work if the interface is WiFi and this is the interface that I really need ...

    - ping6 works to both literal and dns

    - ping doesn't work

    - traceroute doesn't work

    - traceroute6 works to both literal and dns

    - wget only works with IPv6, not if I force IPv4 with -4

    -> IPv4 works if the interface is Ethernet, but some strange things happen with IPv6:

    - ping6 and ping work to both literal and dns

    - traceroute work to both literal and dns

    - traceroute6 only works if I force with -I ICMP instead of UDP

    - wget only works with IPv4, not if I force IPv6 with -6

    Option b)

    Host2 - Mac OSX with VMware Fusion

    VM1 - Ubuntu with Jool as CLAT

    Only one physical interface is used to connect to eth1 in host1, so shared (bridge) with the OSX

    This interface can be either Ethernet or WiFi

    It work in both IPv4 and IPv6 (ping6 see some DUP, but I think is normal because I'm "sharing" a WiFi for both paths)

    Option c)

    Host2 - Mac OSX with VirtualBox

    VM1 - Ubuntu with Jool as CLAT

    VM2 - Ubuntu as "client" of the CLAT

    Only one physical interface is used to connect to eth1 in host1

    This interface can be either Ethernet or WiFi

    The connection between VM1 and VM2 is using "intnet" (internal network)

    -> Nothing works if the interface is WiFi

    -> Everything works if the interface is Ethernet

    To make the setup easier, and ensure no mistakes in any config step, all the interfaces are configured with static addresses.

    I will be happy if I can make work just option c, but with WiFi, as this is for a workshop where the students will connect to an AP, no way we can provide long ethernet cables for everyone ...

    Option b with VMware is not an easy option, as it needs a license for each student ...

    I don't think (in principle) it is a Jool issue, beause it works with VMware, but I don't really know if there is some strange interaction with VirtualBox that Jool may need to consider.

    So, anyone has got similar issues with VirtualBox? Long time ago it had issues with IPv6 with using a wireless interface, but I believe this was not the case since several years ago ...

    Regards,

    Jordi

    **********************************************

    IPv4 is over

    Are you ready for the new Internet ?

    http://www.consulintel.es

    The IPv6 Company

    This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

    _______________________________________________

    Jool-list mailing list

    Jool-list at nic.mx

    https://mail-lists.nic.mx/listas/listinfo/jool-list

    Este mensaje contiene información confidencial y se entiende dirigido y para uso exclusivo del destinatario. Si recibes este mensaje y no eres el destinatario por favor elimínalo, ya que difundir, revelar, copiar o tomar cualquier acción basada en el contenido está estrictamente prohibido. Network Information Center, S.A. de C.V., ubicado en Ave. Eugenio Garza Sada 427 L4-6 Col. Altavista, Monterrey, México, C.P. 64840 recaba tus datos personales necesarios para: la prestación, estudio, análisis y mejora del servicio, la realización de comunicaciones y notificaciones; la transferencia y publicación en los casos aplicables; el cumplimiento de la relación existente; así como para la prevención o denuncia en la comisión de ilícitos. Si eres colaborador o candidato a colaborador de NIC México, tus datos serán utilizados para: la creación y administración de tu perfil como profesionista; el otorgamiento de herramientas de trabajo; la realización de estudios; el otorgamiento de programas y beneficios para mejorar tu desarrollo profesional; la gestión y administración de servicios de pago y/o nómina; así como para contacto y/o notificaciones. Si participas en promociones o en estudios podrás dejar de participar. Para mayor información revisa el Aviso de Privacidad<http://www.nic.mx/es/NicMx.AvisosDePrivacidad>.

    This message contains confidential information and is intended only for the individual named. If you are not the named addressee please delete it, since the dissemination, distribuition, copy or taking any action in reliance on the contents is strictly prohibited. Network Information Center, S.A. de C.V., located on Av. Eugenio Garza Sada 427 L4-6, Col. Altavista, Monterrey, Mexico, CP 64840 collects your personal data which is necessary to: provide, research, analyze and improve the service; send communications and notices; transfer and publish your personal data when applicable; fulfill the existing relationship; prevent or inform in the commission of unlawful acts or events. If the data is processed in your quality of candidate or collaborator of NIC Mexico, the purpose of treatment is to: create and manage your profile as a professional; provide you with working tools; conduct studies; grant benefits and programs to enhance your professional development; manage and administrate payment services and/or payroll; as well as to contact you. If you participate in promotions or surveys you may stop or quit your participation at any time. For more information read the Privacy Note<http://www.nic.mx/es/NicMx.AvisosDePrivacidad>.

**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.