Re: cvs checkout of src,ports and xenocara gives duplicate key msg

2019-12-15 Thread putridsoul66
Currently I'm running the -stable OPENBSD-6.6
I want to set up the ports repository so 
I followed the faqs to set up a /usr/ports partition,
changed the group to wsrc and file modes to 775.
Then I added my local user to wsrc group.
After changing directory to /usr, I hit the following
command

cvs -qd anon...@anoncvs.ca.openbsd.org:/cvs checkout  \
 -rOPENBSD_6_6 -P ports

The output;
cvs server: duplicate key found for 'y'
U ports/.cvsignore
U ports/Makefile
..and then the normal output followed.






Re: small aggr problem ( on current )

2019-12-15 Thread Hrvoje Popovski
On 15.12.2019. 12:45, Holger Glaess wrote:
> hi
> 
> 
>   runing version
> 
> 
> /etc 16>dmesg | more
> Copyright (c) 1982, 1986, 1989, 1991, 1993
>     The Regents of the University of California.  All rights reserved.
> Copyright (c) 1995-2019 OpenBSD. All rights reserved.
> https://www.OpenBSD.org
> 
> OpenBSD 6.6-current (GENERIC.MP) #48: Tue Dec 10 16:30:01 MST 2019
> dera...@octeon.openbsd.org:/usr/src/sys/arch/octeon/compile/GENERIC.MP
> 
> 
> 
> after a reboot the aggr interface do not aggregate the connection with
> the switch,
> 
> just after an physical disaconnection from the ethernet cable , wait for
> some sec,
> 
> and replugin .
> 
> 
> the the iterface are up and active, before ifconfig says "no carrier"
> but the interfaces have
> 
> carrier.
> 
> i dont have the problem with the trunk interface on the same hardware.
> 
> 
> you are on bellab as root
> /etc 20>cat /etc/hostname.cnmac1
> mtu 1518
> up
> 
> 12:43:59 Sun Dec 15
> you are on bellab as root
> /etc 21>cat /etc/hostname.cnmac2
> mtu 1518
> up
> 
> 12:44:01 Sun Dec 15
> you are on bellab as root
> /etc 22>cat /etc/hostname.aggr0
> trunkport cnmac1
> trunkport cnmac2
> mtu 1518
> up
> 
> 
> holger
> 
> 
> 

Hi,

maybe logs below would help for further troubleshooting because i'm
seeing same behavior.

when i add debug statement in hostname.agg0 and boot box i'm getting
this log

starting network
aggr0 ix0 rxm: LACP_DISABLED (LACP_Enabled) -> PORT_DISABLED
aggr0 ix0: selection logic: unselected (rxm !CURRENT)
aggr0 ix1 rxm: LACP_DISABLED (LACP_Enabled) -> PORT_DISABLED
aggr0 ix1: selection logic: unselected (rxm !CURRENT)
aggr0 ix2 rxm: LACP_DISABLED (LACP_Enabled) -> PORT_DISABLED
aggr0 ix2: selection logic: unselected (rxm !CURRENT)
aggr0 ix3 rxm: LACP_DISABLED (LACP_Enabled) -> PORT_DISABLED
aggr0 ix3: selection logic: unselected (rxm !CURRENT)
reordering libraries: done.

after boot aggr status is "no carrier"
sh /etc/netstart isn't helping

but with ifconfig ix0-ix4 down/up aggr interface start to work normally

log when doing ifconfig ix0-ix4 down/up

