What is required to migrate from /etc/hosts to DHCP
Long ago (openSUSE 6.3?) when I had only one machine and an analog modem, I set up /etc/hosts to map my IP address; as time went on I added a router, a network printer, an OS-X machine, etc., but my network was small enough that I could manage the devices with /etc/hosts. Currently I have satellite IP routed through a NetGear WiFi router, in which I have assigned the static addresses in my /etc/hosts file, but I want to migrate to the StarLink system that I recently bought. Unfortunately, the StarLink system's built-in router is a Black Box :-( that only supports devices via DHCP. (It is already handling a WiFi laptop and several smart phones; the legacy devices on the NetGear router use an Ethernet network.) My question is, do I just have to use YaST LAN to switch my network setting from Static to DHCP, or are there other changes required? (Both routers use the same 192.168.x.x address range, so it seems to me that just moving the Ethernet cable from one router to the other without assigning a new address ought to work, but there is no way to talk to the StarLink router if there is an address collision with devices it has already assigned.) My /etc/hosts currently looks like this: | wd=~ | $ cat /etc/hosts | # | # hosts This file describes a number of hostname-to-address | # mappings for the TCP/IP subsystem. It is mostly | # used at boot time, when no name servers are running. | # On small systems, this file can be used instead of a | # "named" name server. | # Syntax: | # | # IPv4 Address Fully Qualified Hostname Short Hostnames | #------------- ------------------------ ------------------- | 127.0.0.1 localhost | # | 192.168.1.1 grey.sixys.site grey router <== NetGear | 192.168.1.2 pinto.sixys.site pinto desktop1 | 192.168.1.3 philips.sixys.site philips TV | 192.168.1.4 chestnut.sixys.site chestnut desktop2 | 192.168.1.5 black.sixys.site black windows | 192.168.1.6 charcoal.sixys.site charcoal dell | #92.168.1.7 unused | #92.168.1.8 unused | 192.168.1.9 palomino.sixys.site palomino server | 192.168.1.10 buckskin.sixys.site buckskin printer | #92.168.1.11 unused | 192.168.1.12 chrome.sixys.site chrome laptop1 | 192.168.1.13 pinto-foal.sixys.site pinto-foal UPS | 192.168.1.14 toreador.sixys.site toreador laptop2 | # | 192.168.100.1 blueroan.sixys.site blueroan downlink <== ViaSat | # | #============================================================ | # IPv6 Address Hostnames | #------------- --------------------------------------------- | ::1 localhost ipv6-localhost ipv6-loopback | | fe00::0 ipv6-localnet | | ff00::0 ipv6-mcastprefix | ff02::1 ipv6-allnodes | ff02::2 ipv6-allrouters | ff02::3 ipv6-allhosts | # | #============================================================ | # DNS Servers: | # 192.168.1.1 | 99.197.99.99 | 99.196.99.99 | #============================================================ | rc=0 | @01:34:39 leslie@pinto Leslie -- Platform: Linux Distribution: openSUSE Leap 15.6 - x86_64
The subject sounds like apples vs. oranges. On 10.08.2024 09:54, J Leslie Turriff via openSUSE Users wrote:
Long ago (openSUSE 6.3?) when I had only one machine and an analog modem, I set up /etc/hosts to map my IP address; as time went on I added a router, a network printer, an OS-X machine, etc., but my network was small enough that I could manage the devices with /etc/hosts. Currently I have satellite IP routed through a NetGear WiFi router, in which I have assigned the static addresses in my /etc/hosts file, but I want to migrate to the StarLink system that I recently bought. Unfortunately, the StarLink system's built-in router is a Black Box :-( that only supports devices via DHCP.
I do not understand it. Do you mean that if you statically configure the same address (and other parameters) that would have been received via DHCP it will not work? Have you tried it?
(It is already handling a WiFi laptop and several smart phones; the legacy devices on the NetGear router use an Ethernet network.)
My question is, do I just have to use YaST LAN to switch my network setting from Static to DHCP, or are there other changes required? (Both routers use the same 192.168.x.x address range, so it seems to me that just moving the Ethernet cable from one router to the other without assigning a new address ought to work, but there is no way to talk to the StarLink router if there is an address collision with devices it has already assigned.)
My /etc/hosts currently looks like this:
| wd=~ | $ cat /etc/hosts | # | # hosts This file describes a number of hostname-to-address | # mappings for the TCP/IP subsystem. It is mostly | # used at boot time, when no name servers are running. | # On small systems, this file can be used instead of a | # "named" name server. | # Syntax: | # | # IPv4 Address Fully Qualified Hostname Short Hostnames | #------------- ------------------------ ------------------- | 127.0.0.1 localhost | # | 192.168.1.1 grey.sixys.site grey router <== NetGear | 192.168.1.2 pinto.sixys.site pinto desktop1 | 192.168.1.3 philips.sixys.site philips TV | 192.168.1.4 chestnut.sixys.site chestnut desktop2 | 192.168.1.5 black.sixys.site black windows | 192.168.1.6 charcoal.sixys.site charcoal dell | #92.168.1.7 unused | #92.168.1.8 unused | 192.168.1.9 palomino.sixys.site palomino server | 192.168.1.10 buckskin.sixys.site buckskin printer | #92.168.1.11 unused | 192.168.1.12 chrome.sixys.site chrome laptop1 | 192.168.1.13 pinto-foal.sixys.site pinto-foal UPS | 192.168.1.14 toreador.sixys.site toreador laptop2 | # | 192.168.100.1 blueroan.sixys.site blueroan downlink <== ViaSat | # | #============================================================ | # IPv6 Address Hostnames | #------------- --------------------------------------------- | ::1 localhost ipv6-localhost ipv6-loopback | | fe00::0 ipv6-localnet | | ff00::0 ipv6-mcastprefix | ff02::1 ipv6-allnodes | ff02::2 ipv6-allrouters | ff02::3 ipv6-allhosts | # | #============================================================ | # DNS Servers: | # 192.168.1.1 | 99.197.99.99 | 99.196.99.99 | #============================================================ | rc=0 | @01:34:39 leslie@pinto
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.6 - x86_64
On 2024-08-10 02:11:51 Andrei Borzenkov wrote:
On 10.08.2024 09:54, J Leslie Turriff via openSUSE Users wrote:
Long ago (openSUSE 6.3?) when I had only one machine and an analog modem, I set up /etc/hosts to map my IP address; as time went on I added a router, a network printer, an OS-X machine, etc., but my network was small enough that I could manage the devices with /etc/hosts. Currently I have satellite IP routed through a NetGear WiFi router, in which I have assigned the static addresses in my /etc/hosts file, but I want to migrate to the StarLink system that I recently bought. Unfortunately, the StarLink system's built-in router is a Black Box :-( that only supports devices via DHCP.
I do not understand it. Do you mean that if you statically configure the same address (and other parameters) that would have been received via DHCP it will not work? Have you tried it?
I haven't tried anything yet. I would like to keep the same IP addresses as the NetGear router has configured, but the StarLink router is a black box; no user configuration is possible. Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64
On 8/14/24 6:13 PM, J Leslie Turriff via openSUSE Users wrote:
I haven't tried anything yet. I would like to keep the same IP addresses as the NetGear router has configured, but the StarLink router is a black box; no user configuration is possible.
Just a word of experience. When switching static to DHCP, just start fresh. You can configure an IP to hand out based on MAC address of the NIC - use that for special equipment, router, box you want at fixed IP, etc.. Otherwise, just configure DHCP correctly and let it do its job. It should hand out the same IP to devices by renewing leases each time it is required. -- David C. Rankin, J.D.,P.E.
From: J Leslie Turriff via openSUSE Users <users@lists.opensuse.org> Date: Wed, 14 Aug 2024 18:13:02 -0500 I haven't tried anything yet. I would like to keep the same IP addresses as the NetGear router has configured, but the StarLink router is a black box; no user configuration is possible. Leslie What makes you sure of that? Have you tried (e.g.) http://192.168.1.1/ to see what answers? The reason I asked is that when we got AT&T fiber two years ago, and I asked about port forwarding, the sales rep said, "No, you can't do that, you have to configure it through the phone app." The phone app turned out to be useless (she was right the you couldn't configure port forwarding there -- or anything else) but I found a full-featured Web interface at http://192.168.1.254/ that gives me everything I need. ================ Maybe I should have asked a simpler question: If DHCP gets a request from an unknown machine on the local network, does it consult the /etc/hosts file in that machine and try to provide that address? Leslie No; DHCP uses only its own internal configuration database. But, as David said, you can configure it to assign specific addresses to hosts permanently based on their MAC (Ethernet hardware) address. You just have to find the right configuraton page. I find it hard to believe that the Starlink box doesn't have one. Somewhere. -- Bob
On 2024-08-15 01:13, J Leslie Turriff via openSUSE Users wrote:
On 2024-08-10 02:11:51 Andrei Borzenkov wrote:
I haven't tried anything yet. I would like to keep the same IP addresses as the NetGear router has configured, but the StarLink router is a black box; no user configuration is possible.
That is impossible. There must always be a configuration method, even if it is limited. It could be via a smartphone app. Or it could be via an external IP living at the ISP, say http://starlink.com/router (I just made it up). This second method is what my ISP does. But accessing that method provides a method to get the router password and disable the ISP page, and then access it locally at http://192.168.1.1 And then, you always have the option to use the DHCP service AND your own static IP definitions. You only have to use static addresses outside of the router DHCP range. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 2024-08-10 02:11:51 Andrei Borzenkov wrote:
The subject sounds like apples vs. oranges.
On 10.08.2024 09:54, J Leslie Turriff via openSUSE Users wrote:
Long ago (openSUSE 6.3?) when I had only one machine and an analog modem, I set up /etc/hosts to map my IP address; as time went on I added a router, a network printer, an OS-X machine, etc., but my network was small enough that I could manage the devices with /etc/hosts. Currently I have satellite IP routed through a NetGear WiFi router, in which I have assigned the static addresses in my /etc/hosts file, but I want to migrate to the StarLink system that I recently bought. Unfortunately, the StarLink system's built-in router is a Black Box :-( that only supports devices via DHCP.
I do not understand it. Do you mean that if you statically configure the same address (and other parameters) that would have been received via DHCP it will not work? Have you tried it?
Maybe I should have asked a simpler question: If DHCP gets a request from an unknown machine on the local network, does it consult the /etc/hosts file in that machine and try to provide that address? Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64
On 15.08.2024 02:26, J Leslie Turriff via openSUSE Users wrote:
On 2024-08-10 02:11:51 Andrei Borzenkov wrote:
The subject sounds like apples vs. oranges.
On 10.08.2024 09:54, J Leslie Turriff via openSUSE Users wrote:
Long ago (openSUSE 6.3?) when I had only one machine and an analog modem, I set up /etc/hosts to map my IP address; as time went on I added a router, a network printer, an OS-X machine, etc., but my network was small enough that I could manage the devices with /etc/hosts. Currently I have satellite IP routed through a NetGear WiFi router, in which I have assigned the static addresses in my /etc/hosts file, but I want to migrate to the StarLink system that I recently bought. Unfortunately, the StarLink system's built-in router is a Black Box :-( that only supports devices via DHCP.
I do not understand it. Do you mean that if you statically configure the same address (and other parameters) that would have been received via DHCP it will not work? Have you tried it?
Maybe I should have asked a simpler question: If DHCP gets a request from an unknown machine on the local network, does it consult the /etc/hosts file in that machine and try to provide that address?
No, it does not.
On Wed, 14 Aug 2024 18:26:40 -0500 J Leslie Turriff via openSUSE Users <users@lists.opensuse.org> wrote:
On 2024-08-10 02:11:51 Andrei Borzenkov wrote:
The subject sounds like apples vs. oranges.
On 10.08.2024 09:54, J Leslie Turriff via openSUSE Users wrote:
Long ago (openSUSE 6.3?) when I had only one machine and an analog modem, I set up /etc/hosts to map my IP address; as time went on I added a router, a network printer, an OS-X machine, etc., but my network was small enough that I could manage the devices with /etc/hosts. Currently I have satellite IP routed through a NetGear WiFi router, in which I have assigned the static addresses in my /etc/hosts file, but I want to migrate to the StarLink system that I recently bought. Unfortunately, the StarLink system's built-in router is a Black Box :-( that only supports devices via DHCP.
I do not understand it. Do you mean that if you statically configure the same address (and other parameters) that would have been received via DHCP it will not work? Have you tried it?
Maybe I should have asked a simpler question: If DHCP gets a request from an unknown machine on the local network, does it consult the /etc/hosts file in that machine and try to provide that address?
No, a DHCP server follows rules based on its own configuration. I find it difficult to believe you can't change the Starlink network, but I'm sure you CAN change the Netgear's network. So set up your machines/devices to get their network address by DHCP from the Netgear, then change its configuration so it uses a different network. e.g. 192.168.2.0. Then all your machines will automatically switch to the new network.
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64
On 8/9/24 23:54, J Leslie Turriff via openSUSE Users wrote:
Long ago (openSUSE 6.3?) when I had only one machine and an analog modem, I set up /etc/hosts to map my IP address; as time went on I added a router, a network printer, an OS-X machine, etc., but my network was small enough that I could manage the devices with /etc/hosts. Currently I have satellite IP routed through a NetGear WiFi router, in which I have assigned the static addresses in my /etc/hosts file, but I want to migrate to the StarLink system that I recently bought. Unfortunately, the StarLink system's built-in router is a Black Box :-( that only supports devices via DHCP. (It is already handling a WiFi laptop and several smart phones; the legacy devices on the NetGear router use an Ethernet network.)
My question is, do I just have to use YaST LAN to switch my network setting from Static to DHCP, or are there other changes required? (Both routers use the same 192.168.x.x address range, so it seems to me that just moving the Ethernet cable from one router to the other without assigning a new address ought to work, but there is no way to talk to the StarLink router if there is an address collision with devices it has already assigned.)
My /etc/hosts currently looks like this:
If I were you I'd just plug the StarLink directly in to my NetGear router's WAN interface and let it worry about DHCP. You could then keep everything on the LAN side of the router the same. I wouldn't trust StarLink's firewall anyway, use the one in your NetGear to protect yourself. Be sure to let us know how the StarLink connection works out for you! Regards, Lew
On 2024-08-10 02:53:12 Lew Wolfgang wrote:
On 8/9/24 23:54, J Leslie Turriff via openSUSE Users wrote:
Long ago (openSUSE 6.3?) when I had only one machine and an analog modem, I set up /etc/hosts to map my IP address; as time went on I added a router, a network printer, an OS-X machine, etc., but my network was small enough that I could manage the devices with /etc/hosts. Currently I have satellite IP routed through a NetGear WiFi router, in which I have assigned the static addresses in my /etc/hosts file, but I want to migrate to the StarLink system that I recently bought. Unfortunately, the StarLink system's built-in router is a Black Box :-( that only supports devices via DHCP. (It is already handling a WiFi laptop and several smart phones; the legacy devices on the NetGear router use an Ethernet network.)
My question is, do I just have to use YaST LAN to switch my network setting from Static to DHCP, or are there other changes required? (Both routers use the same 192.168.x.x address range, so it seems to me that just moving the Ethernet cable from one router to the other without assigning a new address ought to work, but there is no way to talk to the StarLink router if there is an address collision with devices it has already assigned.)
My /etc/hosts currently looks like this:
If I were you I'd just plug the StarLink directly in to my NetGear router's WAN interface and let it worry about DHCP. You could then keep everything on the LAN side of the router the same. I wouldn't trust StarLink's firewall anyway, use the one in your NetGear to protect yourself.
Be sure to let us know how the StarLink connection works out for you!
Regards, Lew
I didn't think of that. It makes sense; I'll give it a try. The only trick would be to turn off the NetGear radio, because both routers use the same 192.168.1.0 range. Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64
On 2024-08-10 02:53:12 Lew Wolfgang wrote:
If I were you I'd just plug the StarLink directly in to my NetGear router's WAN interface and let it worry about DHCP. You could then keep everything on the LAN side of the router the same. I wouldn't trust StarLink's firewall anyway, use the one in your NetGear to protect yourself.
Be sure to let us know how the StarLink connection works out for you!
Regards, Lew
Actually, I don't think this would work, since both routers use the same 192.168.1.0 range and I can't change the range in the StarLink device. :-( Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64
J Leslie Turriff composed on 2024-08-14 18:31 (UTC-0500):
Actually, I don't think this would work, since both routers use the same 192.168.1.0 range and I can't change the range in the StarLink device. :-(
192.168.0.0 is its default. Switch it as you please. e.g. 192.168.0.0 or 192.168.7.0. Your static IP hosts will require conforming if you do. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 2024-08-15 01:31, J Leslie Turriff via openSUSE Users wrote:
On 2024-08-10 02:53:12 Lew Wolfgang wrote:
If I were you I'd just plug the StarLink directly in to my NetGear router's WAN interface and let it worry about DHCP. You could then keep everything on the LAN side of the router the same. I wouldn't trust StarLink's firewall anyway, use the one in your NetGear to protect yourself.
Be sure to let us know how the StarLink connection works out for you!
Regards, Lew
Actually, I don't think this would work, since both routers use the same 192.168.1.0 range and I can't change the range in the StarLink device. :-(
There is a regulation here that says that all ISP routers must have a setting to put in bridge mode. Ie, to do nothing at all, and pass it all to a customer's own router. You must try and see what's on http 192.168.1.1. It is impossible there is no configuration at all. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 2024-08-17 00:26, David C. Rankin wrote:
On 8/16/24 4:20 AM, Carlos E. R. wrote:
You must try and see what's on http 192.168.1.1. It is impossible there is no configuration at all.
Recall, this is a system from the genius that showed us how to turn $44B into $27B overnight -- you never know.
Huh? I must be missing something... I'm going to bed, almost 3AM here. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 8/16/24 02:20, Carlos E. R. wrote:
On 2024-08-15 01:31, J Leslie Turriff via openSUSE Users wrote:
On 2024-08-10 02:53:12 Lew Wolfgang wrote:
If I were you I'd just plug the StarLink directly in to my NetGear router's WAN interface and let it worry about DHCP. You could then keep everything on the LAN side of the router the same. I wouldn't trust StarLink's firewall anyway, use the one in your NetGear to protect yourself.
Be sure to let us know how the StarLink connection works out for you!
Actually, I don't think this would work, since both routers use the same 192.168.1.0 range and I can't change the range in the StarLink device. :-(
But the StarLink hub would have a different SSID than your NetGear. Your WiFi devices would continue to connect as before to the NetGear, correct? But this does bring up an interesting question: can a router have the same non-routeable subnet on both its LAN and WAN interfaces? Would the router have a fit and chase its tail forever?
There is a regulation here that says that all ISP routers must have a setting to put in bridge mode. Ie, to do nothing at all, and pass it all to a customer's own router.
My cable-modem runs in bridge mode by default. But does a StarLink endpoint act like a bridged cable modem or as a router? I know a Linux Guru who uses StarLink, I'll have to ask her about it.
You must try and see what's on http 192.168.1.1. It is impossible there is no configuration at all.
Good advice. But would running nmap on the LAN side of a StarLink endpoint get you in trouble with Elon? I have a feeling that my ISP would get testy if I scanned through my modem into their subnet feeding me. Regards, Lew
On Aug 17, 2024, at 3:32 PM, Lew Wolfgang <wolfgang@sweet-haven.com> wrote:
On 8/16/24 02:20, Carlos E. R. wrote:
On 2024-08-15 01:31, J Leslie Turriff via openSUSE Users wrote: On 2024-08-10 02:53:12 Lew Wolfgang wrote:
If I were you I'd just plug the StarLink directly in to my NetGear router's WAN interface and let it worry about DHCP. You could then keep everything on the LAN side of the router the same. I wouldn't trust StarLink's firewall anyway, use the one in your NetGear to protect yourself.
Be sure to let us know how the StarLink connection works out for you!
Actually, I don't think this would work, since both routers use the same 192.168.1.0 range and I can't change the range in the StarLink device. :-(
I thought of suggesting this but it won’t work. With the Netgear WAN interface plugged into the Starlink LAN interface both interfaces would be in the same subnet and make routing impossible because both would claim priority over the subnet. Ken Schneider
On 2024-08-17 21:31, Lew Wolfgang wrote:
On 8/16/24 02:20, Carlos E. R. wrote:
On 2024-08-15 01:31, J Leslie Turriff via openSUSE Users wrote:
On 2024-08-10 02:53:12 Lew Wolfgang wrote:
Actually, I don't think this would work, since both routers use the same 192.168.1.0 range and I can't change the range in the StarLink device. :-(
But the StarLink hub would have a different SSID than your NetGear. Your WiFi devices would continue to connect as before to the NetGear, correct?
But this does bring up an interesting question: can a router have the same non-routeable subnet on both its LAN and WAN interfaces? Would the router have a fit and chase its tail forever?
Yes, it would have a fit. Or the configuration form would tell you "no". Theoretically, you could design a router that would allow to have the same IP range on each separate interface, but it would have to do clever tricks to do the routing. For instance, this is doable, using two routers: 192.168.1.* ←[router_1]→ 192.168.2.* ←[router_2]→ 192.168.1.* LAN 1 LAN 2 LAN 3 However, someone pinging 192.168.1.10 on the left of router_1 would only reach that machine on LAN_1, never a machine on LAN_2. So it would not work. It would be interesting to do and see what errors it spits out.
There is a regulation here that says that all ISP routers must have a setting to put in bridge mode. Ie, to do nothing at all, and pass it all to a customer's own router.
My cable-modem runs in bridge mode by default. But does a StarLink endpoint act like a bridged cable modem or as a router? I know a Linux Guru who uses StarLink, I'll have to ask her about it.
You must try and see what's on http 192.168.1.1. It is impossible there is no configuration at all.
Good advice. But would running nmap on the LAN side of a StarLink endpoint get you in trouble with Elon? I have a feeling that my ISP would get testy if I scanned through my modem into their subnet feeding me.
You can do nmap on your side of your router, it is your property. Outside of your LAN, that's a different matter. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 2024-08-16 04:20:59 Carlos E. R. wrote:
On 2024-08-15 01:31, J Leslie Turriff via openSUSE Users wrote:
On 2024-08-10 02:53:12 Lew Wolfgang wrote:
If I were you I'd just plug the StarLink directly in to my NetGear router's WAN interface and let it worry about DHCP. You could then keep everything on the LAN side of the router the same. I wouldn't trust StarLink's firewall anyway, use the one in your NetGear to protect yourself.
Be sure to let us know how the StarLink connection works out for you!
Regards, Lew
Actually, I don't think this would work, since both routers use the same 192.168.1.0 range and I can't change the range in the StarLink device. :-(
There is a regulation here that says that all ISP routers must have a setting to put in bridge mode. Ie, to do nothing at all, and pass it all to a customer's own router.
You must try and see what's on http 192.168.1.1. It is impossible there is no configuration at all.
Yes. Well, it turns out that router configuration can only be accomplished via the Starlink smartPhone app. (!) and at the moment, the smartPhone app is telling me, "Router unreachable" and "Your Starlink router is unreachable. Make sure your router is powered on, and that your device is connected to your Starlink WiFi network." even though two laptops and my smartPhone can use it to interact with the internet. I will have to "schedule an outage" :-) with my brother to reboot it and hopefully straighten it out before I can continue. Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64
From: J Leslie Turriff via openSUSE Users <users@lists.opensuse.org> Date: Sat, 10 Aug 2024 01:54:52 -0500 . . . My question is, do I just have to use YaST LAN to switch my network setting from Static to DHCP, or are there other changes required? . . . Leslie The first thing to bear in mind is that /etc/hosts and DHCP are solving different problems: DHCP tells a computer "What address do I use?" and /etc/hosts tells it "What address is system X at?" As long as those answers are consistent for all values of X, on all systems, you can use both. (And the alternative for "What address is system X at?" would be something like DNS, which also involves keeping the answers consistent; there are advantages to switching to DNS, but probably not for a network the size of yours.) But what Lew says about Starlink vs. Netgear is very cogent. Decide what you want for your network topology first, and whether you really need DHCP, and which system should provide it; normally, you want exactly one DHCP server! Then, if you have to go the DHCP route, you should be able to get the DHCP server to assign fixed addresses based on the MAC (Ethernet interface hardware) address. These have to be outside the DHCP "pool" range, so you will probably have to go through and assign new fixed /etc/hosts addresses (which, I can attest, is a pain in the butt). -- Bob Rogers
On 8/10/24 1:54 AM, J Leslie Turriff via openSUSE Users wrote:
My question is, do I just have to use YaST LAN to switch my network setting from Static to DHCP, or are there other changes required?
In addition to other answers: 1) Make sure you only have 1 device handing out addresses via DHCP. You don't want both the starlink and some other device thinking they are the DHCP server. 2) You set each "Interface" in Yast to request an address via DHCP. So if you have both a wireless card and a wired-nic, you configure each in Yast (you can even configure each differently) 3) /etc/host is for "Name Resolution". You simply want to ensure you have defined localhost and your hostname there. Remove all other address that will now get an address via DHCP from the startlink box. A current /etc/host for use with DHCP (for my laptop with TW hostname: wizard domain: 3111skyline.com) can look similar to: #<snip> # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname # #127.0.0.1 localhost localhost.localdomain #::1 localhost localhost.localdomain ipv6-localhost ipv6-loopback 127.0.0.1 wizard.3111skyline.com localhost wizard ::1 wizard.3111skyline.com localhost ipv6-localhost ipv6-loopback wizard # special IPv6 addresses fe00::0 ipv6-localnet ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts Your /etc/hosts sets the "domain.tld" portion of your hostname. 4) Set your hostname without the domain in /etc/hostname. You can do that has root with, e.g. (for my laptop example) # hostname wizard # echo wizard > /etc/hostname or set it in Yast. 5) Now confirm your local hostname resolution is working properly, e.g. $ hostname wizard $ hostname -f wizard.3111skyline.com 6) Now when you obtain a DHCP address, it can (if it does) get a proper hostname for your device so it can do proper name resolution. Personally, I never let any box do DHCP on my LAN. I just have one box that runs 24/7 act as a server running Bind DNS (named) and dhcp with dhcp providing dynamic updates to named. That way addresses and name resolution are always handled by a Linux box on the LAN and it doesn't matter what device I plug in -- so long as its DHCP is turned OFF. dnsmask offers a simpler solution than Bind -- it's really just what you learned first. I've read no reviews of starlink, but it is another item I would be reluctant to trust. Worth scouring tech reviews to see if there is anything to be wary of -- other than the nut at the head of the company... Hopefully some of this help. You can put your system together in many ways, and it's totally up to you. In the end all you care about is that each device gets an IP and that name resolution works so each device can find all others on your LAN. (and hopefully the DHCP server is smart enough to handle stale leases and reuse the same address for the same device MAC each time it hands out an address -- that's just something you will have to monitor) -- David C. Rankin, J.D.,P.E.
On 8/10/24 1:54 AM, J Leslie Turriff via openSUSE Users wrote:
but I want to migrate to the StarLink system
Also, be wary about traffic on that network. I just had my first intrusion attempt from Starlink a day or so ago: The IP 129.222.103.39 has just been banned by Fail2Ban after 3 attempts against dovecot. Here is more information about 129.222.103.39 : # # ARIN WHOIS data and services are subject to the Terms of Use # available at: https://www.arin.net/resources/registry/whois/tou/ # # If you see inaccuracies in the results, please report at # https://www.arin.net/resources/registry/whois/inaccuracy_reporting/ # # Copyright 1997-2024, American Registry for Internet Numbers, Ltd. # # start NetRange: 129.222.0.0 - 129.222.255.255 CIDR: 129.222.0.0/16 NetName: SPACEX-STARLINK-IPV4 NetHandle: NET-129-222-0-0-1 Parent: NET129 (NET-129-0-0-0-0) NetType: Direct Allocation OriginAS: AS14593 Organization: SpaceX Services, Inc. (SS-2296) RegDate: 2021-12-06 Updated: 2021-12-07 Ref: https://rdap.arin.net/registry/ip/129.222.0.0 <snip> -- David C. Rankin, J.D.,P.E.
participants (9)
-
Andrei Borzenkov -
Bob Rogers -
Carlos E. R. -
Dave Howorth -
David C. Rankin -
Felix Miata -
J Leslie Turriff -
kschneider bout-tyme.net -
Lew Wolfgang