05-01-2024 10:31 AM
Hello. I experienced an issue today that I found several closed threads about , but I didn’t happen across the exact situation. I had. It’s possible I may have missed it, but wanted to share this information just in case.
I had switched most of my lan systems to static IP addresses some time ago and today was not seeing the desired device in the list of devices available for port forwarding. What I found in my case, is that the device was in the IPv6 list, but not in the IPv4 list. After disabling IPv6 on the device (and generating traffic on that system), the device then showed in the IPv4 device list for port forwarding.
Is it expected that showing in the IPv6 list would prevent showing in the IPv4 list?
05-04-2024 03:31 PM
Hello @_buffalobill_,
Thanks for reaching out to the community! I understand your confusion about the device not showing up in the IPv4 list. No, normally, seeing a device in the IPv6 list shouldn't prevent it from appearing for port forwarding. Here are some possible reasons and troubleshooting steps:
Possible Reasons:
Router Configuration: Some routers might prioritize IPv6 over IPv4 for device discovery. Disabling IPv6 forced the router to rely solely on IPv4, making the device visible in that list.
Device Settings: In rare cases, some devices might have a setting that conflicts with displaying on both IPv4 and IPv6 lists simultaneously. Disabling IPv6 on the device itself might have resolved this conflict.
Troubleshooting Steps:
Here are some steps you can take to address the issue:
Check Router Settings:
Review device settings:
Test with re-enabled IPv6:
I hope the information above works for you. Please let me know if you have any other questions.
All the best,
Jorge.
05-17-2024 10:24 PM - edited 05-17-2024 10:26 PM
Just to add some detail if it comes up for anyone else, the only router at play is the Google WiFi router
Model: AC-1304
Software version: 14150.376.32
the device in question was an Ubuntu VM with no LAN access issues. It was listed in the devices portion of the app, but was not listed in the IPV4 devices to be able to port forward to.
I got things working the way I wanted by disabling IPV6 on the Ubuntu VM, just not clear why it was necessary.
If this doesn’t sound like expected behavior and/or cannot be replicated, this thread may be closed as far as I am concerned.