aggr0 ix0 rxm: PORT_DISABLED (port_enabled) -> EXPIRED
aggr0 ix0 rxm: EXPIRED (LACPDU) -> CURRENT
aggr0 ix0: Selected UNSELECTED -> SELECTED
aggr0 ix0 mux: DETACHED (Selected == SELECTED) -> WAITING
aggr0 ix0 mux: WAITING (Selected == SELECTED) -> ATTACHED
aggr0 ix0: mux attached
aggr0 ix1 rxm: PORT_DISABLED (port_enabled) -> EXPIRED
aggr0 ix0 mux: ATTACHED (Partner.Sync) -> COLLECTING
aggr0 ix0: collecting enabled
aggr0 ix0 mux: COLLECTING (Partner.Sync) -> DISTRIBUTING
aggr0 ix0: distributing enabled
aggr0 ix1 rxm: EXPIRED (LACPDU) -> CURRENT
aggr0 ix1: Selected UNSELECTED -> SELECTED
aggr0 ix1 mux: DETACHED (Selected == SELECTED) -> WAITING
aggr0 ix1 mux: WAITING (Selected == SELECTED) -> ATTACHED
aggr0 ix1: mux attached
aggr0 ix2 rxm: PORT_DISABLED (port_enabled) -> EXPIRED
aggr0 ix2 rxm: EXPIRED (LACPDU) -> CURRENT
aggr0 ix2: Selected UNSELECTED -> SELECTED
aggr0 ix2 mux: DETACHED (Selected == SELECTED) -> WAITING
aggr0 ix2 mux: WAITING (Selected == SELECTED) -> ATTACHED
aggr0 ix2: mux attached
aggr0 ix3 rxm: PORT_DISABLED (port_enabled) -> EXPIRED
aggr0 ix3 rxm: EXPIRED (LACPDU) -> CURRENT
aggr0 ix3: Selected UNSELECTED -> SELECTED
aggr0 ix3 mux: DETACHED (Selected == SELECTED) -> WAITING
aggr0 ix3 mux: WAITING (Selected == SELECTED) -> ATTACHED
aggr0 ix3: mux attached
aggr0 ix1 mux: ATTACHED (Partner.Sync) -> COLLECTING
aggr0 ix1: collecting enabled
aggr0 ix1 mux: COLLECTING (Partner.Sync) -> DISTRIBUTING
aggr0 ix1: distributing enabled
aggr0 ix2 mux: ATTACHED (Partner.Sync) -> COLLECTING
aggr0 ix2: collecting enabled
aggr0 ix2 mux: COLLECTING (Partner.Sync) -> DISTRIBUTING
aggr0 ix2: distributing enabled
aggr0 ix3 mux: ATTACHED (Partner.Sync) -> COLLECTING
aggr0 ix3: collecting enabled
aggr0 ix3 mux: COLLECTING (Partner.Sync) -> DISTRIBUTING
aggr0 ix3: distributing enabled



Re: route an IPv4 /32 to a different interface

2019-12-15 Thread Kapetanakis Giannis

On 15/12/2019 21:57, Denis Fondras wrote:

Hi,

I have this setup :

em3: flags=8843 mtu 1500
 lladdr
 index 4 priority 0 llprio 3
 media: Ethernet autoselect (1000baseSX full-duplex)
 status: active
 inet6 fe80::aa9:b803:8a7a:ca72%em3 prefixlen 64 scopeid 0x4
 inet 172.16.0.254 netmask 0xff00 broadcast 172.16.0.255
em4: flags=8843 mtu 1500
 lladdr
 index 5 priority 0 llprio 3
 media: Ethernet autoselect (1000baseSX full-duplex)
 status: active
 inet 172.16.0.249 netmask 0xfffc broadcast 172.16.0.251
 inet6 fe80::29ae:98d:f238:fd68%em4 prefixlen 64 scopeid 0x5

I have a computer with IPv4 address 172.16.0.248 connected to em3.
When I try to ping it, obviously it goes to em4.

How can I route 172.16.0.248 through em3 ?

I tried with :
* route add 172.16.0.248/32 172.16.0.254 -iface em3
* route add 172.16.0.248/32 -llinfo -link -static -iface em3
but without luck.

Thank you in advance,
Denis




You can do this with pf route-to

G



Re: route an IPv4 /32 to a different interface

2019-12-15 Thread Tom Smyth
Hi Denis,

ok ..I hadnt read your email fully sorry about that...

what are you trying to achieve here?

you have a  172.16.0.249/30 address on em3  which includes
172.16.0.248-127.16.0.251

and then you have a 172.16.0.254/24 which includes the entire range of
 172.16.0.0-172.16.0.255

I think you are making life tougher on your self and who ever has to
diagnose the system after you...
it is private IP space co can you not put them on different networks
and do meat and Potatoes Routing ?

the other thing you need to consider is that you need to turn on proxy
arp (which can be very counter productive and cause other issues  ) so
that your host responds to arp requests for

172.16.0.249 and 172.16.0.250  on em3 (assuming you want hosts on the
network attached to em3 to be able to talk the ips connected to em4)

the other concern I would have is that you are trying to route traffic
to an ip that is a reserved ip  172.16.0.248 is the network address of
em4 according to your configuration...

I hope this helps...




