It was a problem with that Hyper-V version, some DHCPv6 related packet
was dropped somehow. Microsoft fixed it in a later version and it
started working. You can close this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0
** Summary changed:
- DHCPv6 does not work
+ DHCPv6 does not work in Hyper-V
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1624722
Title:
DHCPv6 does not work in Hyper-V
Status in lin
> I also verified (using dumpcap -xx and Wireshark) that Hyper-V does
not change the contents of the solicit packet.
It was tcpdump -xx and then dumpcap + Wireshark, certainly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
Since I cannot edit my above comment I post an update:
After writing the above post I checked the client again, just to be
sure. To my greatest surprise I found that the fec0::0:0:1::2 address
was correctly assigned to it!
Checked syslog on the server and found that the address was assigned 3
min
I've done the following test today on two physical machines, so no
virtualization is involved.
How to reproduce:
What I have tried today: Installed Ubuntu 14.04 64bit (kernel
4.4.0.-38-generic) on two physical machines (no virtualization
involved). Upgraded them and installed radvd and isc-dhcp-s
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1624722
Title:
DHCPv6 does not work in Hyper-V
Status in linux package in U
Adding on to my previous comment, I had tried a fresh Debian jessie
install with v3.16 of the Linux kernel. DHCPv6 works just fine until I
switch to the one in the jessie-backports repo, which currently is 4.6.
So somewhere between 3.16 and one of the 4.x kernels a regression was
introduced.
--
Y
I did a quick capture with Wireshark (this time using Hyper-V on Windows
10) and indeed the VM sends out a solicit, but I don't see any evidence
of it reaching the router (nothing in the logs). DHCP Guard is switched
off but I think that would affect a DHCP server, not a client. Plain
SLAAC with my
In my case this is not caused by Hyper-V's DhcpGuard feature either,
because that's turned off for both VMs involved. (Same for RouterGuard.)
See: https://social.technet.microsoft.com/Forums/en-
US/f03c0c8e-8924-4071-b86e-18fb141e4710/how-to-configure-dhcp-guard-in-
hyperv-2012?forum=winserverhyper
Additions to my previous comment:
- I have Ubuntu 14.04 LTS (and 16.04 LTS) 64 bit version set up as a router
with DHCPv6 support.
- Client is vanilla Ubuntu 14.04 64 bit desktop.
The problems I described above apply to the server VM, where the solicit
packet appears to be eaten by the kernel.
-
Same happens in Ubuntu 14.04 with kernel 4.4.0-36-generic. Also
reproduced on the above 16.04 distribution.
DHCPv6 server: isc-dhcp-server in IPv6 mode (isc-dhcp-server6)
Wireshark captures indicate that the solicit is sent from the client,
arrives to the server's network interface, then lost in
apport information
** Tags added: apport-collected
** Description changed:
When using Ubuntu (in this case the live 16.04.1 LTS ISO) as a
Generation 2 (Gen1 untested) Hyper-V VM, an IPv6 address can't be gotten
through DHCPv6. dhclient continues to send out solicitations but they
never r
13 matches
Mail list logo
