Re: [PLUG] Linux server on Xfinity home network

[Victor via plug <plug@lists.phillylinux.org>]

Big agree with Frank on the equipment that ISP's give out being
terrible and separating devices. I don't have further experience to
offer advice with the Xfinity stuff though.

If you'd like to just statically assign the raspberry pi, look to the
"nmtui" command line utility. I'm assuming you're calling it
"Raspbian" by mistake as they switched to calling it Raspberry Pi OS
("raspios") a while back. The old methods of statically assigning
weren't working for me recently and the "nmtui" utility wasn't easy to
find in a sea of outdated advice on the matter when searching. If
youare using an older version of raspbian I don't have procedures to
help but some searching should turn up the config file to edit.

On Wed, Nov 6, 2024 at 12:45 PM Frank via plug
<plug@lists.phillylinux.org> wrote:
>
> The router/modem combos they give out are really bad.  I tried to use one briefly, but it didn't do much, and what it did do, it didn't do well.  I wouldn't be surprised if it just doesn't work.
>
>
> I ended up using my own router (and kept their modem), and I'm much happier now.  And even easier, I use one VLAN for my DHCP devices, and one VLAN for my static IP devices.  With a router that handles VLANs, not only do you not have to worry about the "reserved IP" situation any more, but you have a lot more intrinsic security, since most people wouldn't want DHCP devices like "smartphones"  or tablets or iOT gadgets on the same subnet with a server.
>
>
> - Frank
>
>
>
> On 11/6/24 12:05 PM, Adam Zion via plug wrote:
>
> Likely a stupid problem, but a search of the archives for "xfinity reserve IP" didn't yield any hits.
>
> The Xfinity router claims to be able to convert a DHCP address to a reserved IP by a click of a button. But, no. Even if I reserve the same IP that has been assigned to the server (wired ethernet connection, which shouldn't make a difference but just may, for especially stupid reasons), the rest of the network can't talk to the device. That's even after a reboot.
>
> So, three questions:
>
> Question the First: has anyone encountered + been able to solve it?
>
> Question the Second: might it be peculiar to linux hosts? Given that I don't have any Windows servers - ew - to test, it's tough to discern this for myself.
>
> Question the Third: given that it may be easier to assign this a static IP rather than relying on the vagaries of DHCP and name resolution via random queries, how does one correctly assign a static IP in Raspbian? It seems that what I've found assumes only IP4 or that someone wants to assign the IP via a graphical interface (this is a headless NAS).
>
> Thx,
> -Z
>
> --
> Lord* Adam Zion, MSIS
> Registered Linux User #471910
> http://www.adamzion.com
>
> * Yes, really
>
> ___________________________________________________________________________
> Philadelphia Linux Users Group         --        http://www.phillylinux.org
> Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
> General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug
>
> ___________________________________________________________________________
> Philadelphia Linux Users Group         --        http://www.phillylinux.org
> Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
> General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug
___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug