[opensuse] TP-Link WA-901N AP
On 2020-03-22 04:55 AM, Per Jessen wrote:
Two of our access points are TP-Link TL WA901 and WA801 - they both support 4 SSIDs with VLANs. We have assigned a separate VLAN for the guest SSID.
As I mentioned in another note, routers might provide only guest SSIDs, which only allow access to the Internet. Access points can use VLANs to connect as needed to the network.
BTW, I also have a TP-Link WA-901N AP. It has a bug in it which allows multicasts to leak from the main LAN to the VLAN. This makes it impossible for me to use another SSID, as the IPv6 router advertisements leak from the LAN to the guest VLAN, which results in the devices getting addresses in the wrong network. Mine is version 2 and I don't know if that has been fixed in later versions.
The exact number I have is TL-WA901ND. I see: Firmware Version: 3.16.9 Build 150408 Rel.38268n Hardware Version: WA901ND v4 00000000
When I called their support, the first level insisted that was normal. However, 2nd level agreed it was a problem, but there was no fix forthcoming.
<anecdote> 12-15 years ago, I had an issue with a Zyxel ADSL router - I wanted it to log messages to my syslog daemon, which it had the options for. It just didn't work. I kept harrassing the local support, and managed to make someone reproduce the problem. In the end I got a firmware package which fixed the problem, but it was never made public :-) </anecdote> -- Per Jessen, Zürich (6.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-03-22 10:25 AM, Per Jessen wrote:
Firmware Version: 3.16.9 Build 150408 Rel.38268n Hardware Version: WA901ND v4 00000000
Here's my info: Firmware Version: 3.12.16 Build 130131 Rel.53760n Hardware Version: WA901N v2 00000000
When I called their support, the first level insisted that was normal. However, 2nd level agreed it was a problem, but there was no fix forthcoming. <anecdote> 12-15 years ago, I had an issue with a Zyxel ADSL router - I wanted it to log messages to my syslog daemon, which it had the options for. It just didn't work. I kept harrassing the local support, and managed to make someone reproduce the problem. In the end I got a firmware package which fixed the problem, but it was never made public:-) </anecdote>
Sometimes support can be "fun". Last year I had a problem with IPv6. After a bit of testing I determined that while I could ping etc. from my firewall, I couldn't from my LAN. I could also ping the firewall from elsewhere, but not anything on the LAN. With Wireshark, I could see the outgoing pings from my LAN, but no reply. When I pinged from outside, I didn't see it at all. Traceroute showed similar. I was able to convince tier 2 support that there was a problem, but the people responsible for maintaining the network refused to do anything, as I was using my own router/firewall (pfSense), with the modem in bridge mode. My next door neighbour also had the same problem, but he had only a single computer and had the modem in gateway mode. I did some more testing with Wireshark, capturing DHCPv6 traffic, and could see the CMTS was generating an error message about no prefixes being available and was even able to identify the failing system by host name! Still, those network guys wouldn't do anything. I then had a senior tech come to my home, with his own modem. That also failed. He then took his modem to the cable head end and tested with 4 different CMTS. Only the one I was connected to failed. This finally convinced the network guys there was a problem they had to fix and this was only after 3 months! I was only able to get this resolved because of my technical ability and determination. A regular customer wouldn't have had a hope. Also, I found I had to teach both the tier 2 and senior tech some of the finer details about how IPv6 works, as they had only a general idea. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-03-22 10:25 AM, Per Jessen wrote:
The exact number I have is TL-WA901ND. I see:
Firmware Version: 3.16.9 Build 150408 Rel.38268n Hardware Version: WA901ND v4 00000000
Do VLANs properly support IPv6 with it? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 2020-03-22 10:25 AM, Per Jessen wrote:
The exact number I have is TL-WA901ND. I see:
Firmware Version: 3.16.9 Build 150408 Rel.38268n Hardware Version: WA901ND v4 00000000
Do VLANs properly support IPv6 with it?
That is one thing I have not tested. Years back, I raised a ticket with Android about not supporting ipv6-only mode, and since then I have only handed out IPv4 to guests. I have seen some issues with a number of nanopis that we run - sometimes they "miss" RAs, and then suddenly cannot be reached on IPv6. I _have_ suspected the APs for a while, but I have had nothing solid to go on. -- Per Jessen, Zürich (3.8°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-03-22 02:10 PM, Per Jessen wrote:
James Knott wrote:
On 2020-03-22 10:25 AM, Per Jessen wrote:
The exact number I have is TL-WA901ND. I see:
Firmware Version: 3.16.9 Build 150408 Rel.38268n Hardware Version: WA901ND v4 00000000 Do VLANs properly support IPv6 with it?
That is one thing I have not tested. Years back, I raised a ticket with Android about not supporting ipv6-only mode, and since then I have only handed out IPv4 to guests.
I have seen some issues with a number of nanopis that we run - sometimes they "miss" RAs, and then suddenly cannot be reached on IPv6. I _have_ suspected the APs for a while, but I have had nothing solid to go on.
The problem I had was that devices on the guest SSID would receive the RA from the LAN, rather than the VLAN and would get wrong addresses. In what way does Android not support IPv6 only? What's a nanopi? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 2020-03-22 02:10 PM, Per Jessen wrote:
James Knott wrote:
On 2020-03-22 10:25 AM, Per Jessen wrote:
The exact number I have is TL-WA901ND. I see:
Firmware Version: 3.16.9 Build 150408 Rel.38268n Hardware Version: WA901ND v4 00000000 Do VLANs properly support IPv6 with it?
That is one thing I have not tested. Years back, I raised a ticket with Android about not supporting ipv6-only mode, and since then I have only handed out IPv4 to guests.
I have seen some issues with a number of nanopis that we run - sometimes they "miss" RAs, and then suddenly cannot be reached on IPv6. I _have_ suspected the APs for a while, but I have had nothing solid to go on.
The problem I had was that devices on the guest SSID would receive the RA from the LAN, rather than the VLAN and would get wrong addresses.
In what way does Android not support IPv6 only?
It was probably 4-5 years back, there is a ticket somewhere. Back then, niether iPhone nor Android supported an IPv6-only network, they required IPv4 first.
What's a nanopi?
A small ARM-device running Linux. -- Per Jessen, Zürich (2.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-03-22 03:18 PM, Per Jessen wrote:
In what way does Android not support IPv6 only? It was probably 4-5 years back, there is a ticket somewhere. Back then, niether iPhone nor Android supported an IPv6-only network, they required IPv4 first.
I just tried an experiment. I turned off the DHCP server and tried connecting to WiFi with my Pixel 2 phone. The WiFi icon flashed a "?" and then connected. IPv6 worked, but IPv4 didn't, as expected. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-03-22 03:24 PM, James Knott wrote:
On 2020-03-22 03:18 PM, Per Jessen wrote:
In what way does Android not support IPv6 only? It was probably 4-5 years back, there is a ticket somewhere. Back then, niether iPhone nor Android supported an IPv6-only network, they required IPv4 first.
I just tried an experiment. I turned off the DHCP server and tried connecting to WiFi with my Pixel 2 phone. The WiFi icon flashed a "?" and then connected. IPv6 worked, but IPv4 didn't, as expected.
I just tried the same experiment with 15.0 & KDE network manager. It failed. Even though it got a valid IPv6 address, it does not get a DNS server address, even though RDNSS is available. Also, while IPv6 initially works, it also fails when the connection times out. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-03-22 03:24 PM, James Knott wrote:
On 2020-03-22 03:18 PM, Per Jessen wrote:
In what way does Android not support IPv6 only? It was probably 4-5 years back, there is a ticket somewhere. Back then, niether iPhone nor Android supported an IPv6-only network, they required IPv4 first.
I just tried an experiment. I turned off the DHCP server and tried connecting to WiFi with my Pixel 2 phone. The WiFi icon flashed a "?" and then connected. IPv6 worked, but IPv4 didn't, as expected.
I reported this issue a while ago: https://bugzilla.opensuse.org/show_bug.cgi?id=1113152 Perhaps someone could try this with 15.1 or 15.2, as it is something that should be fixed. While most networks still provide IPv4 as well as IPv6, the day is coming when there will be IPv6 only networks. My cell phone carrier is already there. My phone runs IPv6 only and requires 464XLAT to access IPv4 only sites. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-03-22 03:18 PM, Per Jessen wrote:
It was probably 4-5 years back, there is a ticket somewhere. Back then, niether iPhone nor Android supported an IPv6-only network, they required IPv4 first.
Was it a DNS issue? IIRC, Android needed to use DHCPv4 to get a DNS server address as, for some idiotic reason, Android does not support DHCPv6. However, RDNSS is now available and I seems to work with Android. I have no idea about iPhones, as I'm allergic to Apple gear. ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 2020-03-22 03:18 PM, Per Jessen wrote:
It was probably 4-5 years back, there is a ticket somewhere. Back then, niether iPhone nor Android supported an IPv6-only network, they required IPv4 first.
Was it a DNS issue? IIRC, Android needed to use DHCPv4 to get a DNS server address as, for some idiotic reason, Android does not support DHCPv6. However, RDNSS is now available and I seems to work with Android. I have no idea about iPhones, as I'm allergic to Apple gear. ;-)
I don't remember if anyone gave me an explanation - I gave up pursuing it, the situation was slightly contrived. -- Per Jessen, Zürich (-1.7°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
James Knott -
Per Jessen