Ubee EVW32C port forwarding help

Kenneth Cruz67 said:Are you absolutely sure you and customer support are even on the same page here? I mean, did you happen to mention to them that this isn't some fancy NAS setup, but just a simple USB drive without any kind of dedicated network card? There isn't really anything to forward when the router's IP and the USB's IP are essentially one and the same.

Okay, I suppose that explains why the drive isn't accessible without port forwarding, but wouldn't port forwarding be the actual solution to that? Like, wouldn't you just open a port on the external IP and then have everything hitting that port forwarded to an internal IP?

There isn't really anything to redirect if the drive is plugged directly into the router itself, because there isn't a separate internal IP to point to.

So, does that mean things work differently on your router? Is the drive actually exposed directly via the external IP?

Yes, exactly! So, when I type in my external IP, I get directed straight to my router's login page, assuming I'm browsing the web through that same router. However, if I try to access it from a completely different network, it actually sends me right to my server where Apache is running, since I've gone ahead and forwarded port 80. And if I try to connect via FTP using the external IP, it prompts me for a username and password and then opens up my USB drive just like that.

Additionally, if this functionality is just hardcoded into the router and it doesn't support port forwarding to itself, I guess I might need to pick up some extra hardware.

You could probably just grab a WD network drive, maybe something like a My Cloud, for roughly $100 to $500

https://www.amazon.com/products/detail...m_medium=click

Yeah, we're definitely talking past each other—I think. Like, he totally understood what I was asking, but then he goes, "Man, nobody has ever asked me anything like this before," and since this isn't exactly a standard service AT&T provides, they aren't exactly experts on it.

Kenneth Cruz67 said:Are you absolutely sure you and customer support are even on the same page here? I mean, did you happen to mention to them that this isn't some fancy NAS setup, but just a simple USB drive without any kind of dedicated network card? There isn't really anything to forward when the router's IP and the USB's IP are essentially one and the same.

Okay, I suppose that explains why the drive isn't accessible without port forwarding, but wouldn't port forwarding be the actual solution to that? Like, wouldn't you just open a port on the external IP and then have everything hitting that port forwarded to an internal IP?

There isn't really anything to redirect if the drive is plugged directly into the router itself, because there isn't a separate internal IP to point to.

So, does that mean things work differently on your router? Is the drive actually exposed directly via the external IP?

Yes, exactly! So, when I type in my external IP, I get directed straight to my router's login page, assuming I'm browsing the web through that same router. However, if I try to access it from a completely different network, it actually sends me right to my server where Apache is running, since I've gone ahead and forwarded port 80. And if I try to connect via FTP using the external IP, it prompts me for a username and password and then opens up my USB drive just like that.

Additionally, if this functionality is just hardcoded into the router and it doesn't support port forwarding to itself, I guess I might need to pick up some extra hardware.

You could probably just grab a WD network drive, maybe something like a My Cloud, for roughly $100 to $500

https://www.amazon.com/products/detail...m_medium=click

So at this point, it's either the router doesn't allow IP access to Samba, or if it's set up to stay off the public address, then the whole thing is just a paperweight...

Kenneth Cruz67 said:Are you absolutely sure you and customer support are even on the same page here? I mean, did you happen to mention to them that this isn't some fancy NAS setup, but just a simple USB drive without any kind of dedicated network card? There isn't really anything to forward when the router's IP and the USB's IP are essentially one and the same.

Okay, I suppose that explains why the drive isn't accessible without port forwarding, but wouldn't port forwarding be the actual solution to that? Like, wouldn't you just open a port on the external IP and then have everything hitting that port forwarded to an internal IP?

There isn't really anything to redirect if the drive is plugged directly into the router itself, because there isn't a separate internal IP to point to.

So, does that mean things work differently on your router? Is the drive actually exposed directly via the external IP?

Yes, exactly! So, when I type in my external IP, I get directed straight to my router's login page, assuming I'm browsing the web through that same router. However, if I try to access it from a completely different network, it actually sends me right to my server where Apache is running, since I've gone ahead and forwarded port 80. And if I try to connect via FTP using the external IP, it prompts me for a username and password and then opens up my USB drive just like that.

Additionally, if this functionality is just hardcoded into the router and it doesn't support port forwarding to itself, I guess I might need to pick up some extra hardware.

You could probably just grab a WD network drive, maybe something like a My Cloud, for roughly $100 to $500

https://www.amazon.com/products/detail...m_medium=click

Look, it's not that deep—I've got three USB drives at home, an Android stick, and an Android box sitting there. Honestly, this whole thing is just me messing around for the hell of it; I don't actually *need* any of this. There is zero chance I'm spending real money on it. It's more of a "let's see if I can actually pull this off" kind of hobby rather than a necessity. If this fails, I'll probably just try to burn something onto an old Android stick and route it through there, and if that's a bust, I'll move on to the newer box. Either way, the tinkering never ends.
I'm thinking about shooting an email to AT&T and the manufacturer just to get some clarity on this mess.

Edit: Ubee doesn't provide end-user support; they'll just tell you to call your service provider.

wiredcanyon94 said:It’s not the ISP. You can prove that to yourself by trying to access something inside your own network from an outside connection—assuming you actually set up your port forwarding correctly, of course.
If that works, but what you're trying to do still fails, then the provider is definitely messing with something on their side.

Yeah, I was planning on running that test today, but honestly, the day just kind of got away from me.
It’s getting close, but I really want to be 100% sure before I jump to conclusions.
If it turns out to be what I think it is, I'm moving straight to Plan B with that Android stick—unfortunately, it's stuck on Android 4.something, so I'm guessing X is going to make things... interesting.😁

Check if you're stuck behind CGNAT—it probably is.

shadowviper12 said:Hey everyone,

So, I’ve got this Ubee EVW32C-0S-010 router sitting on my desk, and I decided to get a little adventurous—you know how it goes—and try hooking up an external hard drive to it. The goal? To share my music and movie collection across the network. I actually managed to get the local sharing working just fine; the drive shows up perfectly when I'm hanging out on my home Wi-Fi.
But, once you taste success, you start getting greedy, right? So I thought, why stop at the living room? Why not make this drive accessible from anywhere in the world? To pull this off, I went through the whole ritual: first, I called up Comcast to get them to ditch the CGNAT (which was a headache, honestly), then I went into the router settings and killed the FW, disabled the 'WAN block' in the advanced options, and dove headfirst into the port forwarding configuration. I set up two rules—forwarding ports 444-446 and 136-140. For the external address, I double-checked everything by comparing what the router says with what comes up on my IP lookup site to make sure they match. As for the internal IP, I wasn't totally sure which one to use, so I tried both 192.168.0.1 and 192.168.0.10. Unfortunately, it's been a total bust—the drive is still invisible once I step outside my house. I can ping the external IP just fine, but those ports? They aren't opening for either of the internal addresses I picked.
I even gave customer support another ring to see if they were pulling my leg or if there was some issue on their end, but they just insisted everything looks perfect from where they're sitting.
Just to test things out, I've been using CX File Explorer on my phone—which, by the way, is an absolute lifesaver for local file management.
Does anyone have any bright ideas? Like, am I missing something obvious here??

Thanks in advance!

fadedorca66 said:Check if you're stuck behind CGNAT—it probably is.

🕺

Skimmed through this thread real quick, my bad 😁

Man, I wish it was just an issue with CGNAT...

While I'm sitting here waiting on AT&T to actually get back to me with some intel from the manufacturer, I decided to mess around a bit—you know how it is—by setting up an FTP server on my laptop and trying to forward the ports. It actually works, though there's a catch: it won't budge unless I shove my laptop's IP address straight into the DMZ in the router settings. That's what got me thinking, so I tried putting its internal address in the DMZ instead, but nope—the router immediately threw a fit and refused. It’s pretty clear the hardware just doesn't support what I'm trying to do, but honestly, let the manufacturer weigh in on that themselves.

On a side note, I stumbled onto something pretty weird while I was Googling stuff. I found this entire thread of ours copied verbatim over on a site like htc.com:
https://www.htc.com/showthread.php?t=1313633
I have no idea what kind of scheme this is. Are they just scraping entire forums to farm ad clicks or something?

shadowviper12 said:Man, I wish it was just an issue with CGNAT...

