WSL2 Port Forwarding?
So I've got no issue port forwarding on my windows 10 server, it works fine, but the issue comes when I'm port forwarding for an application running in WLS2 on that same windows server. I configured WSL2 so that it uses the ipv4 address 192.168.0.100, and this works just fine as any device on the local network can ping 192.168.0.100 and get a response. My issue is: when I go to port forward 192.168.0.100 on port 27018, you can't port forward by IP address, rather you must first "select a device for this port forward." I figured the best way to add wsl2 as a connected device would be through my routers gateway control panel. I clicked on connected devices, then add device with reserved IP, I added WSL2 by entering it's MAC address and reserving 192.168.0.100 for it, and after a second WSL2 appears as a connected device under the "Online Devices-Private Network" tab. After only 2ish minutes though, WSL2 is moved down to "Offline Devices", which means I can't use it for the "select a device for this port forward" step, so there's no way to port forward 192.168.0.100 on port 27018. This is despite the fact wsl2 is certainly still connected and every device on the network can still access it with ping 192.168.0.100. Worst part is, if I chose "forget this device" in the cox wifi app, the app deletes my WSL2 entry so I can't interact with it anymore, but it's still saved under "Offline Devices" so the IP I reserved for it is permanently reserved for a device that will never go online. I've done this multiple times while testing, so addresses: 192.168.0.16, 192.168.0.17, and 192.168.0.100 are now permanently locked to devices who will never go online. Is there any way to port forward by IP address, or a way to make WSL2 not be dropped to "offline devices" despite being reachable by every device on the local network? If I am quick enough and port forward my wsl2 before it's dropped to "offline devices", will my router continue port forwarding 192.168.0.100 on port 27018 even after it's moved to "offline devices"? That would an okay workaround if so, I only haven't experimented because every time I make an attempt, I risk making more ipv4 addresses reserved to offline devices, and therefore they become inaccessible. If not the only alternative is to buy a better non-cox router right?Solved302Views0likes3CommentsPort Forwarding, Correct IP not showing up in Cox's website
I've been setting up a minecraft server for some friends and I am running it on a separate desktop. I've gotten all the way to here where you have to port forward using the IP of the device but it's not showing up. It's discoverable on the network seeing as how I'm tapped into it from my main Computer. It's frustrating that you can't put in a static IP on Cox's website. About to purchase my own router and not deal with this.729Views0likes3CommentsUnable to access self hosted server via public IP
I have a Raspberry Pi at home that I often use for development purposes. And I am able to access(SSHd running on a custom port) this device when I am on my home network (LAN) using its private IP. The custom port where my device's SSHd runs is port-forwarded using the Cox Panoramic WiFi app. Until a few days ago, I was able to access my device using the router'spublic IP via custom port. Currently, I am still able to access the device using the public IP when I am outside the LAN. But I am not able to access using the public IP when I am on my home network (LAN). Does anyone have any solutions?Solved207Views0likes3CommentsPort Forwarding on Cox Wi-fi App?
I am having trouble opening ports on my TG1682G Panoramic Wi-Fi router. I have installed the Cox Wi-Fi app, but it has proved unhelpful. Going to the dedicated section for port forwarding immediately throws an error message, saying "Something unexpected happened", with no further technical details that could help me diagnose the issue. I am running an up-to-date version of the Android Cox Wi-Fi app on my phone, and this feature fails to function both over cellular data and over Wi-Fi. There are other sections of the app that also tell me they "can't display [my] details right now", which may indicate an issue with the service the app should be connecting to. There is no other means of opening ports on my router, since the feature has been removed from all other services- accessing the router from the default gateway results in a redirect to wifi.cox.com, which has also seen its features stripped to move to the app. Many posts on this forum say "Buy another router". Maybe someday soon- but I'd appreciate help in finding interim/stop-gap solutions, even frustrating ones, if there are any. One post had a recommendation to reach out to an email, but they asked for a lot of personal information- so I asked for a phone number. No reply yet.1KViews1like2CommentsCan't delete port forward with Panoramic Wifi App.
As the title says. For some reason, I can not delete any of my port forwards with the Panoramic Wifi App. And I can't go tohttps://wifi.cox.com/network/advanced-settingsto do it there cause for some stupid reason they put it to where it shows where you can download the app and they removed the feature of port forwarding from the router site that's connected to the IP address. If anyone can help me and tell me why they made if I have to be really blunt here, these stupid decisions that just make it more difficult.718Views0likes4CommentsCox Gateway Port Blocking and macOS
I am trying to use VMware on my Mac to connect to my work VM. Every time I try to connect I get an error that the connection has timed out. If I use my iPhone as a hotspot instead of WiFiI can connect with no issues. Googled and found that it is probably blocked ports on the Cox side. I did set up port forwarding using the Cox WiFi app and I still can not connect. I have tried a bunch of different ports the last ones I tried are 443, 4172, 8443, and 22443. Please help!!! macOS Monterey VMware Horizon Client 2206 Panoramic WiFi Gateway: Technicolor - CGM4140COM2.1KViews0likes13CommentsUnable to create or edit existing port forwards (Panoramic Router)
I am currently unable to to modify or create new port forward on my Cox Panoramic Router. I have been able to make them in the past, without any issues at all. However for the last few months, when I attempt to make/edit an existing port forward I get a error saying message saying "We're having some trouble - Please try again. If the problem persist, check back later". (Screenshot:https://www.screencast.com/t/PmLOGrVKFE) I've tried the following steps to attempt to resolve this: Restarted Gateway (duh) Cleared cache and cookies as well as attempt port forwards from 3 different desktop computers - same error Installed the "Cox Wifi App" on my phone (with wifi turned off) to remote manage gateway setting - same error (rules out a device or network issue) Factory reset the Gateway - Obviously this cleared my old port forwards as well as everything else, forcing me to manually re-configured my network... but I am still unable to create a new port forward (same error) At this point I am convinced it must be something with either the gateway itself, or a recent update changed something on Cox side with the remote management tool works. Has anyone else had this issue? Surely I can't be alone here!576Views0likes0CommentsCox port data throttle question
Multiple people in my house are trying to play the same game. The game needs to communicate over ports: TCP 54992-54994, 55006-55007, 55021-55040 From working at spectrum/charter in the past, I know there is a throttle limit for data when it comes to uncommon ports. I know service reps also have no idea what I am talking about if I were to call them. Most of our "head end" techs were unaware of this as well. My question is, who do customers contact or how do we convey to our ISP that data over certain ports shouldn'tbe throttled when multiple users need to use them?572Views0likes0Comments