Up Next: Fixing my File Server

[overclockedmind]

After all, it doesn't need to be accessible from outside the LAN. Just my two cents, there.

[FourthWorld]

I also use T-Mobile 5G. Good value, but the Carrier-Grade NAT that drives their network prevents me from using my lovely 2U server for anything outside my LAN.

I've become okay with this, given how cheap VPSes have become.

Exactly. There's a workaround; ya just gotta find it, and be ready for it.
In that regard, do you know if it will accept DHCP with a static IP, within its subnet? I'm thinking 192.168.x.250 for the file server, but it may throw a fit if I declare a static IP even within its subnet. Ideas at all?

Given the network limitations, TMobile has limited their device options. I just added my own router for LAN, and everything inside connects to that. Flexible, simple.

[overclockedmind]

I also use T-Mobile 5G. Good value, but the Carrier-Grade NAT that drives their network prevents me from using my lovely 2U server for anything outside my LAN.

I've become okay with this, given how cheap VPSes have become.

Exactly. There's a workaround; ya just gotta find it, and be ready for it.
In that regard, do you know if it will accept DHCP with a static IP, within its subnet? I'm thinking 192.168.x.250 for the file server, but it may throw a fit if I declare a static IP even within its subnet. Ideas at all?

Given the network limitations, TMobile has limited their device options. I just added my own router for LAN, and everything inside connects to that. Flexible, simple.

Yeah, that's on the to-do list.

[overclockedmind]

One last-ditch effort: I know macOS Monterey can mount NTFS shares with a simple alteration from read-only to read-write.

Only trouble is, I've Googled the heck out of it, and 10,000 results from Some Software for Newer macOS versions infests the information.

Anyone? Something about NTFS and rw instead of ro and... fstab, I think?

Right now, I copied the entire lot of the server's share to an external hard drive, connected to my primary machine. That works, but I'd rather have access to it from within the LAN period, and I can just "ask Monterey" what its IP is, if nothing else.

[richmond62]

Just look for 'Mounty.app' for MacOS: works for NTFS volumes out of the box.

[overclockedmind]

"Hey Macbook, what's your IP address?"

[tperry2x]

One last-ditch effort: I know macOS Monterey can mount NTFS shares with a simple alteration from read-only to read-write.
Only trouble is, I've Googled the heck out of it, and 10,000 results from Some Software for Newer macOS versions infests the information.
Anyone? Something about NTFS and rw instead of ro and... fstab, I think?

As default, MacOS does not create the fstab file, but it will obey & use it if it's there. You'd have to create it manually (and format it properly) which I can't quite remember the gist of
Or, I might misunderstand - do you mean you want to make drives mount r/w in Linux?

[overclockedmind]

One last-ditch effort: I know macOS Monterey can mount NTFS shares with a simple alteration from read-only to read-write.
Only trouble is, I've Googled the heck out of it, and 10,000 results from Some Software for Newer macOS versions infests the information.
Anyone? Something about NTFS and rw instead of ro and... fstab, I think?

As default, MacOS does not create the fstab file, but it will obey & use it if it's there. You'd have to create it manually (and format it properly) which I can't quite remember the gist of
Or, I might misunderstand - do you mean you want to make drives mount r/w in Linux?

I was looking for Monterey, but in the future that info might come in handy. Thanks

[overclockedmind]

In fact, lemme just fire up the MBA with LM on it... to be continued!

[overclockedmind]

I also use T-Mobile 5G. Good value, but the Carrier-Grade NAT that drives their network prevents me from using my lovely 2U server for anything outside my LAN.

I've become okay with this, given how cheap VPSes have become.

I'm considering routers now, to put between their ... service box, andmy LAN, so I can have my LAN back. Any recommendations?

Doesn't need to be "carrier grade" or "gamer." Does need gigabit Ethernet ports and WiFi 6, at least, ability to run OpenWRT, et al a bonus. Not needing a reboot once a day would also be a bonus (no, I don't have to do that with the T-Mobile thing... yet, anythow.

Also... anyone (perhaps FourthWorld) want to tell me whether I can turn the wireless off on T-Mobile's box? I'd ask them, but I'd be on the phone for two hours...

[overclockedmind]

So, I did get the file server to insist that is was 192.168.12.2, with a normal ping response.

The trouble is, how long does that last before there's an IP address conflict, et cetera?

Just glad to see two machines ping each other properly in a LAN (gawd, what misery.)

Thus, I'll still be adding another router to this equation.

[overclockedmind]

So, I did get the file server to insist that is was 192.168.12.2, with a normal ping response.

The trouble is, how long does that last before there's an IP address conflict, et cetera?

Just glad to see two machines ping each other properly in a LAN (gawd, what misery.)

Thus, I'll still be adding another router to this equation.

Seems like specifying DNS servers worked around them adding ".lan" to numerical addresses.

If I tried to ping a v4 IP address, it would treat it as a hostname (totally broken) and add ".lan" to a numerical address.

Some thought required. The seamless solution, of course, is to add another router, We'll let the current solution "percolate" awhile.

[FourthWorld]

So, I did get the file server to insist that is was 192.168.12.2, with a normal ping response.

The trouble is, how long does that last before there's an IP address conflict, et cetera?

Is this LAN-only?

Here I just used the DHCP Address Registration settings in my router to assign a fixed IP to my LAN server, no DNS needed.

If it needs to be reachable from the outside that's a much more complex issue requiring an external tunnelling service, due to T-Mobile's CGN.

[overclockedmind]

So, I did get the file server to insist that is was 192.168.12.2, with a normal ping response.

The trouble is, how long does that last before there's an IP address conflict, et cetera?

Is this LAN-only?

Here I just used the DHCP Address Registration settings in my router to assign a fixed IP to my LAN server, no DNS needed.

If it needs to be reachable from the outside that's a much more complex issue requiring an external tunnelling service, due to T-Mobile's CGN.

Yep, LAN-only.