so gonna add some more info to this, have been incontact with netcomm since this post and they are trying to simulate the issues in this thread and as previously talked about in this thread here: http://www.geekzone.co.nz/forums.asp?forumid=82&topicid=150662
04/05/15 17:03 Jason Rowe Just Added 3 wireshark files
1. When the issue happened on your laptop (can't see the connected ethernet device on the NF8AC, please run" arp -d on the said laptop on the commands prompt, and advise what is the result). I am able to go over to the Wi-Fi network supplied by the Technicolour device. Its coming back to the netcomm where the problem lies. I went NF8AC -> TG589 -> NF8AC and I had the following connection to the wired lan device: Connection -> Connection -> No connection, I can go back to the TG589 and the connection is fine to the wired lan device. . Using the apr –d command had no effect on the situation, it kept showing the NF8AC on the same MAC access which is to be expected.
2. When the issue happened again, when the laptop can't see the connected ethernet device on the NF8AC, please immediately connect that laptop to NF8AC with the ethernet cable and check, can now the laptop see the other connected device or not? Plugging the laptop back into an Ethernet cable enabled it to ping the other wired LAN devices. As soon as you unplug it and go back to Wi-Fi you loose that ability.
Issue is when your device was connected to another modem through WiFI and when you were moving back toward NF8AC, the cache on your laptop still maintain the MAC address of the other modem on the ARP, thus the laptop got confused. I don’t believe this matters though, as the arp cache still retains the MAC and IP of each device
Also I am aware that you are using manual static IP address on the computer, on this case, please try Obtain IP address automatically on all your PCs and set static IP address through NF8AC itself by going to Advanced Setup >> LAN >> click "Add Entries" button on the bottom >> type in the MAC address of your devices and IP addresses that you want for each one of them and save it. Did that no change
Ive noticed that the MAC address of the NF8AC is showing as the same no matter if its on Ethernet, 2.4ghz or 5ghz Wi-Fi, is this correct? InSSIDER is showing the 2.4 and 5ghz radios as having different MAC addresses, and they are also different to the one the NF8AC is showing when you do an arp –a. When my laptop connects via Ethernet it has a different MAC address to that of when its connected via Wi-Fi, even though the IP address might be the same. Not sure if is relevant or not.
I have manually added the ARP information using the following command:” netsh interface ipv4 add neighbors "Local Area Connection" IP address MAC Address”. That information showed in the ARP table but I was still not able to ping/connect to the device. But in doing so the response from my PC has gone from Destination Host Unreachable, to Request time out, which I think is significant.
Destination Host Unreachable This message indicates one of two problems: either the local system has no route to the desired destination, or a remote router reports that it has no route to the destination. If the message is simply "Destination Host Unreachable," then there is no route from the local system, and the packets to be sent were never put on the wire. If the message is "Reply From < IP address >: Destination Host Unreachable," then the routing problem occurred at a remote router, whose address is indicated by the "< IP address >" field.
Request Timed Out This message indicates that no Echo Reply messages were received within the default time of 1 second. This can be due to many different causes; the most common include network congestion, failure of the ARP request, packet filtering, routing error, or a silent discard.
So to me getting a time out, even though the device im pinging on the network, the NF8AC is droping the ICMP/ARP requests from the device on WiFi. I believe any ARP requests my laptop sends out are not being forwarded by the NF8AC so my laptop is unable to find a route to the PC. Even when entering the ARP info into the NF8AC it know the MAC address and IP of the PC but is still unable to connect to it
Im going to upload a few Wireshark files (I assume you use Wireshark?) which may or may not help with the diagnostic, im a little rusty with it so I might be missing something.
We did another test, this time our R&D engineer did the test, and unfortunately still using NetComm-NetComm devices since we don't have any other product then NetComm.
Could you do few test: 1. When the issue happened on your laptop (can't see the connected ethernet device on the NF8AC, please run" arp -d on the said laptop on the commands prompt, and advise what is the result). 2. When the issue happened again, when the laptop can't see the connected ethernet device on the NF8AC, please immediately connect that laptop to NF8AC with the ethernet cable and check, can now the laptop see the other connected device or not?
Issue is when your device was connected to another modem through WiFI and when you were moving back toward NF8AC, the cache on your laptop still maintain the MAC address of the other modem on the ARP, thus the laptop got confused.
Also I am aware that you are using manual static IP address on the computer, on this case, please try Obtain IP address automatically on all your PCs and set static IP address through NF8AC itself by going to Advanced Setup >> LAN >> click "Add Entries" button on the bottom >> type in the MAC address of your devices and IP addresses that you want for each one of them and save it.
Greetings. Please accept our sincere apology for the delayed response. Unfortunately we currently do not have a different unit for testing but we are trying to get one. We will keep you posted for further updates.
I believe testing with one netcomm router and one being used as an access point is a flawed way to conduct the testing as the fault is happening with non netcomm devices. I have shown myself with 3 different branded devices that there are issues with wireless devices talking to wired devices. I have also provided a link in which other people have the same issue again with non netcomm devices being used as an access point.
If you wish to try and replicate the symptoms that myself and others are seeing you are going to have to test it with another branded device as the access point.
Greetings. Thanks for your detailed email. We have tested this settings and it worked using our NetComm modem. Would you mind to update us on how it did go with your unit?
We look forward to hearing from you. Thank you and have a great day! 1 week ago #126946 16/04/15 17:53 Jason Rowe HI
Borrowed a couple more routers and switched them to access point mode to see if I could replicate the issues and with both routers tested they both had the same issues. The modems were: engenius ESR1221N2 300Mbps 802.11b/g/n Wireless N Router TP-LINK TL-WR841ND 300Mbps 802.11b/g/n Wireless N Router
When the devices connect they say the correct network name in the network settings, i.e. home. All the laptops have static IP addresses, they have a gateway assigned as the NF8AC, and the DNS server is either the NF8AC or my ISP’s DNS severs. The devices over DHCP are getting the correct IP’s for the relevant things. The gateway is only relevant when wanting to go outside your own LAN.
The issue im having is nothing to do with connecting to the internet i.e. outside my network, none of the devices have issues connecting to the net, only other devices on the network.
It seems to be that when the device connects to the access point it loses the ability to talk to any hard wired device on the LAN except the NF8AC. Weather this is due to how the NF8AC deals with where its MAC address is now coming from (a LAN port as opposed to one of the onboard WIFI devices) I don’t know. It’s a layer 2 issue though.
Im trying to get my hands on a second NETCOMM device so I can try it, your devices may have something in the firmware that allows them to pass this info or they pass this info slightly differently to other devices I don’t know.
Other information that you can please check, if the computers that are being connected to any of the modem have any "unidentified network" or not if you open the "Network and Sharing Center" on that computer.
The idea is, since computers are being connected to both SSID which sometimes can be modem "A" or "B" so we need to specify the default gateway on the computer itself so it can find the correct gateway.
So on that particular you may need to use static ip on the computer to enable you to specify the default gateway.
16/04/15 14:40 Jason Rowe Thanks again for the response
Might I suggest trying the test with a second access point that is not a Netcomm device, as all the examples, mine and others in those 2 threads listed, have different branded devices as the access points.
My AP device is a technicolour/Thompson (old VDSL modem) another person’s was a netgear device, im trying to get more info on other devices
From what others have said it seems to be a layer 2 issue,
Im going to try a few more things here and see what I can come up with
We ran a test for this setup connected to our NB604N with the same setup as yours, ethernet cable from NF8AC to our ADSL Modem as AP, put NB604N on the same network with NF8AC, turned off its DHCP and so far it is still working fine.
We had put SSID identical to each other and so far still running fine.
It has been 2 days, will see couple of days more, but the limitation on our testing environment is both modems are next to each other, our testing room is quite limited. But at least we can check devices connected to each modem and see if they can ping to each other or not, is it correct?
Attached is a copy of the current config, i have changed the username back to admin, the password for logging in is admin, and the 2.4 and 5ghz wifi passwords are both 12345678. thats all i have changed to whats currently running.
It seems like it is an issue with both the NF4N and the NF8AC, and it not liking the device going from the wifi interface to an Ethernet interface with the same MAC address.
If there is anything else you need please let me know
07/04/15 8:07 Jason Rowe Im more than happy to answer any extra questions on this via email or over the phone.
I wasnt able to add any more detais into the online form as it has a text limit on it. 3 weeks ago #30256 Add Note
So there is the communications so far, does anyone see anything else that could be tested or anything that could point to the issue?
I do have a few wireshark captures here if anyone who knows what they are looking at would care to have a look, as i havent used it for years and cant really remember what im looking at/for
Does anyone have a Netcomm device that would work as an access point that i could borrow for a week or so to do some of my own testing? it would be very much appreciated.
so it looks like we may have a resolution to this:
On 12/05/15, at 10:21, Ian Paul Budiman wrote:
Hi Jason,
Thanks for the email.
Our engineer has just updated me that after further testing and further investigation on the captured packet then they could see some inconsistency on this matter and the issue has been lodged and should be fixed on the next firmware update.
We thanking you for bringing this matter to our attention and your patience on this matter.
Please don't hesitate to contact us again if you need any further assistance.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.
ID Verified
