On Sat, Jul 29, 2023 at 04:34:17AM +0000, Philipp Buehler wrote: > Moin Chris, > > Am 29.07.2023 04:17 schrieb Chris Bennett: > > The network is 108.181.26.176/28. > > > > Right now,the first IP is 108.181.26.178 and the last regular address is > > 108.181.26.190, which might be wrong. I'm too tired to read any more > > man pages or web pages. I needed more than 2hrs of sleep. > > I'm super worn out, so forgive my mistakes. > > > > Any help appreciated. I don't want the next syspatch reboot to fail. > > To save mindboggling counting of 'f' or similar, just write this to > /etc/hostname.em1 > inet 108.181.26.178/28 > The ifconfig called from netstart will figure it out ;-) That's a headups > for everybody, so cc misc@. >
Yes, there was a big delay when he put in one f too few. Besides changing IP ranges, they also just started pushing a single IP address that serves as everything, but also a different checkbox for the same thing for Linux only. I know essentially nothing about Linux besides the fact that I quickly tried several, but I didn't like them. I then ran into something mentioning OpenBSD. After reading the website, I saw that OpenBSD was and has been an excellent choice. No regrets. I already know from experience that if I asked them for any details about that networking change, I would NOT get a useful answer. After I got to multiple days, my goal had to be getting able to ssh in and start fixing things. Security through obscurity does not work. So I think it is well worth it to show and get help. I am so tired right now, that my Dad had a problem with sound using YouTube on a Firestick. I couldn't tell him even the simplest step, so I just had him reboot it. I'm going to kill everything that has outside access, get a good night's sleep and then change every password for inside stuff and all emails. Then I'm going to carefully read every man page, etc. until I understand everything fully. Now is the right time for this. Until recently, I only had a laptop stuck at 6.6 and a lousy phone hotspot or an even crappier access to almost useless wifi in places like libraries. Two used computers and a really great phone hotspot make everything good now. Thank you very much. > The current ifconfig em1 shows a bit wild setup for 108.181.26.179; but that > > is likely unintended and the wrong mask/bc will be gone with the above > setting. > > The route output shows several hosts in 108.136/108.137 ranges where there > is no corresponding setup given. > > But to reach the system via 108.181.26.178 again, this looks sound. > > HTH, > -- > pb > > PS: > tyo# cat /etc/hostname.vlan1 > vlandev vio0 > inet 108.181.26.178/28 > tyo# sh /etc/netstart vlan1 > tyo# ifconfig vlan1 > vlan1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > lladdr fe:e1:bb:6e:63:36 > index 7 priority 0 llprio 3 > encap: vnetid none parent vio0 txprio packet rxprio outer > groups: vlan > media: Ethernet autoselect > status: active > inet 108.181.26.178 netmask 0xfffffff0 broadcast 108.181.26.191 > PPS: to check quickly on reachability of a gateway directly: > ping -I 108.181.26.178 -t 1 108.181.26.177 > and check arp table accordingly I will try this right now and save this email in the mailbox for important things to keep long term. -- Chris Bennett
