Re: ttyC0 floods with error messages
On Fri, 13 Dec 2019, putridsou...@gmail.com wrote: Date: Fri, 13 Dec 2019 19:12:41 +0530 (IST) From: putridsou...@gmail.com To: misc@openbsd.org Subject: ttyC0 floods with error messages After boot, the following error message floods the virtual console on ttyC0 repeatedly, rest of virtuals console stay clear somehow. Is there a way to treat this permanently, other than Ctrl-l everytime, or disconnecting the mouse. There must be some config to disable this direct dumping of errors onto console. wsmouse0 at ums0 mux 0 wsmouse0 detached ums0 detached uhidev2 detached uhidev2 at uhub5 port 2 configuration 1 interface 0 "Logitech USB Optical Mouse" rev 2.00/72.00 addr 3 uhidev2: iclass 3/1 ums0 at uhidev2: 3 buttons, Z dir For some reason the same happens to me with both OpenBSD & NetBSD, but not with FreeBSD which is rock solid. I tend to just jump up to tty2 or whatever. Of course you can't do that on the installation. Good Luck, Clay clays.sh...@sdf.org SDF Public Access UNIX System - http://sdf.org
Re: APU2 fails to boot on OpenBSD 6.6-current #521
> Just upgraded my APU2 to the latest -current and it seems to hang on the disk. > It was fine running on -current #512. I encountered this problem on 6.6 stable with the latest syspatches installed after updating the APU firmware[1] to 4.11.0.1. It worked again after downgrading to 4.10.0.3. [1] https://pcengines.github.io smime.p7s Description: S/MIME cryptographic signature
Re: ipv6 via he.net connectivity issues - possible regression?
Hi, This is no longer an issue with latest snapshot. Best regards, Pedro Caetano A sexta, 13/12/2019, 14:05, Pedro Caetano escreveu: > Hi David, thank you for your reply > > I will test that and report back. > > > Best regards, > Pedro Caetano > > On Fri, Dec 13, 2019 at 1:27 PM David Gwynne wrote: > >> aggr(4) didn't exist in OpenBSD 6.6, so maybe that's the difference. Does >> the problem go away if you use trunk(4) instead of aggr(4)? Alternatively, >> could you build a -current kernel and make sure you have >> src/sys/net/if_aggr.c r1.25 and see what effect that has? >> >> Cheers, >> dlg >> >> > On 13 Dec 2019, at 8:06 am, Pedro Caetano >> wrote: >> > >> > Hi misc, >> > >> > I'm running amd64 -current, snapshot #518. >> > >> > My router has 4 em(4) interfaces. >> > em0 provides ipv4 internet via vlan100 which is connected to ISP ont. >> > em1, em2, em3 are bonded using aggr(4) to a lacp capable switch. >> > >> > A /48 subnet is routed via gif(4) tunnel to he.net, then subnetted into >> > /64s. >> > >> > Three vlans exist on top of the aggr(4) device. >> > Ipv4 addresses are assigned by dhcpd(8), ipv6 addresses are assigned by >> > rad(8). >> > >> > Hosts can acquire ip via rad(8), but are unable to access the internet >> > unless the gateway is pinged. >> > Hosts are also unreachable from the internet. >> > >> > Unfortunately I cannot tell precisely when this behavior started, but I >> > guess this was not an issue on 6.5. >> > >> > Please let me know if any more information is needed. >> > >> > Best regards, >> > Pedro Caetano >> >>
Re: How to open new window/pane in the current working directory in tmux?
On 13.12.2019 14:47, openbsd-misc-nos...@riseup.net wrote:
I have next options in tmux.conf:
bind '"' split-window -c "#{pane_current_path}"
bind % split-window -h -c "#{pane_current_path}"
bind c new-window -c "#{pane_current_path}"
But it doesn't work anymore. And I can't find working options in
Google. I tried
all suggestions from stackexchange and it doesn't work either. What
working options
for OpenBSD 6.6?
Did not know that Google and StackExchange is integrated in OpenBSD
documentation
In current (after 6.6) there is:
https://man.openbsd.org/tmux
pane_path #T Path of pane (can be set by application)
https://cvsweb.openbsd.org/src/usr.bin/tmux/screen.c (revision 1.56)
Can't see nothing about removal of pane_current_path even in CHANGES on
git so
if something was forgotten or is not BSD specific?
Thanks!
Re: ipv6 via he.net connectivity issues - possible regression?
Hi David, thank you for your reply I will test that and report back. Best regards, Pedro Caetano On Fri, Dec 13, 2019 at 1:27 PM David Gwynne wrote: > aggr(4) didn't exist in OpenBSD 6.6, so maybe that's the difference. Does > the problem go away if you use trunk(4) instead of aggr(4)? Alternatively, > could you build a -current kernel and make sure you have > src/sys/net/if_aggr.c r1.25 and see what effect that has? > > Cheers, > dlg > > > On 13 Dec 2019, at 8:06 am, Pedro Caetano > wrote: > > > > Hi misc, > > > > I'm running amd64 -current, snapshot #518. > > > > My router has 4 em(4) interfaces. > > em0 provides ipv4 internet via vlan100 which is connected to ISP ont. > > em1, em2, em3 are bonded using aggr(4) to a lacp capable switch. > > > > A /48 subnet is routed via gif(4) tunnel to he.net, then subnetted into > > /64s. > > > > Three vlans exist on top of the aggr(4) device. > > Ipv4 addresses are assigned by dhcpd(8), ipv6 addresses are assigned by > > rad(8). > > > > Hosts can acquire ip via rad(8), but are unable to access the internet > > unless the gateway is pinged. > > Hosts are also unreachable from the internet. > > > > Unfortunately I cannot tell precisely when this behavior started, but I > > guess this was not an issue on 6.5. > > > > Please let me know if any more information is needed. > > > > Best regards, > > Pedro Caetano > >
How to open new window/pane in the current working directory in tmux?
I have next options in tmux.conf:
bind '"' split-window -c "#{pane_current_path}"
bind % split-window -h -c "#{pane_current_path}"
bind c new-window -c "#{pane_current_path}"
But it doesn't work anymore. And I can't find working options in Google. I tried
all suggestions from stackexchange and it doesn't work either. What working
options
for OpenBSD 6.6?
Thanks!
ttyC0 floods with error messages
After boot, the following error message floods the virtual console on ttyC0 repeatedly, rest of virtuals console stay clear somehow. Is there a way to treat this permanently, other than Ctrl-l everytime, or disconnecting the mouse. There must be some config to disable this direct dumping of errors onto console. wsmouse0 at ums0 mux 0 wsmouse0 detached ums0 detached uhidev2 detached uhidev2 at uhub5 port 2 configuration 1 interface 0 "Logitech USB Optical Mouse" rev 2.00/72.00 addr 3 uhidev2: iclass 3/1 ums0 at uhidev2: 3 buttons, Z dir
Re: ipv6 via he.net connectivity issues - possible regression?
aggr(4) didn't exist in OpenBSD 6.6, so maybe that's the difference. Does the problem go away if you use trunk(4) instead of aggr(4)? Alternatively, could you build a -current kernel and make sure you have src/sys/net/if_aggr.c r1.25 and see what effect that has? Cheers, dlg > On 13 Dec 2019, at 8:06 am, Pedro Caetano > wrote: > > Hi misc, > > I'm running amd64 -current, snapshot #518. > > My router has 4 em(4) interfaces. > em0 provides ipv4 internet via vlan100 which is connected to ISP ont. > em1, em2, em3 are bonded using aggr(4) to a lacp capable switch. > > A /48 subnet is routed via gif(4) tunnel to he.net, then subnetted into > /64s. > > Three vlans exist on top of the aggr(4) device. > Ipv4 addresses are assigned by dhcpd(8), ipv6 addresses are assigned by > rad(8). > > Hosts can acquire ip via rad(8), but are unable to access the internet > unless the gateway is pinged. > Hosts are also unreachable from the internet. > > Unfortunately I cannot tell precisely when this behavior started, but I > guess this was not an issue on 6.5. > > Please let me know if any more information is needed. > > Best regards, > Pedro Caetano