While I'm sitting here waiting on AT&T to actually get back to me with some intel from the manufacturer, I decided to mess around a bit—you know how it is—by setting up an FTP server on my laptop and trying to forward the ports. It actually works, though there's a catch: it won't budge unless I shove my laptop's IP address straight into the DMZ in the router settings. That's what got me thinking, so I tried putting its internal address in the DMZ instead, but nope—the router immediately threw a fit and refused. It’s pretty clear the hardware just doesn't support what I'm trying to do, but honestly, let the manufacturer weigh in on that themselves.

On a side note, I stumbled onto something pretty weird while I was Googling stuff. I found this entire thread of ours copied verbatim over on a site like htc.com:
https://www.htc.com/showthread.php?t=1313633
I have no idea what kind of scheme this is. Are they just scraping entire forums to farm ad clicks or something?

You can't be serious, 🤣

I am so sorry, but I guess that just doesn't make any sense whatsoever. 😛

😁 😁 you can tell I'm totally losing my mind here...

Sadly, I'm already working on a Plan B—trying to get Samba running on an Android 4.4.2 stick..

I suppose you could just forward port 21 from the WAN side directly to your laptop's IP address, which would get everything running smoothly without having to resort to putting the whole machine in the DMZ.

To be honest, I’ve always been a bit wary about putting anything in the DMZ—I can't quite put my finger on why, but it just doesn't feel like the smartest move to me! 🤔

https://www.htc.com/

The rest of the discussion is up there somewhere. 🤣

I tried messing around with port forwarding, but honestly, nothing clicked until I just threw the whole thing into the DMZ.

shadowviper12 said:I tried messing around with port forwarding, but honestly, nothing clicked until I just threw the whole thing into the DMZ.

Well, I suppose you might have messed things up a little bit back then, but honestly, it’s all pretty straightforward—about as simple as making a batch of homemade chili! 🤔

I was digging through some old threads on another forum and saw someone else run into this exact same headache—it didn't actually start working until they shoved everything into the DMZ. I didn't even touch any of my other settings, just did that one thing and suddenly, boom, it worked.

shadowviper12 said:I was digging through some old threads on another forum and saw someone else run into this exact same headache—it didn't actually start working until they shoved everything into the DMZ. I didn't even touch any of my other settings, just did that one thing and suddenly, boom, it worked.

Oh, I totally get that, and I suppose it would work if you just put it in the DMZ, but that really isn't the right way to handle things, I think. Not only is it a complete disaster from a security standpoint—it’s basically like walking around without any clothes on!—but you also run into the issue where you can't route different ports to different hosts if you go that route.

Yeah, I'm stuck being limited to just one host right now, which—let's be honest—is a total security nightmare. I'm gonna mess around a bit more to see if I can make port forwarding work, but man, I'm running out of ideas here. All I've found online is that it worked for one guy using the DMZ setting, and then another guy mentioned that sometimes you have to leave the external address as 0.0.0.0 in the port forwarding settings instead of typing in the actual IP... but every time I try that, the config just refuses to apply and throws an error in my face.

shadowviper12 said:Man, I wish it was just an issue with CGNAT...

While I'm sitting here waiting on AT&T to actually get back to me with some intel from the manufacturer, I decided to mess around a bit—you know how it is—by setting up an FTP server on my laptop and trying to forward the ports. It actually works, though there's a catch: it won't budge unless I shove my laptop's IP address straight into the DMZ in the router settings. That's what got me thinking, so I tried putting its internal address in the DMZ instead, but nope—the router immediately threw a fit and refused. It’s pretty clear the hardware just doesn't support what I'm trying to do, but honestly, let the manufacturer weigh in on that themselves.

On a side note, I stumbled onto something pretty weird while I was Googling stuff. I found this entire thread of ours copied verbatim over on a site like htc.com:
https://www.htc.com/showthread.php?t=1313633
I have no idea what kind of scheme this is. Are they just scraping entire forums to farm ad clicks or something?

If you had to resort to using the DMZ for a single device, then your port forwarding isn't set up correctly.

shadowviper12 said:Yeah, I'm stuck being limited to just one host right now, which—let's be honest—is a total security nightmare. I'm gonna mess around a bit more to see if I can make port forwarding work, but man, I'm running out of ideas here. All I've found online is that it worked for one guy using the DMZ setting, and then another guy mentioned that sometimes you have to leave the external address as 0.0.0.0 in the port forwarding settings instead of typing in the actual IP... but every time I try that, the config just refuses to apply and throws an error in my face.

