I have an older Samsung smart TV with an Ethernet port. I bought a Netgear WNCE3001 universal wifi adapter which plugs into the Ethernet port and gets its power from a USB port. This has always worked well. I recently bought a hAP AC and placed it next to the TV, connected to a CCR1009-7G-1C-PC Cloud Core router. It was initialized in CAP mode, putting all its Ethernet ports in the bridge for my LAN. The wifi has been provisioned with CAPsMAN and works well with the WNCE3001 and other wireless clients, Windows devices have been connected to the hAP with cable and they work fine. However, when I connect the Samsung to the hAP with cable, the Samsung cannot get internet access. It is assigned an IP address, gateway and DNS server but it won’t connect to the Internet. I have looked at all the packets to and from the TV and it doesn’t appear to even try to go outside the LAN. The Samsung is working with the LAN and can see some DLNA servers but can’t get to the Internet. I have straight and crossover cables but no luck. Any ideas or suggestions about this issue?
Try to connect something else to the wifi adapter and see if that works.
If you mean the Netgear, it connects to a single Ethernet port and connects to the wifi network so that a single wired-only device can communicate wirelessly. Using that, the Samsung accesses the Internet fine. What is odd is that the TV gets the same IP address, gateway and DNS server through the Netgear as it does when wired to the hAP. It just can’t get to the Internet wired but can wirelessly through the Netgear. The CAP wireless interface is on the same bridge as the hAP ethernet port. Nothing connects to the Netgear wirelessly; it connects to an AP.
If you mean connect something else to the hAP, that has already been done. Everything connects fine wirelessly, including a Samsung TV (with integrated wifi) in another room.
I was trying to find if there is something that prevents network connectivity for the Samsung via your MikroTik, which is unrelated to the WiFi adapter, or if there is a problem with the WiFi adapter.
But maybe I don’t understnad your configuration.
There are “known issues” that affect the DHCP function for some obscure devices. It could be that the Samsung does not get a proper IP and/or other parameters from the MikroTik DHCP server while it was OK on your older router. But that has to be determined somehow.
@TomSF: do I understand correctly that connection between TV and internet is according to this ASCII art?
working configuration:
internet <--> CCR <-- wire --> hAP ac (CapsMan controlled) <-- wifi --> Netgear <-- wire (sort of) --> TV
non-working configuration:
internet <--> CCR <-- wire --> hAP ac (CapsMan controlled) <-- wire --> TV
There are things that CapsMan configures on CAPs which might prevent things from working.
I suggest that you post full configuration of both CCR and hAP ac (sensitive data, such as WiFi security profile, publis IP address or PPPoE credentials, obfuscated). You can get it from console using command /export hide-senstive.
Also: is the IP config on TV consistent with settings for your LAN (e.g. correct IP network address and subnet mask, correct default gateway)?
To debug this problem, I started over. The cable to the router is on ether1 of the hAP. I disabled CAPsMAN manager on the router and factory reset the hAP into CAP mode. CAPsMAN had not provisioned the hAP. A wired Windows netbook could access the internet but the wired Samsung could not. It was the same problem; valid IP address, netmask and dns server but no internet. The IP info is the same as when the Samsung is connected via Netgear adapter. I then reset the router to the factory defaults and retested. Doing that, both the netbook and TV could get the internet. The problem seems to be in the router configuration, not hAP configuration or CAPsMAN managemnt. I captured the factory router configuraton and my normal coniguration and am going through them to issolate the cause. If I can’t find it, I will post both and ask for help. Stay tuned.
I got the Samsung working! The following are the changes between a configuration that didn’t work and one that does. In some cases, my action resulted in using default values for a parameter. I don’t know which one(s) was the key one and would welcome any explanations or opinions. If desired, I can post the before and after configurations for each change.
- For /interface bridge, I removed “add arp=reply-only” and “fast-forward=no” from bidge1 (non-guest LAN) and guestAPbridge.
- For the DHCP servers on bridge1 and guestAPbridge, I removed “add-arp=yes”.
- For the ports on bridge1, I removed “hw=no”.
- For /ip neighbor discovery-settings I changed “set discover-interface-list=none” to “set discover-interface-list=all”.
- For /ipv6 nd, I removed “set [ find default=yes ] hop-limit=64 other-configuration=yes”.
Did you check the ARP tables (on the router and the device) before you made that change?
I think the arp=reply_only / add-arp=yes configuration could cause obscure problems, that would be the first I disable when there is no connectivity.
I did not check the ARP tables before the change and can’t see the tables on the TV but I did some more tests. I have confirmed that the key is the DHCP Server setting for add ARP for leases. It seems that this would be a desirable setting but with it enabled, the Samsung cannot get to the internet. It has a valid entry in the router ARP table though. With it disabled, it can and it has no entry in the router ARP table. The mystery continues…
Maybe the Samsung has some weird implementation of ARP or a strange replacement for its function.
I sometimes have read about Android and Apple devices that can change their MAC address during operation for some strange privacy reason.
I never dared to use this special mode on our WiFi guest network with hundreds of users, too scared that something might not work and people might spend hours figuring out what is wrong.
Your experience has confirmed my feeling…
The DHCP server lease information has MAC address and Active MAC address which might be related to what you mentioned. For the Samsung, they are both the same. Someday I might string a long cable from one of my other Samsung TV’s to see if the problem is Samsung wide or just related to this model.