On Sun, 15 Dec 2019 at 20:11, Denis Fondras  wrote:
>
> Hi,
>
> I have this setup :
>
> em3: flags=8843 mtu 1500
> lladdr
> index 4 priority 0 llprio 3
> media: Ethernet autoselect (1000baseSX full-duplex)
> status: active
> inet6 fe80::aa9:b803:8a7a:ca72%em3 prefixlen 64 scopeid 0x4
> inet 172.16.0.254 netmask 0xff00 broadcast 172.16.0.255
> em4: flags=8843 mtu 1500
> lladdr
> index 5 priority 0 llprio 3
> media: Ethernet autoselect (1000baseSX full-duplex)
> status: active
> inet 172.16.0.249 netmask 0xfffc broadcast 172.16.0.251
> inet6 fe80::29ae:98d:f238:fd68%em4 prefixlen 64 scopeid 0x5
>
> I have a computer with IPv4 address 172.16.0.248 connected to em3.
> When I try to ping it, obviously it goes to em4.
>
> How can I route 172.16.0.248 through em3 ?
>
> I tried with :
> * route add 172.16.0.248/32 172.16.0.254 -iface em3
> * route add 172.16.0.248/32 -llinfo -link -static -iface em3
> but without luck.
>
> Thank you in advance,
> Denis
>


-- 
Kindest regards,
Tom Smyth.



Re: route an IPv4 /32 to a different interface

2019-12-15 Thread Tom Smyth
Hi Denis
Try to add a static arp entry   for that particular Ip 172.16.0.248/32
 to the mac address of 172.16.0.254
that should work

On Sun, 15 Dec 2019 at 20:11, Denis Fondras  wrote:
>
> Hi,
>
> I have this setup :
>
> em3: flags=8843 mtu 1500
> lladdr
> index 4 priority 0 llprio 3
> media: Ethernet autoselect (1000baseSX full-duplex)
> status: active
> inet6 fe80::aa9:b803:8a7a:ca72%em3 prefixlen 64 scopeid 0x4
> inet 172.16.0.254 netmask 0xff00 broadcast 172.16.0.255
> em4: flags=8843 mtu 1500
> lladdr
> index 5 priority 0 llprio 3
> media: Ethernet autoselect (1000baseSX full-duplex)
> status: active
> inet 172.16.0.249 netmask 0xfffc broadcast 172.16.0.251
> inet6 fe80::29ae:98d:f238:fd68%em4 prefixlen 64 scopeid 0x5
>
> I have a computer with IPv4 address 172.16.0.248 connected to em3.
> When I try to ping it, obviously it goes to em4.
>
> How can I route 172.16.0.248 through em3 ?
>
> I tried with :
> * route add 172.16.0.248/32 172.16.0.254 -iface em3
> * route add 172.16.0.248/32 -llinfo -link -static -iface em3
> but without luck.
>
> Thank you in advance,
> Denis
>


-- 
Kindest regards,
Tom Smyth.



route an IPv4 /32 to a different interface

2019-12-15 Thread Denis Fondras
Hi,

I have this setup :

em3: flags=8843 mtu 1500
lladdr 
index 4 priority 0 llprio 3
media: Ethernet autoselect (1000baseSX full-duplex)
status: active
inet6 fe80::aa9:b803:8a7a:ca72%em3 prefixlen 64 scopeid 0x4
inet 172.16.0.254 netmask 0xff00 broadcast 172.16.0.255
em4: flags=8843 mtu 1500
lladdr
index 5 priority 0 llprio 3
media: Ethernet autoselect (1000baseSX full-duplex)
status: active
inet 172.16.0.249 netmask 0xfffc broadcast 172.16.0.251
inet6 fe80::29ae:98d:f238:fd68%em4 prefixlen 64 scopeid 0x5

I have a computer with IPv4 address 172.16.0.248 connected to em3.
When I try to ping it, obviously it goes to em4.

How can I route 172.16.0.248 through em3 ?

I tried with :
* route add 172.16.0.248/32 172.16.0.254 -iface em3
* route add 172.16.0.248/32 -llinfo -link -static -iface em3
but without luck.

Thank you in advance,
Denis



Re: cvs checkout of src,ports and xenocara gives duplicate key msg

2019-12-15 Thread Nick Holland
On 2019-12-15 09:42, putridsou...@gmail.com wrote:
> I recently did a checkout of the src,ports and xenocara
> repositories and was greeted by the following message on 
> each checkout. After this the command proceeds smoothly.
> Also doing "echo $?" gives "0" so it's not a error.
> 
> cvs server: duplicate key found for 'y'
> 
> A quick search online tied this message to file corruption.
> On further testing, the message repeated itself. Can anyone
> indicate if this has something to do with my hard disk or
> anoncvs server.