When you're doing port forwarding, you don't input the external address; you use the internal one. You probably meant that, but you just phrased it wrong.

wiredcanyon94 said:If you had to resort to using the DMZ for a single device, then your port forwarding isn't set up correctly.

When you're doing port forwarding, you don't input the external address; you use the internal one. You probably meant that, but you just phrased it wrong.

Yeah, I guess there really isn't any point in bothering with an external address at all. I was just sitting here looking over my own settings to see how everything is configured on my end!

I was thinking about setting up some port forwarding on my Arris TG3482V, specifically for WAN TCP/UDP port 80 to point over to 192.168.1.10 via TCP/UDP, and I guess I'm just wondering if anyone has run into any hiccups with that configuration lately!

So, it looks like all the external traffic hitting port 80 is being redirected straight to the local IP port 80, I guess!

I was just looking through my settings and I think I might have run into a bit of a snag—it looks like I don't have an external IP address showing up at all! 👍

Nah, I’m not saying I was wrong—not even close.

Here’s what the Port Forwarding window looks like:

https://ibb.co/x6yFVMM

Man, oh man... now I have to go through the whole process again just to snap a screenshot and show you guys what happens when I try putting 0.0.0.0 in for the external address. It actually went through this time! It threw some weird error before, but apparently, it’s accepting zeros now. Honestly, I have no clue what I did differently this time around. Just pure luck, I guess.

Anyway, there’s the Port Forwarding config. If anything looks wonky to you guys, just let me know and I'll fix it easy.

I’ve been messing around with an Android stick lately—good news is it works fine once I plug my drive and mouse dongle into a USB hub and then into the stick. I still need to dig around for an Ethernet adapter to plug in and really test the stability. Bad news? This thing is running Android 4.2.2, so I’m pretty much stuck with whatever old apps actually work. 'Andsmb' is supposed to be compatible with this version of Android, but the whole thing just crashes the second I tap anything. Found another one that seems legit, but the free version is way too stripped down, so I’ll probably end up having to hunt for a third option or just bite the bullet and buy the Pro version.

shadowviper12 said:Nah, I’m not saying I was wrong—not even close.

Here’s what the Port Forwarding window looks like:

https://ibb.co/x6yFVMM

Man, oh man... now I have to go through the whole process again just to snap a screenshot and show you guys what happens when I try putting 0.0.0.0 in for the external address. It actually went through this time! It threw some weird error before, but apparently, it’s accepting zeros now. Honestly, I have no clue what I did differently this time around. Just pure luck, I guess.

Anyway, there’s the Port Forwarding config. If anything looks wonky to you guys, just let me know and I'll fix it easy.

I’ve been messing around with an Android stick lately—good news is it works fine once I plug my drive and mouse dongle into a USB hub and then into the stick. I still need to dig around for an Ethernet adapter to plug in and really test the stability. Bad news? This thing is running Android 4.2.2, so I’m pretty much stuck with whatever old apps actually work. 'Andsmb' is supposed to be compatible with this version of Android, but the whole thing just crashes the second I tap anything. Found another one that seems legit, but the free version is way too stripped down, so I’ll probably end up having to hunt for a third option or just bite the bullet and buy the Pro version.

Your port configuration is off. Those aren't the right ports for FTP. That's exactly why you had to resort to using the DMZ.

Kenneth Cruz67 said:I suppose you could just forward port 21 from the WAN side directly to your laptop's IP address, which would get everything running smoothly without having to resort to putting the whole machine in the DMZ.

To be honest, I’ve always been a bit wary about putting anything in the DMZ—I can't quite put my finger on why, but it just doesn't feel like the smartest move to me! 🤔

https://www.htc.com/

The rest of the discussion is up there somewhere. 🤣

wiredcanyon94 said:Your port configuration is off. Those aren't the right ports for FTP. That's exactly why you had to resort to using the DMZ.

If you find yourself needing to go a bit further, I guess you might also be able to redirect port 20 along with port 21! 👍

Look, the reason I set that specific port up was just because I configured my FTP server to run on it—nothing fancy. And honestly? It’s working perfectly fine when I'm just accessing it from within my local network.