NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR750 Port Forwarding Not Working
I am trying to get port forwarding to work and I have not been successful. - I have tried with and without a DDNS service and neither has worked. - I have a static IP address assigned to my targe...
Thank you. I have tested that. TeamViewer is supposed to generate and send the magic packet but it needs to know where to send it. My public IP does match those sites. Now that I have updated to the newest version of FW my device list is missing connected devices and is showing incorrect IP addresses. This might be part of the problem.
- In my CMD window, it shows that the PC I am on has an internal IP address of 192.168.1.22(preferred)
- In the list of devices on the main Orbi Page, it has the correct device name listed with a different MAC address and IP address as 192.168.1.14
- When I check the DHCP Reservation, it still shows the correct device name and the MAC address and IP address match what is shown in the CMD window when the ipconfig /all command is run.
Both this PC and another are plugged into the Orbi Satelite and only one is showing up even though they both have access to the internet. Neither of them match the MAC or IP address as shown for the 1 device name it did see. I am getting very confused.
I think 7.1.2 on page 15 might be the problem:
https://dl.teamviewer.com/docs/en/TeamViewer-Manual-Wake-on-LAN-en.pdf
(Having failed thus far to find a solution, ..........)
UDP is really frustrating because there is no "connection" like there is with TCP. (The sender does not send a connection request, wait for the target to respond, OK (an "Ack"), then send the first data packet. And, the data packets have sequence numbers which guarantee that if they get out of order during their journey through the internet, they get put back together in the correct order. UDP is just, "Send" and that's the end of it.
So, if the TeamViewer server sends a UDP Magic Packet to the public IP address, the Orbi will forward that packet (without changing anything) to..... Where?
- If the target PC is "connected", the Orbi can find it using Address Resolution Protocol (ARP). "Who has 192.168.1.22?"
- If the target PC is not connected, I'm not sure what the Orbi can do with this packet.
The Wikipedia article has a section on troubleshooting:
https://en.wikipedia.org/wiki/Wake-on-LAN
Things like:
- which port does this Ethernet card expect WOL to appear on? (0? 7? 9?)
- which power states does it "wake" from?
- will it accept a Magic Packet that is not a Broadcast packet? (IP address 255.255.255.255)
I would approach this in two steps:
- Does the Orbi forward the Magic Packet to the target computer when the computer is turned on?
Use Wireshark on the target PC to see if the Magic Packet arrives.
Perhaps use the Orbi debug mode to 'capture LAN/WAN traffic' and verify that (a) the Magic Packet appears on the WAN interface and (b) is transmitted out the LAN interface. - What happens when the computer is turned off?
Wireshark is no good for this because the computer is not running. hmmm.....