You left out an incredible amount of information and context
here, so I'm going to say there's a PEBKAC here somewhere.

Now, if you want to tell us in detail what you are doing and
what is actually happening.  Otherwise, best I can say is
something ain't right.

Nick.



Re: Third server now locked up after reboot due to no keyboard attached

2019-12-15 Thread Nick Holland
On 2019-12-14 14:28, Alfred Morgan wrote:
> I have now another machine running OpenBSD not recover from a reboot. I
> thought I was having hardware issues with my two other servers (both zbox)
> and now this third one (Dell) with totally different hardware is having the
> same problem getting stuck at the boot> prompt. The problem goes away and
> boots continue normally if I attach a USB keyboard in all three cases. I
> feel like this problem started showing up around OpenBSD 6.4. Is this a
> known issue?

certainly not a universal issue...(i.e., I haven't experienced it)

> When there is no keyboard attached the boot> prompt shows a box with a
> question mark in it looking like an unknown character. Picture showing this
> on bootx64 3.46:
> https://photos.app.goo.gl/7HAqQic6GArLGzaXA

Well...yeah.
If the boot loader echoed anything, it's behaving As Desired -- a char at
the command line means "STOP ALL BOOTING, I have something special I want
you to do".

The boot loader is entirely depenedent upon the firmware (BIOS), the kernel
isn't loaded, OpenBSD isn't running.  There's not a lot that OpenBSD
can do about this -- the boot loader could "eat" all chars sitting in the
buffer, but that would make interrupting the boot process just a little
more difficult when you DO want to stop it.

However, I think there are a few things you might be able to do to solve
your problem...

1) BIOS upgrade.  Long shot, but maybe?
2) BIOS config option?  Also a long shot, but since I'd call this a
boot firmware bug, maybe some combination of USB related options would
fix this?
3) a boot.conf file should fix -- simply putting "boot" in /etc/boot.conf
should override anything in the keyboard buffer.  Need to "control" the
boot?  plug in a keyboard and hold down either CTRL key, and you will be
given the boot> prompt.

Nick.


