Xenial fails to connect my intermediate AP (dhcp multicast)

Bug #1574474 reported by Lucas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
isc-dhcp (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hi,

On Xenial, neither manual nor automatic tools can connect to an intermediary AP (TPLINK TL-WR702N).
Ipv6 is disabled by kernel commandline. It worked fine on 12.04

uname -a output: Linux xxxx 4.4.0-21-generic #37-Ubuntu SMP 2016 x86_64 x86_64 x86_64 GNU/Linux.

only when connecting to this AP, UFW throws a
[UFW BLOCK] IN=wlp3s0 OUT= MAC=78:e4:00:91:97:fb:dc:53:7c:44:69:5c:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=15995 PROTO=2

the SRC here is my router,there is another line with src=192.168.0.254 which is my AP

I've done a sudo sysctl net.ipv4.icmp_echo_ignore_broadcasts=0; nothing changed.

when connecting, dhcp also throws a: addr6conf: unsuported family address.

when setting up manually IPv4 addresses, my AP is not pingable (no mention of my router, which is behind)

thanks

Lucas (lcsperais)
tags: added: xenial
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1574474/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → ufw (Ubuntu)
Revision history for this message
Seth Arnold (seth-arnold) wrote :

Could you double-check that your ufw rules are referring to the correct NIC? Interface naming has changed a few times recently, and I have a suspicion that your problems may be a result of the new names not matching existing ufw rules.

Perhaps disable ufw entirely for testing?

Thanks

Changed in ufw (Ubuntu):
status: New → Incomplete
Revision history for this message
Lucas (lcsperais) wrote :

hi,

I disabled ufw entirely and rebooted for effect: no change.

I prevented avahi-daemon from using ipv6: no effect

My AP is a WR702N, with a new firmware from 2016, I converted it to a router, no effect whatsoever (symptoms are the same: cannot event ping the device even in static ip)

dhclient throws a loop of those lines before timing out:
dhclient[2845]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 3 (xid=0x6c648c32)

when connecting directly to the router dhclient sends a
dhclient[2866]: DHCPREQUEST of 192.168.0.163 on wlp3s0 to 255.255.255.255 port 67
without the DHCPDISCOVER part

I tried disabling rp filters in sysctl, no effect I tried using igmpv2, no effect.

thanks

Revision history for this message
Seth Arnold (seth-arnold) wrote :

Alright, if ufw is disabled, perhaps it's an isc-dhcp-client issue.. thanks

affects: ufw (Ubuntu) → isc-dhcp (Ubuntu)
Changed in isc-dhcp (Ubuntu):
status: Incomplete → New
Revision history for this message
Lucas (lcsperais) wrote :

I tied a kernel 4.3 (it was compiled for trusty though, but my machine worked fine under it): no change.

I compiled and installed isc-dhcp 4.1 -ESVR13 from source and used it manually with wpa_supplicant : no change.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.