workarounds:
sudo sysctl net.ipv6.conf.wlan0.accept_dad=0
followed by disconnecting and reconnecting wireless gets IPv6 back for me for
the session, and
adding 'net.ipv6.conf.wlan0.accept_dad=0' to '/etc/sysctl.conf' got IPv6 to
work on reboots.
without that command:
IPv6 works on my Orange
In a new setup (Sitecom router, no more Zyxel) and Ubuntu 13.10, I still
have the same problem via Wifi:
[ 1782.075212] IPv6: wlan0: IPv6 duplicate address
2001:abc:1234:b45d:1af4:6aff:fe9c:ced4 detected!
[ 1813.616483] IPv6: wlan0: IPv6 duplicate address
2001:abc:1234:b45d:1af4:6aff:fe9c:ced4
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1120617
Thanks to further analysis of Joost, the problem seems to be in the
Zyxel firmware, not in Ubunt / Linux: problem occurs after changing the
default SSID name to something else. See https://forum.telfort.nl
/pilots-feedback-273/ipv6-p-2812hnu-f1-wifi-dad-33361/ (warning: Dutch)
--
You received
Think it's a modem/modem firmware issue.
I'm experiencing the same behavior on WiFi when using the Zyxel P-2812HNU-F1
with firmware V3.11(TUE.5) ( telfort )
With MacOSX, IOS and Linux. Autogen fails, manual works.
On the wire no problems.
--
You received this bug notification because you are a
FWIW:
I tested OpenSuSE 12.2, and it has the same problem as Ubuntu 12.10. So,
conclusion: not a Ubuntu-only problem.
However:
I tested Raspbian (a Debian derivative , Linux 3.6.11 on armv6l) on my
Raspberry Pi, and it has NOT the problem. Settings:
pi@raspberrypi ~ $ sudo sysctl
One Step Further:
A big difference between the Laptop and Netbook versus the Raspi: the
laptop and netbook are connected via Wifi, the Raspi via wired ethernet.
So is it wlan related?
So let's test that hypothesis.
I booted a fresh Ubuntu on a third laptop, connected via Wifi, and I had the
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.8 kernel[0] (Not a kernel in the daily directory) and install both
the linux-image and linux-image-extra .deb packages.
If this bug is fixed in the
Joseph, thanks for your reply.
It's a long time that I upgraded a kernel, so maybe I'm wrong, but I
don't see a 3.8 for Quantal (which I'm running). Only for Raring. See
below. Tips?
But maybe this is easier for me: run Raring daily from a USB stick. I Checked
Raring daily in a VM, and it has
I'm now running 13.04-to-be Raring Ringtail daily version (so
2013-02-12), with Linux 3.8.0-6-generic, and ... exactly the same
behaviour:
After connecting to the Wifi, two public IPv6 address appear on the
wlan0, and then disappear within a second or so. And dmesg says:
[ 280.076792] IPv6:
PS:
1) FWIW: I'm running the 13.04 from a live-USB-stick
2) To avoid confusion: I did the sudo sysctl net.ipv6.conf.wlan0.accept_dad=0
part after seeing the default behaviour was buggy. So the above report is in
chronological order.
--
You received this bug notification because you are a
PS:
I also checked my netbook with Ubuntu 11.10, and it showed the same problem. It
might be I have turned on privacy extensions on that device.
I also ran a fresh Ubuntu 12.10 from a USB stick, and it showed the same problem
net.ipv6.conf.all.use_tempaddr=0 (instead of -1) also gives a
Ouch: as described above, I tried
net.ipv6.conf.eth0.accept_dad = 0
which didn't work ... but I'm using wlan0, so I tried
net.ipv6.conf.wlan0.accept_dad = 0
and that works. So turning off DAD / Duplicate Address Detection is a much
better workaround:
1) I do get a private extension IPv6
13 matches
Mail list logo