> Here is the dmesg from my latest Dell server:
> 
> OpenBSD 6.6 (GENERIC.MP) #3: Thu Nov 21 03:20:01 MST 2019
> r...@syspatch-66-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/
> GENERIC.MP
> real mem = 8487182336 (8094MB)
> avail mem = 8217251840 (7836MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe (71 entries)
> bios0: vendor Dell Inc. version "A02" date 11/14/2014
> bios0: Dell Inc. OptiPlex 3020M
...



Re: ttyC0 floods with error messages

2019-12-15 Thread Kenneth Gober
On Fri, Dec 13, 2019 at 8:42 AM  wrote:

> 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
>

In my experience when the console is spammed by mouse detach and attach
events, it's because the mouse is defective, usually because the cable is
wearing out and developing an intermittent fault.  Switch to a different
mouse,
even if the mouse appears to work ok, because it will probably get worse.

Another reason for these messages is because you're using a KVM switch that
performs the switch operation by disconnecting/reconnecting your USB
devices,
but I assume that isn't the cause here.

Suppressing the errors is probably a bad idea, in that case how would you
know
your mouse is developing a fault until more serious problems arise?  Better
to
be notified early so you have time to deal with it.

-ken


cvs checkout of src,ports and xenocara gives duplicate key msg

2019-12-15 Thread putridsoul66
I recently did a checkout of the src,ports and xenocara
repositories and was greeted by the following message on 
each checkout. After this the command proceeds smoothly.
Also doing "echo $?" gives "0" so it's not a error.

cvs server: duplicate key found for 'y'

A quick search online tied this message to file corruption.
On further testing, the message repeated itself. Can anyone
indicate if this has something to do with my hard disk or
anoncvs server.



Re: regression tests (was: OpenBSD Errata: December 11th, 2019 (ldso))

2019-12-15 Thread Frank Beuth

On Sat, Dec 14, 2019 at 11:39:57AM +0100, Claus Assmann wrote:

On Sat, Dec 14, 2019, Frank Beuth wrote:


OpenBSD doesn't have unit tests (or if they are, they're not in the main


Hmm, what about src/regress/ ?


Ah, that's what I was looking for. Not sure how I missed that.



Re: ppppoe octeon kernel panic .6.6

2019-12-15 Thread Holger Glaess

hi


with the current version


OpenBSD 6.6-current (GENERIC.MP) #48: Tue Dec 10 16:30:01 MST 2019
dera...@octeon.openbsd.org:/usr/src/sys/arch/octeon/compile/GENERIC.MP


the pppoe interface works as expected. no kernel panic anymore


thanks

holger

Am 22.10.19 um 21:12 schrieb Holger Glaess:

hi

ii will try tomorrow to do an backtrace after the panic.

i there additonal thinks what i can , or just this described in

https://www.openbsd.org/ddb.html

?


Holger


Am 22.10.19 um 07:10 schrieb Peter J. Philipp:

Hi,

The mail from Holger Glaess seems to be missing a backtrace.  I got 
one, but
I have very little time today and tomorrow to debug anything, I have 
put a
temporary replacement for the octeon pppoe router at my premises for 
the time

being.

Also, I tried poking around in sppp_auth_send() in 
/sys/net/if_spppsubr.c but
to no avail.  The fault lies in bcopy() in that function.  In the 
backtrace
it shows up as smallcpy().  When pppoe0 is disabled the kernel 
doesn't panic.


My bt follows with dmesg from my machine that was upgraded to 6.6.
After that Holger Glaess's mail which I had to fish out of my trash as I
had accidentally deleted it.

saturn# cu -l /dev/cuaU0 -s 115200
Connected to /dev/cuaU0 (speed 115200)
btint
smallcpy+0x8 (1,980001b6e376,1,2)  ra 0x8125140c sp 
0x98000ffdb

9b8, sz 0
sppp_auth_send+0x10c (1,980001b6e376,1,2)  ra 0x8124d294 
sp 0x98000

ffdb9b8, sz 144
sppp_lcp_tlu+0x274 (1,980001b6e376,1,2)  ra 0x81246f64 sp 
0x980

00ffdba48, sz 128
sppp_cp_input+0x141c (1,980001b6e376,1,2)  ra 0x81245458 
sp 0x98000

ffdbac8, sz 112
sppp_input+0x1d0 (1,980001b6e376,1,2)  ra 0x810b5e74 sp 
0x98000

ffdbb38, sz 80
pppoeintr+0xf9c (1,980001b6e376,1,2)  ra 0x813572c8 sp 
0x98000f

fdbb88, sz 400
if_netisr+0x118 (1,980001b6e376,1,2)  ra 0x8145d48c sp 
0x98000f

fdbd18, sz 80
taskq_thread+0x54 (1,980001b6e376,1,2)  ra 0x8127a0ec sp 
0x9800

0ffdbd68, sz 80
proc_trampoline+0x1c (1,980001b6e376,1,2)  ra 0x0 sp 
0x98000ffdbdb8, sz

  0
User-level: pid 81393
ddb{1}> show panic
the kernel did not panic
ddb{1}> boot reboot
System restart.
Jumping to start of image at address 0xbfca


U-Boot 2012.04.01 (UBNT Build ID: 4605996-gd120a44) (Build time: Oct 
14 2013 - 18:14:14)


Skipping PCIe port 0 BIST, in EP mode, can't tell if clocked.
Skipping PCIe port 1 BIST, reset not done. (port not configured)
BIST check passed.
UBNT_E200 r1:1, r2:9, serial #: 24A43C069F12
Core clock: 800 MHz, IO clock: 600 MHz, DDR clock: 533 MHz (1066 Mhz 
DDR)

Base DRAM address used by u-boot: 0x8f80, size: 0x80
DRAM: 2 GiB
Clearing DRAM.. done
Flash: 8 MiB
Net:   octeth0, octeth1, octeth2, octeth3, octeth4, octeth5, octeth6, 
octeth7

MMC:   Octeon MMC/SD0: 0
USB:   USB EHCI 1.00
scanning bus for devices... cannot reset port 1!?
1 USB Device(s) found
Type the command 'usb start' to scan for USB storage devices.

Hit any key to stop autoboot:  0
reading boot

3122300 bytes read
argv[2]: numcores=2
Allocating memory for ELF segment: addr: 0x8200 (adjusted 
to: 0x200), size 0x330d50
## Loading big-endian Linux kernel with entry point: 
0x8200 ...

Bootloader: Done loading app on coremask: 0x3
Starting cores 0x3
bootmem desc 0x48108 version 3.0
avail phys mem 0x001004d0 - 0x01fffbc0
skipped
avail phys mem 0x02330d50 - 0x0f10
avail phys mem 0x0f100020 - 0x0f100080
avail phys mem 0x0f1000a0 - 0x0fffd700
avail phys mem 0x2000 - 0x8f80
Total DRAM Size 0x8000
mem_layout[0] page 0x08CD -> 0x3C40
mem_layout[1] page 0x3C41 -> 
0x3FF)+"ij}"}Rj$}"}R$}}Rj$}B}Rj$}B}Rj$}
Rj$}2ij}}{j}"}R$Rj$}"}}Rj$}*R$}}}R$}}}Rj$}$}R}}Rj$2}{j$}R$}Rj$}}j}}RR}Rj$}"}{j}Copyright989, 
1991, 1egents of the y of Califhtorg


