Re: How to troubleshoot DHCP issues?
Sorry, there was a typo: The problem *does disappear* with `lladdr random` removed . It seems that with `lladdr random` removed, the problem does not seem to disappear.
Re: How to troubleshoot DHCP issues?
> My first suggestion might be to stay with a single lladdr for a > while to see if your setup works for more than a day and a half. Thanks for the suggestion! It seems that with `lladdr random` removed, the problem does not seem to disappear. lladdr random Why this line? I was wondering the same thing. What problem do you think you are solving by doing this? I try to make it harder for my ISP to gather information about the device I'm using, thus was using random MAC address. > The "random" lladdr catches my eye. But I don't know how > frequently that changes. Could it change every time the lease > is renewed? Skimming through the code for dhcpleased, looks like there's no invocation of the SIOCSIFLLADDR ioctl, so I would assume that the lladdr stays the same unless the netstart script is re-run (thus invoking ifconfig to change lladdr), but I will to test that to make sure. It smells of a bug somewhere... I mean, as long as the lladdr does not change in the middle of the lease, then the router should have been able to successfully obtain a new IP address, right? Best Regards
50Gbe
Hi folks! I wonder if OBSD supports 50Gbe network cards. And what is the cable standard to support such data transfers ? Thanks. -- The lion and the tiger may be more powerful, but the wolves do not perform in the circus
Re: Crash when unplugging a UPS USB connection
On 2021-08-05, Mike wrote: > On 8/5/2021 9:52 AM, Stuart Henderson wrote: > >> >> By requiring that somebody have an affected UPS to reproduce the >> bug you seriously reduce the number of people who can help. > > OK, sorry for the noise. > > I'll move on then. > > Thanks for the reply. > > > Short of having an affected UPS, providing the debug information that is printed on-screen is the next best thing. Please do continue to report problems, but please include information and take into account that people who might be able to help can't necessarily reproduce it themselves. Fortunately abieber@ had an affected UPS too and posted on the bugs@ thread with stack trace etc. (He is a developer but anybody with the problem and either a camera or paper and pencil could do that too). Which pointed at a particular set of commits likely to have caused it. With a bit more testing that was confirmed, and shortly after mpi@ diagnosed the cause. Providing that information in an easy to read form really does help.
Re: Crash when unplugging a UPS USB connection
On 8/5/2021 9:52 AM, Stuart Henderson wrote: > > By requiring that somebody have an affected UPS to reproduce the > bug you seriously reduce the number of people who can help. OK, sorry for the noise. I'll move on then. Thanks for the reply.
Re: WireGuard host crashes roughly every week
Thanks so much Matt!
It works! I've reenabled PersistantKeepalive overnight and mbufs are staying
low.
The failed handshakes are still occurring, "ifconfig wg0 debug" filled my dmesg
with hundreds of lines like:
> wg0: Handshake for peer 10 did not complete after 5 seconds, retrying (try 6)
> wg0: Sending handshake initiation to peer 10
> wg0: Zeroing out keys for peer 10
But I don't have any evidence that this is hurting anything :)
--Matt
> On Aug 4, 2021, at 5:36 AM, Matt Dunwoodie wrote:
>
> On Tue, 3 Aug 2021 13:02:15 -0500
> "Matt P." wrote:
>
>> Hi Stuart!
>>
>> Your advice lead me to discover, the issue happens only with the
>> "PersistantKeepalive = 25" option I had enabled on each wg-quick
>> peer. Looks like you could recreate it by making a few no-address
>> peers with this option enabled.
>
> Hi Matt,
>
> This insight was very helpful. It looks like mbufs are not freed if
> we're sending to a peer with no endpoint. Specifically, "wg_send" is
> expected to free the mbuf if there is an error sending. This (untested)
> patch should fix it.
>
> Cheers,
> Matt
>
> diff --git if_wg.c if_wg.c
> index 18333eda4cb..5f4319558ab 100644
> --- if_wg.c
> +++ if_wg.c
> @@ -810,6 +810,7 @@ wg_send(struct wg_softc *sc, struct wg_endpoint *e,
> struct mbuf *m)
>IPPROTO_IPV6);
> #endif
>} else {
> +m_freem(m);
>return EAFNOSUPPORT;
>}
>
Re: Crash when unplugging a UPS USB connection
On 8/5/2021 8:18 AM, Stuart Henderson wrote: > Please report to bugs@ with the following, > > - quick summary of problem > - dmesg > - a text version of the panic/crash message > - at least a text version of the function names from the backtrace > if not the full thing > - links to images hosted elsewhere (not attachments) if the text version > of the above isn't the full thing Thanks for the reply. I did that on a week or two ago. I was not able to get the text version of the crash message, but the images show it clearly. https://marc.info/?l=openbsd-bugs=162612361706514=2 To clarify, to reproduce... - Reboot after the fresh install of OpenBSD current. - plug in the USB comm cable from the UPS - the console shows the USB connection details - unplug the USB comm cable from the UPS - the console shows the crash
Re: Crash when unplugging a UPS USB connection
On 2021-08-05, Mike wrote: > On 8/5/2021 8:18 AM, Stuart Henderson wrote: >> Please report to bugs@ with the following, >> >> - quick summary of problem >> - dmesg >> - a text version of the panic/crash message >> - at least a text version of the function names from the backtrace >> if not the full thing >> - links to images hosted elsewhere (not attachments) if the text version >> of the above isn't the full thing > > Thanks for the reply. > > I did that on a week or two ago. I was not able to get the text version > of the crash message, but the images show it clearly. Just type in the relevant lines from the images. > https://marc.info/?l=openbsd-bugs=162612361706514=2 For bug reports you really need to get the basic information in front of developer's eyeballs without any extra work on their part. Plain text in the email will be right there. Links that need opening in a browser can be useful for extra information. A zip file that needs downloading, extracting, files opening - it's quite a barrier when somebody might just be able to quickly read the panic message and functions in the backtrace and say "aha I know what that is". > To clarify, to reproduce... > > - Reboot after the fresh install of OpenBSD current. > > - plug in the USB comm cable from the UPS By requiring that somebody have an affected UPS to reproduce the bug you seriously reduce the number of people who can help. > - the console shows the USB connection details > > - unplug the USB comm cable from the UPS > > - the console shows the crash > > > > > > > >
Re: How to troubleshoot DHCP issues?
On Thu, Aug 5, 2021 at 6:29 AM Stuart Henderson wrote: > > On 2021-08-03, beebeet...@posteo.de wrote: > > Hi all, > > > > Me again on some DHCP-related issues... > > > > So I started using OpenBSD as my home router around two weeks ago, > > running openBSD 6.9. It obtains its IP address from the ISP via > > DHCP. The setup is pretty simple, just the following two lines in > > my hostname.if file: > > > > lladdr random > > Why this line? I was wondering the same thing. What problem do you think you are solving by doing this? Because by doing this the DHCP server thinks you are a new system so you will get a new IP address.
Re: WireGuard host crashes roughly every week
On 2021/08/04 13:57, Claudio Jeker wrote:
> > diff --git if_wg.c if_wg.c
> > index 18333eda4cb..5f4319558ab 100644
> > --- if_wg.c
> > +++ if_wg.c
> > @@ -810,6 +810,7 @@ wg_send(struct wg_softc *sc, struct wg_endpoint *e,
> > struct mbuf *m)
> > IPPROTO_IPV6);
> > #endif
> > } else {
> > + m_freem(m);
> > return EAFNOSUPPORT;
> > }
> >
> >
>
> Diff looks sensible. OK claudio@
Thanks, committed.
Re: How to troubleshoot DHCP issues?
On 2021-08-03, beebeet...@posteo.de wrote: > Hi all, > > Me again on some DHCP-related issues... > > So I started using OpenBSD as my home router around two weeks ago, > running openBSD 6.9. It obtains its IP address from the ISP via > DHCP. The setup is pretty simple, just the following two lines in > my hostname.if file: > > lladdr random Why this line?
Re: Crash when unplugging a UPS USB connection
Please report to bugs@ with the following, - quick summary of problem - dmesg - a text version of the panic/crash message - at least a text version of the function names from the backtrace if not the full thing - links to images hosted elsewhere (not attachments) if the text version of the above isn't the full thing On 2021-08-03, Mike wrote: > On 7/12/2021 4:16 PM, Mike wrote: >> On 7/12/2021 3:12 PM, Mike Larkin wrote: >>> On Sun, Jul 11, 2021 at 04:11:39PM -0400, Mike wrote: I run NUT on OpenBSD to monitor a Cyperpower UPS. The UPS plugs into the OpenBSD box via a USB connection. OpenBSD 6.8, I had no problems, everything ran fine. When the power went out, NUT saw that and reacted according to configuration. After I upgraded to OpenBSD 6.9 (a fresh install, not an in-place upgrade), when the power dropped, I'd be greeted with a blue crash screen. It seems that when the power drops, the UPS temporarily drops the USB connection, seemingly the equivalent of unplugging the USB connector. I am able to reproduce that 100% by booting up OpenBSD 6.9 with the UPS communications cable plugged into the USB port. When I unplugged that USB connector, the crash occurs. This first occurred on my production box which is a Supermicro motherboard. I can provide that dmesg if needed. Both OpenBSD 6.8 and current below are fresh installs on a test Lenovo laptop. On OpenBSD 6.8, when I plug in the UPS and unplug it, here is what I see on the console (dmesg is included): >>> >>> This crash happens to me as well when I unplug my upd(4). I'll try to find >>> what diff caused this. >>> >>> -ml >> >> >> Many thanks for the confirmation! >> >> Mike. >> >> > > This crash also occurs with the following two UPSs: > > Cyberpower EC750G > Tripp-Lite OmniSmart1500LCDT > > As before, to reproduce it > > 1) fresh install of OpenBSD current > 2) do the reboot after the install > 3) plug in the UPS > 4) unplug it > > > I can supply images of the crash screens for the two UPSs above if they > are needed. > > Thanks! > > > >
Re: X blanking
On 2021-08-05, gh057 wrote: > I'm running xfce-4.16, I've disabled the screensaver in settings, I've tried > xset; I've tried installing xscreensaver and running it with the screensaver > disabled. > > But it still blanks. > > Sent from ProtonMail mobile > In which way do you use xset?
Re: Can't figure out what's taking up space on /
Le mercredi 04 août 2021 à 14:20 -0700, Greg Thomas a écrit : > At some point my rsync script ran while /backup wasn't mounted or > something. The culprit was there. Hello. I've done that more than once, especially on NFS-mounted backups. Since then, I put the mount points directories immutable (before mount) fremen# mkdir /tmp/foo fremen# chflags schg /tmp/foo fremen# touch /tmp/foo/bar touch: /tmp/foo/bar: Operation not permitted fremen# ls -loa /tmp/foo total 8 drwxr-xr-x 2 root wheel schg 512 Aug 5 11:01 . drwxrwxrwt 14 root wheel -512 Aug 5 11:01 .. fremen# mount /dev/vnd0a /tmp/foo/ fremen# touch /tmp/foo/bar fremen# ls -lao /tmp/foo/ total 8 drwxr-xr-x 2 root wheel - 512 Aug 5 11:10 . drwxrwxrwt 14 root wheel - 512 Aug 5 11:10 .. -rw-r--r-- 1 root wheel - 0 Aug 5 11:10 bar Regards, -- Bastien
