Re: I need help to see if I can reboot new network OK. Wild misadventures with non-OpenBSD support and bad IPMI
On Sat, Jul 29, 2023 at 07:41:18PM +, Philipp Buehler wrote: > Am 29.07.2023 21:29 schrieb Chris Bennett: > > The other IP's are randomly missing or give this: > > > > link#2 UHLc 0 450 - 3 em1 > > Hi, I'm happy. I practiced on the other server until I was sure, then I changed the first server over to the new way. I got one link#2 on the last IP, so I aliased that one in too and rebooted. Everything is great. What does link#2 mean in a more literal sense? Tomorrow all I have to do is new DNS records and swap the IP addresses for the other server. Tell them to switch me over to the new IP's and I'm done. I have no idea what the network problem was, but I leave my desktop on 24/7. It crashed for the first time ever. Most likely it was the problem. Thank you for the education. I fully approve of getting little pieces at a time. Change this. Doesn't work. Study it carefully. Post again. More problems. Then more help. I have always liked OpenBSD's policy of not giving information to just copy/paste. Now I need to go make a donation. Have a great day. -- Chris
Re: Any experiences with OpenBSD and Dell HBA355i (and/or Dell R350)
On Fri, Jul 28, 2023 at 05:56:21PM +0200, Rachel Roch wrote: > As per subject really, does anyone on-list have experience with the Dell > HBA355i controller and/or Dell350 ? > > I might have the chance to get my hands on an R350 which ideally I'd like to > use with OpenBSD and so wanted to reach out the community to find out if > there is anything I should be aware of. I haven't tried a HBA355 specifically, but that should work with mpii(4). There's some chance it'll need some new pci ids added to the driver and possibly some other slight changes. Dell RAID controllers up to the PERC 11 should work with mfii(4), but the PERC 12 will apparently need a new driver.
Re: Upgrade: Unbound constraint let fw_update always fail
Daniele B. said on Tue, 25 Jul 2023 16:33:50 +0200 (GMT+02:00) >My unattended upgrade happend like that: > >- I took up unbound >- sysupgrade >- 1st fw_update (this probbly is okay) >- reboot >- installation of the sets >- 2nd fw_update (this fails because unattended, local Unbound is down) >- reboot >- 3rd fw_update (this fails because unattended, local Unbound is down) >- syspatch (this fails as well) > >I finally took up my dev environment and run fw_update & syspatch. > >If the first fw_update is enough to be sure about a sucessfull >installation then case solved, just keeping the good stuff from the >thread.. Hi Daniele, OK, I'm hearing that you want ongoing control of which daemons are up and which are down, and that precludes just putting them in your /etc/rc.conf and/or /etc/rc.conf.local. There are two alternative process supervisors, runit and s6, that can give you much finer control over your daemons. Both have been designed from the ground up to be portable between Linux and every BSD distribution. You can use either runit or s6 to augment your rc.conf. You needn't *replace* rc.conf or rc.conf.local, you can *augment* them. I use runit (on Void Linux) every day, and love it to death. Runit is extremely simple. S6 is a little more capable and a little more complex. You can get lots of extremely authoritative information about runit and s6 on the Supervision mailing list. To subscribe, send an empty message to supervision-subscr...@list.skarnet.org. HTH, SteveT Steve Litt Autumn 2022 featured book: Thriving in Tough Times http://www.troubleshooters.com/bookstore/thrive.htm
Re: I need help to see if I can reboot new network OK. Wild misadventures with non-OpenBSD support and bad IPMI
On Sat, Jul 29, 2023 at 07:41:18PM +, Philipp Buehler wrote: > Oh, you need an alias for each IP that should be bound on em1 > so, like: > # cat /etc/hostname.em1 > inet 103.103.103.170/29 > inet alias 103.103.103.171/32 > inet alias 103.103.103.172/32 > inet alias 103.103.103.173/32 > inet alias 103.103.103.174/32 > This seemed to work. The network is very strange for me. Not sure if my hotspot is bad or if they are having network problems at the company. New network, new problems? I will get back later if this is a real problem or not. I was reading route manpage. Next is netstart script and manpage. Thanks. I really appreciate it. Chris Bennett > > mygate and netstart has a manpage, as there is 'hostname.if' to read :) > > PS: pointless to use '-x'; just a lot of debug noise > > -- > pb > --
Re: I need help to see if I can reboot new network OK. Wild misadventures with non-OpenBSD support and bad IPMI
Am 29.07.2023 21:29 schrieb Chris Bennett: The other IP's are randomly missing or give this: link#2 UHLc 0 450 - 3 em1 Each route flush;sh -x /etc/nestart or a reboot changes the result. Oh, you need an alias for each IP that should be bound on em1 so, like: # cat /etc/hostname.em1 inet 103.103.103.170/29 inet alias 103.103.103.171/32 inet alias 103.103.103.172/32 inet alias 103.103.103.173/32 inet alias 103.103.103.174/32 # cat /etc/mygate 103.103.103.169 mygate and netstart has a manpage, as there is 'hostname.if' to read :) PS: pointless to use '-x'; just a lot of debug noise -- pb
Re: I need help to see if I can reboot new network OK. Wild misadventures with non-OpenBSD support and bad IPMI
On Sat, Jul 29, 2023 at 06:18:40PM +, Philipp Buehler wrote: > Am 29.07.2023 20:04 schrieb Chris Bennett: > > inet 103.103.103.168/29 > > That's wrong, you put the "first" IP-address you want to > use/have on em1. So that would be 170/29 > Well, that half-worked. Always get ...170, works. ssh works. autossh with -M no longer works except with autossh -M 0 ...169 is the gateway. ...175 is broadcast. The other IP's are randomly missing or give this: link#2 UHLc 0 450 - 3 em1 Each route flush;sh -x /etc/nestart or a reboot changes the result. I just tried mygate at ...174. No good. > (168 is this network's BSD-broadcast or "net address") > > > > /etc/mygate is > > 103.103.103.169 > Cannot forsee what your ISP provides as the gateway, but > likely that's correct. > Feel free to offer me a good man page to start with. Coffee is working. -- Chris Bennett
Re: I need help to see if I can reboot new network OK. Wild misadventures with non-OpenBSD support and bad IPMI
Am 29.07.2023 20:04 schrieb Chris Bennett: inet 103.103.103.168/29 That's wrong, you put the "first" IP-address you want to use/have on em1. So that would be 170/29 (168 is this network's BSD-broadcast or "net address") /etc/mygate is 103.103.103.169 Cannot forsee what your ISP provides as the gateway, but likely that's correct. All names (hosts,myname) is not directly relevant to IP networking. Do not put names in mygate (just a sidenote). ifconfig gave 103.103.103.168 as the IP address route -n show gave 103.103.103.168 as the gateway. Likely a config from the errornous hostname.if entry, see above. I did not change or remove what's in /etc/hostname which is at 103.103.103.170. Does that matter? hosts I assume? That might be relevant to apache, but not the networking (reachability) itself. -- pb
Re: I need help to see if I can reboot new network OK. Wild misadventures with non-OpenBSD support and bad IPMI
On Sat, Jul 29, 2023 at 04:34:17AM +, Philipp Buehler wrote: > > 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@. > Hmm, I also have a newer server with the same company that does have a usable IPMI. I also have to change IP's with it too. It is running -current from a few weeks ago, so this is a fictional address except for the last three digits (168) 103.103.103.168/29 Right now, I have my first IP I'm using at 103.103.103.170 I put into /etc/hostname.em1: inet 103.103.103.168/29 /etc/mygate is 103.103.103.169 /etc/myname is network-moron.com I did not change /etc/hosts which just has the addresses from 103.103.103.170 to 103.103.103.175 added. I rebooted, but couldn't ping the server at any address. In IPMI, there were no network problems on the boot screen, but apache2 failed to start. ifconfig gave 103.103.103.168 as the IP address route -n show gave 103.103.103.168 as the gateway. For the heck of it, I changed /etc/mygate to 103.103.103.168, just to see if that provided any useful information. Same failed outcome, as I expected. .later I tried every obvious variation I could think of. Nothing works except what I used on the other server. A couple of years ago I tried to do what you suggested with a script to swap back in the old hostname and reboot. I couldn't ever get it to work Since what I had worked (not what I really wanted to use with the aliases), I just blew it off. I took a good while with my brain in sludge mode last night to change some essential passwords and shut off imap, etc. I still lacking enough sleep. Having coffee, going to eat and probably go back to bed. I just wanted to try this out while I could. I wanted to post about this and then RTFM's later with a clear head. I did not change or remove what's in /etc/hostname which is at 103.103.103.170. Does that matter? -- Chris Bennett
Re: libvirtd on openbsd
On Fri, Jul 28, 2023 at 03:22:48AM +, All wrote: | For some reason I didn't get reply from Stuart to my inbox. | Its on the mailing lists though. Looks like Stuart only replied to the list. He's helpful like that, preventing you from getting the same mail twice. Thanks, Stuart. | Thank you for your reply. I guess there are no solutions to run | VMs with a graphical interface yet. Unless, I run qemu and vnc | to a VM. You can run X on a vmd VM too if you're using vnc. There was some discussion about it recently. Paul -- >[<++>-]<+++.>+++[<-->-]<.>+++[<+ +++>-]<.>++[<>-]<+.--.[-] http://www.weirdnet.nl/
Re: Routing multiple IPv4 blocks
On Fri, Jul 28, 2023 at 10:09:31PM +0100, Polarian wrote: > I do have one question, if anyone is willing to answer it, so I have on and > off specified "keep state" depending on when I wrote the rule, but the > following specifies it is the default: > https://www.openbsd.org/faq/pf/filter.html > > So why do a lot of examples I see specify keep state if it is the default, > is there any benefit of specifying it which I am missing? I would guess that some of the examples are based on something that was written long enough ago that "keep state" was not the default. I personally only add "keep state" when I also need to add state options such as pflow or state tracking options. If you do a "pfctl -vnf /etc/pf.conf" and compare the output to the stored file, you will see that "keep state" and possibly other defaults will be appened (and things like lists of ports generating several rules and so on). - Peter -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: Ryzen 9 (7x000) users: do you experience hangs?
Hi, I'm running OpenBSD-current (OpenBSD 7.3-current (GENERIC.MP) #1314: Tue Jul 25 17:02:17 MDT 202) for many years now on my Lenovo Thinkpad T14 AMD Gen1 without any big issues so far. Few weeks ago, my system started to hang randomly, but many times, it was linked to Firefox high memory usage or after a suspend. In both case, the network is unreachable and the only way to "fix" this issue is to do an hard reboot. In fact, I got many X11 hangs in the past, but those were easily fixed by killing X11, firefox or just by remotely rebooting the laptop. Here my dmesg: https://dmesgd.nycbug.org/index.cgi?do=view=7234
Re: I need help to see if I can reboot new network OK. Wild misadventures with non-OpenBSD support and bad IPMI 11 Perhaps they just don't have a proper setup or are not using it.
On Sat, Jul 29, 2023 at 04:34:17AM +, 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 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 0xfff0 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