OpenBSD 6.6 (BOOT) #97: Sat Oct 12 06:00:20 MDT 2019
dera...@octeon.openbsd.org:/usr/src/sys/arch/octeon/compile/BOOT
real mem = 2147483648 (2048MB)
avail mem = 2083438592 (1986MB)
mainbus0 at root: board 20003 rev 1.9
cpu0 at mainbus0: CN61xx CPU rev 0.1 800 MHz, Software FP emulation
cpu0: cache L1-I 37KB 37 way D 32KB 32 way, L2 1024KB 8 way
clock0 at mainbus0: int 5
iobus0 at mainbus0
simplebus0 at iobus0: "soc"
octciu0 at simplebus0
"gpio-controller" at simplebus0 not configured
"mdio" at simplebus0 not configured
"mdio" at simplebus0 not configured
"pip" at simplebus0 not configured
"i2c" at simplebus0 not configured
"i2c" at simplebus0 not configured
com0 at simplebus0: ns16550a, 64 byte fifo
com0: console
com1 at simplebus0: ns16550a, 64 byte fifo
com1: probed fifo depth: 0 bytes
"spi" at simplebus0 not configured
octmmc0 at simplebus0
sdmmc0 at octmmc0: 8-bit, mmc high-speed
"bootbus" at simplebus0 not configured
"dma-engine" at simplebus0 not configured
"dma-engine" at simplebus0 not 

small aggr problem ( on current )

2019-12-15 Thread Holger Glaess

hi


  runing version


/etc 16>dmesg | more
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2019 OpenBSD. All rights reserved. 
https://www.OpenBSD.org


OpenBSD 6.6-current (GENERIC.MP) #48: Tue Dec 10 16:30:01 MST 2019
dera...@octeon.openbsd.org:/usr/src/sys/arch/octeon/compile/GENERIC.MP



after a reboot the aggr interface do not aggregate the connection with 
the switch,


just after an physical disaconnection from the ethernet cable , wait for 
some sec,


and replugin .


the the iterface are up and active, before ifconfig says "no carrier" 
but the interfaces have


carrier.

i dont have the problem with the trunk interface on the same hardware.


you are on bellab as root
/etc 20>cat /etc/hostname.cnmac1
mtu 1518
up

12:43:59 Sun Dec 15
you are on bellab as root
/etc 21>cat /etc/hostname.cnmac2
mtu 1518
up

12:44:01 Sun Dec 15
you are on bellab as root
/etc 22>cat /etc/hostname.aggr0
trunkport cnmac1
trunkport cnmac2
mtu 1518
up


holger





Re: unbound network optimizations

2019-12-15 Thread Mischa
On 12 Dec at 20:54, Jordan Geoghegan  wrote:
> 
> 
> On 2019-12-12 06:21, Winter Paulson wrote:
> > Hello,
> > 
> > I'm also experiencing the "Host is down" problem:
> > 
> > unbound: [85343:0] error: recvfrom 361 failed: Host is down
> > 
> > Running openbsd 6.6 (GENERIC.MP), current syspatch,
> > native unbound as a full resolver, pf disabled.
> > 
> > OpenBSD is a guest VM on a debian buster host using virtual e1000
> > network card ("Intel 82540EM" driver in openbsd). No firewall
> > in between. The VM is a tor-exit node.
> 
> I've heard others recommend using the vio driver over the em driver numerous
> times on here if running a virtualized instance. You may have a better time
> than you are now by using the VirtIO drivers. The intel nic emulation can
> sometimes have issues. Better to use an interface designed for virtualized
> environments.

I am seeing the same on OpenBSD on vmd/vmm. Similar setup.

Mischa



Re: APU2 fails to boot on OpenBSD 6.6-current #521

2019-12-15 Thread Mischa
On 13 Dec at 22:52, Alexander Pluhar  wrote:
> 
> > 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.

Can confirm it's working again after downrading to 4.10.0.3.


Mischa