This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/

[ipv6-wg] ripemtg-nat64 network at RIPE71: complain here ;)

Previous message (by thread): [ipv6-wg] ripemtg-nat64 network at RIPE71: complain here ;)
Next message (by thread): [ipv6-wg] ripemtg-nat64 network at RIPE71: complain here ;)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Shane Kerr shane at time-travellers.org
Mon Nov 16 14:35:01 CET 2015

All,

Using VirtualBox on the NAT64 fails for me, although is partially due
to the wireless hardware I have.

If I use the NatNetwork interface style (NAT with IPv6 support), then I
don't see any DNS servers, so it's unusable.

If I use the bridged network interface style, IPv6 does get addresses
but can't actually use them. I think that this is a problem with my
Broadcom WiFi hardware, as it happens even using normal dual-stacked
IPv4/IPv6. I blame the evil out-of-mainline kernel drivers. (This setup
works fine using wired Ethernet.) 

VirtualBox 5.0.2
Debian testing / 4.2.0-1-amd64 kernel
Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter

Cheers,

--
Shane

Previous message (by thread): [ipv6-wg] ripemtg-nat64 network at RIPE71: complain here ;)
Next message (by thread): [ipv6-wg] ripemtg-nat64 network at RIPE71: complain here ;)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ipv6-wg Archives ]