Re: ipv6 assistance

That works - I didn't realize I needed to install a package to have ipv6 work with OpenBSD. Thank you.

ipv6 assistance

Running -current on my router and finally (after years) decided to move into using ipv6. I added "inet6 autoconf" to hostname.em0 (also has "inet autoconf") and I get a link local address: = # ifconfig em0 em0:inet6 fe80::2132:31ff:fe0b:7ea4%em0 prefixlen 64

sysupgrade fails firmware fetch

Today "sysupgrade -s" failed to fetch updated firmware: = Verifying sets. Fetching updated firmware. fw_update: failed. Cannot fetch http://firmware.openbsd.org/firmware/7.5//SHA256.sig (404 Not Found) Upgrading. = Seems it's looking for a 7.5 directory

Re: upgrade to latest snapshot failing

On Fri, Nov 17, 2023 at 2:43 PM Stuart Henderson wrote: > > Try booting bsd.rd and downloading a newer snap. The latest bsd.rd is identical to the bsd.upgrade file. The older bsd,rd from yesterday boots fine as the system does recover from the failed upgrade if one has physical access to it to

Re: upgrade to latest snapshot failing

On Fri, Nov 17, 2023 at 2:06 PM Stuart Henderson wrote: > > Bit old by now, boot bsd.rd and try a newer one? > > If that fails too: which arch? I'm currently on #1447, amd64, from which I was running "sysupgrade -s". Apparently boots from bsd.upgrade during the process.

upgrade to latest snapshot failing

Following -current: OpenBSD 7.4-current (GENERIC.MP) #1447: Wed Nov 15 09:56:54 MST 2023 Upgrade via "sysupgrade -s" now failing with: init: single user shell terminated, restarting init: single user shell terminated, restarting init: single user shell terminated, restarting Chris

Re: OpenBSD Wireguard implementation not copying ToS from inner to outer WG header

Hopefully not as dumb of a question as I suspect it might be. Does the generic... = match out on $ext_if inet proto tcp from ($ext_if) set prio (3, 7) match in on $ext_if inet proto tcp to ($ext_if) set prio (3, 7) = ...take advantage of this patch when using wireguard or does the match

Re: core dumps from latest wireguard-tools

Tried this: pkg_delete wireguard-tools pkg_delete -a(which removes bash-5.2.15) then pkg_add wireguard-tools (which also reinstalls bash-5.2.15) And it resolved the issue on all 3 systems.

Re: core dumps from latest wireguard-tools

What I find odd is that it dumps core on 3 of the 5 systems but works fine on the other two. All systems are x64 at OpenBSD 7.3-current (GENERIC.MP) #1216 with wireguard-tools-1.0.20210914p1v0. On Mon, Jun 5, 2023 at 8:51 AM Stuart Henderson wrote: > > On 2023-06-05, Sonic wrote: >

core dumps from latest wireguard-tools

After upgrading several systems to the latest snapshot this evening most of them are causing core dumps when running wg: # wg Segmentation fault (core dumped) This is with: wireguard-tools-1.0.20210914p1v0

Re: alias issue with snapshot #1175

Sorry for the noise. It did turn out to be that the 3rd party device was squatting on the .45 address. Thanks to all!

Re: alias issue with snapshot #1175

On Tue, May 9, 2023 at 2:24 AM Stuart Henderson wrote: > The only strange thing in there that I'm seeing is > > inet 10.68.73.1 255.255.255.248 > ... > !route add -inet /24 10.68.73.1 > !route add -inet /24 10.68.73.1 > > i.e. adding a route pointing at the local machine for those various >

Re: alias issue with snapshot #1175

On Tue, May 9, 2023 at 12:35 AM Navan Carson wrote: > Do you have names that depend on DNS in pf.conf? No.

Re: alias issue with snapshot #1175

oot, once the interface is restarted all is well. Absolutely nothing in the logs indicating any error. On Mon, May 8, 2023 at 10:48 AM Sonic wrote: > > On Mon, May 8, 2023 at 9:24 AM Stuart Henderson > wrote: > > There's not enough information really. /etc/hostname.* and maybe results &g

Re: alias issue with snapshot #1175

On Mon, May 8, 2023 at 9:24 AM Stuart Henderson wrote: > There's not enough information really. /etc/hostname.* and maybe results > of ifconfig -A and netstat -rn might give more clues. Here's that info - hopefully not munged beyond use. Note that this is after the interface has been restarted

Re: alias issue with snapshot #1175

brings the .45 alias back to an active state. On Sun, May 7, 2023 at 8:43 PM Sonic wrote: > > After doing a "sh /etc/netstart em0" that alias is back up and > working. The problem occurs after boot. > > On Sun, May 7, 2023 at 7:23 PM Sonic wrote: > > > > Hell

Re: alias issue with snapshot #1175

After doing a "sh /etc/netstart em0" that alias is back up and working. The problem occurs after boot. On Sun, May 7, 2023 at 7:23 PM Sonic wrote: > > Hello, > > Upgrade a system to the latest snapshot - 1175 - and am seeing a > problem with an alias address. > The

alias issue with snapshot #1175

Hello, Upgrade a system to the latest snapshot - 1175 - and am seeing a problem with an alias address. The outside IP is part of a /29 (not actual addresses) : inet 51.67.20.41 netmask 0xfff8 broadcast 51.67.20.47 inet 51.67.20.42 netmask 0x inet 51.67.20.43

Re: Problem with WireGuard on OpenBSD 7.3

On Thu, May 4, 2023 at 9:45 AM Janne Johansson wrote: > Apart from that, you either use /usr/local/bin/wg(-quick) to set up > your wireguard interface OR hostname.wg0 not calling one from the > other. Thanks for that. Seems every website I've found uses calling /usr/local/bin/wg from the

udp port 0

I'm seeing the following in my pf logs: == Sep 15 14:08:49.593449 rule def/(short) pass in on em2: 172.26.20.137.60866 > 172.26.62.1.0: udp 0 Sep 15 14:08:49.809690 rule def/(short) pass in on em2: 172.26.20.137.65148 > 172.26.62.1.0: udp 0 Sep 15 14:09:29.149953 rule

Re: Modern RFC3442 (Classless DHCP Static Routes)

On Tue, May 10, 2022 at 4:23 AM wrote: > most > other OSes ship with "broken" RFC3442 support in this fashion. Cisco > doesn't, but Mac, Ubuntu, Windows, and Android do. Color me suprised to > find out this wrinkle of RFC3442. Note that the test is using the Openbsd isc-dhcp-server-4.4.3

Re: Modern RFC3442 (Classless DHCP Static Routes)

Dealing with broken clients can be handled with separate groups or even "deny booting;" instead of breaking the dhcp server.

Re: Modern RFC3442 (Classless DHCP Static Routes)

On Mon, May 9, 2022 at 6:03 AM Stuart Henderson wrote: > On 2022-05-09, Stuart Henderson wrote: > > ...so the correct configuration is clear: list both a 0.0.0.0/0 > classless route and "option routers", and it should work for all > cases. Yes. The server sends both, the clients that handle

Re: Modern RFC3442 (Classless DHCP Static Routes)

On Fri, May 6, 2022 at 7:18 AM Florian Obser wrote: > Also, dhcpd(8) does not even hand out option 3 when option 121 is > configured. That doesn't seem like correct behavior (the ISC version certainly offers both). Both options should be sent if configured, it's up to the client to properly

Re: dhcp issues

On Sun, Jul 18, 2021 at 3:55 PM Stuart Henderson wrote: > > The bits that can't be handled are the more per-interface things ("fetch > an address but ignore dns or the default route on interface X however do > fetch them from interface Y", or "my ISP won't give me a lease without > providing a

Re: dhcp issues

On Sat, Jul 17, 2021 at 11:20 AM Theo de Raadt wrote: > > Instead, we are focusing on 99% of the use cases. I hardly think that wanting to override your ISP's name servers is outside of the 99% use cases. Of course it wouldn't be the first time I am wrong. > You might want to look into using

Re: dhcp issues

On Fri, Jul 16, 2021 at 10:35 PM Theo de Raadt wrote: > We are moving from a model where dhclient on 1 interface believes it is > MASTER of /etc/resolv.conf and a bunch of system aspects, and the > userbase is familiar with a pile of hacky control knobs in > dhclient.conf. > > Towards a model

dhcp issues

Having some issues after a sysupgrade to the latest snapshot (of this writing) - OpenBSD 6.9-current (GENERIC.MP) #131. Seems the base change to dhcpleased/resolvd has presented some issues. Pf does not start on boot as it claims my dhcp interface has no address, however after logging in I can

Re: how to use OpenBSD firewall (pf) to protect Ooma Telo VOIP phone system

For starters use a separate vlan for the phones. On Mon, Jul 5, 2021 at 2:02 PM Jonathan Thornburg wrote: > > Short summary: > > Has anyone used an OpenBSD firewall (pf) to protect an Ooma Telo VOIP > phone system from internet attacks? If so, how did you do it? More > generally, how do people

Re: help me to create hostname.wg

On Fri, Oct 30, 2020 at 12:07 PM kasak wrote: > $ wg showconf wg0 > [Interface] > ListenPort = 9022 > > why the keys is not configured? You're not root.

Re: can't install some packages on -current

On Tue, Aug 4, 2020 at 4:24 PM wrote: > Update the installed packages first pkg_add -Uu It's a fresh install based on -current just downloaded. First attempt at installing packages, so no packages to upgrade.

Re: can't install some packages on -current

stick to > releases. > > Sonic wrote: > > > On a slightly older install I have the missing libraries (and the newer > > ones): > > /usr/lib/libc++.so.4.0 > > /usr/lib/libc++.so.5.0 > > /usr/lib/libc++abi.so.2.1 > > /usr/lib/libc++abi.so.3.0 &

Re: can't install some packages on -current

/libc++.so.5.0 /usr/lib/libc++abi.so.3.0 /usr/lib/libpcap.so.9.0 Chris On Tue, Aug 4, 2020 at 4:00 PM Sonic wrote: > > Fresh install of -current and I'm getting these errors when running pkg_add: > > library pcap.8.4 not found > /usr/lib/libpcap.so.9.0 (system): bad major > library

can't install some packages on -current

Fresh install of -current and I'm getting these errors when running pkg_add: library pcap.8.4 not found /usr/lib/libpcap.so.9.0 (system): bad major library c++.4.0 not found /usr/lib/libc++.so.5.0 (system): bad major library c++abi.2.1 not found /usr/lib/libc++abi.so.3.0 (system): bad major

Re: wireguard multiple interfaces

On Fri, Jul 31, 2020 at 3:15 PM wrote: > Use multiple interfaces, one per site to connect with. Overhead isnt really > present, its just routing and hashes at that point. > (I’ve had no issues doing site to sites in this fashion, has been working > great for months) I was picturing 3 wgx

wireguard multiple interfaces

The need is for site-to-site vpns (multiple client sites to one server site), 3 vlans each. >From a management point of view it might be better to use 3 wireguard interfaces on all of the routers (wg0, wg1, wg2). But I'm not sure if that adds overhead, and if so how much. Basically, is it better

Re: IKEDv2 and alias addresses

On Thu, Jun 25, 2020 at 4:10 PM Tobias Heider wrote: > I tried to reproduce your bug (on current) but it seems to work as intended > for me. It would certainly help to have a bit more info such as an iked log > and a tcpdump of your failed handshake as well as the used openbsd version. The

Re: IKEDv2 and alias addresses

On Sun, Jun 21, 2020 at 5:20 PM Stuart Henderson wrote: > > IIRC "local" isn't enough, some packets are still sent on the bound > 0.0.0.0, the kernel chooses the source address (based on the local > interface address in the route to the destination) and it can be > the wrong address for the other

Re: IKEDv2 and alias addresses

On Sun, Jun 21, 2020 at 12:11 PM Patrick Wildt wrote: > If you want to use a specific address for a policy, you can use the > "local" keyword to specify it. This is part of the policy, not a global > option. > > Then iked(8) continues to losten on 0.0.0.0:500, but the policy will > only match if

IKEDv2 and alias addresses

With IKEDv1 I was able to use alias addresses for the VPN tunnels with a Listen-on directive in isakmpd.conf: == [General] Listen-on= 1.2.3.7 == So far my attempts with IKEDv2 have been unsuccessful at using alias addresses. Is it possible? Thanks!

Re: unexpected behavior

Was wondering if I wanted such an interface for management purposes, that is - unconnected during normal installed operation but accepting dhcp assignment when connected - could it be placed in a different domain (not r0)? This way it should be available when needed but yet not interfere with the

Re: issue with IKEv2 setup

On Wed, Jun 3, 2020 at 1:49 PM Tobias Heider wrote: > It does. /etc/iked/pubkeys/fqdn/server2.domain is where the peer's public key > should be. The peers public key is there, the peer, as far as I can tell is server1.domain, yet the example shows server2.domain.

issue with IKEv2 setup

Following the FAQ at https://www.openbsd.org/faq/faq17.html I ran into the following problem with the server2 example: === ikev2 'server2_rsa' active esp \ from 10.0.2.0/24 to 10.0.1.0/24 \ peer 192.0.2.1 \ dstid server2.domain

Re: unexpected behavior

Thanks! On Tue, Jun 2, 2020 at 10:48 AM Anders Andersson wrote: > > On Tue, Jun 2, 2020 at 4:30 PM Sonic wrote: > > > > Recently discovered (snapshot form May 30) having any hostname.if > > configured for dhcp, even if unplugged and inactive, prevents the > > d

unexpected behavior

Recently discovered (snapshot form May 30) having any hostname.if configured for dhcp, even if unplugged and inactive, prevents the default gateway defined in /etc/mygate from being set. Is this normal?

Re: dhcpd and unbound on a small LAN

On Mon, Jan 6, 2020 at 9:35 AM Steve Litt wrote: > I need something like that for my situation. Two questions: > > 1) Does the preceding setup prevent anyone with a different mac address > from getting 192.168.0.68? Via dhcp, yes, it would. Unless they change their MAC address to match. They

Re: dhcpd and unbound on a small LAN

On Mon, Jan 6, 2020 at 7:27 AM Anders Andersson wrote: > ... > Every time information has to be entered twice there is room for error > and inconsistencies, so preferably this list should be automatically > generated from a simpler file, maybe /etc/hosts. No need for dual entry or messing with

Re: pflog flooded with igmp queries

On Thu, Jan 2, 2020 at 12:34 PM Otto Moerbeek wrote: > > Can't seem to find that specific info anywhere. > > see man pf.conf and then search for allow-opts I see that it says they are blocked, but nothing to indicate they are also automatically logged. Chris

Re: pflog flooded with igmp queries

On Thu, Jan 2, 2020 at 12:27 PM Sonic wrote: > I used: > block proto igmp More specifically: block drop quick proto igmp as I thought "return" would simply add extra traffic to the network. Chris

Re: pflog flooded with igmp queries

On Thu, Jan 2, 2020 at 1:00 AM Sebastien Marie wrote: > And by default, packets > with ip-options are block-logged. Can't seem to find that specific info anywhere. > I suppose that adding an explicit rule with allow-opts should do the trick. > depending your need (block or allow): >

Re: pflog flooded with igmp queries

Ralink 802.11 n WLAN" rev 2.00/1.01 addr 3 run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address 00:25:d3:9b:fb:db vscsi0 at root scsibus2 at vscsi0: 256 targets softraid0 at root scsibus3 at softraid0: 256 targets root on sd0a (942874cb9f340f4f.a) swap on sd0b dump on sd0b inteldrm

pflog flooded with igmp queries

The pflogs on my firewall and on a new system I'm installing (-current with pretty much a default pf.conf) are flooded with igmp query entries. Neither system has a log rule for such action. Ex: === rule 1/(match) pass in on em1: 192.168.1.20 > 224.0.0.1: igmp

Re: VPN over alias address

Adding the route to other side network from the alias address does work: route add 192.168.99.0/24 50.79.22.45 On Sun, Oct 21, 2018 at 1:58 PM Sonic wrote: > > On Mon, Oct 15, 2018 at 7:17 PM Stuart Henderson wrote: > > The problem is _not_ that your source address is 50.79.22.41,

Re: VPN over alias address

On Mon, Oct 15, 2018 at 7:17 PM Stuart Henderson wrote: > The problem is _not_ that your source address is 50.79.22.41, > because it wouldn't work with 50.79.22.45 either, you need to be > using an address that is covered by the flows (say 192.168.55.1). > > Try "ping -I $source_ip $dest_ip" with

Re: VPN over alias address

On Mon, Oct 15, 2018 at 5:09 PM Johan Hattne wrote: > Not sure I’m understanding your question, but is this not > application-dependent? So for an internal interface mec0 and ssh, you could, > > $ ssh -B mec0 f...@example.com > > and for ping, > > $ ping -I mec0 example.com The addresses

VPN over alias address

Have setup a site-to-site VPN using alias addresses which works fine for systems inside the network, however, when attempting to connect from the routers themselves to the remote network the fact that they use the default address on the external interface and not the chosen alias address appears

Re: Equipment for OBSD based firewall

How does the Edgerouter compare in performance to an Atom 2358/2558 based system? Especially interested in firewall performance using site-to-site VPN's. On Mon, Sep 3, 2018 at 8:01 PM Jordan Geoghegan wrote: > > On 09/03/18 16:17, Bogdan Kulbida wrote: > > Ladies and gentlemen, > > > > I need

Re: Unsetting a DHCP option in dhcpd.conf(5)

I suspect you can use groups, set it for a group and leave it out of another group. On Tue, Feb 27, 2018 at 12:55 PM, Grzegorz Kowalczyk wrote: > Hi, > > can an option be unset in a host declaration of dhcpd.conf(5)? > > I'm trying to set a generic "option routers

Re: pf integration with dhcpd

On Fri, Oct 27, 2017 at 2:48 PM, Carlos Cardenas wrote: > On a 6.2-syspatch box, I wanted to start leveraging the pf integration dhcpd > pfctl -t dhcpd_X -T show Do you see the current leases in "/var/db/dhcpd.leases"? A "reserved" address would not show up there, nor

Re: tmpfs

On Tue, Aug 2, 2016 at 3:13 PM, Theo de Raadt wrote: > I see you have selected only the parts of my reply which suit you. > > The rest of my reply clearly stated we don't have people to do the > work you want. > >> I doubt I'm the only non-developer who counts on that file to

Re: tmpfs

On Tue, Aug 2, 2016 at 9:42 AM, Theo de Raadt wrote: > Whoa. You haven't read the first paragraph of current.html, let me > include it here: > > Active OpenBSD development is known as the -current branch. These > sources are frequently compiled into releases known as

Re: tmpfs

I don't know why this thread got out of hand. But, as the OP I really had just two points. One was that, like myself, there may have been many others using tmpfs (due to the upbeat announcement of its inclusion). And that two, there was no indication of its removal in the "following -current" faq,

tmpfs

I remember a bit of fanfare when tmpfs was enabled in OpenBSD - http://undeadly.org/cgi?action=article=20131217081921 and at the time switched from using mfs to tmpfs. At the time it appeared that tmpfs solved some mfs issues. It seems we've come full circle and noticed during a perusal of the cvs

internet connection issues

Have a client whose Internet connection is less then reliable. It's cable service and the cable company always claims there is nothing wrong on their end. Of course the service is intermittent and by the time the onsite clerk calls the ISP it's usually back up and always by the time they get

sendsyslog error 57

Running -current (OpenBSD 6.0-beta (GENERIC.MP) #7: Wed Jun 1 10:21:47 EDT 2016) the following gets logged on every boot: sendsyslog: dropped 3 messages, error 57 Chris

Re: ntpd tries to connect via ipv6

On Tue, May 31, 2016 at 1:04 PM, Stefan Wollny wrote: > I asked this just last week. Indeed! Sorry I missed it. Thanks all!

ntpd tries to connect via ipv6

Getting many such log entries: === May 31 08:53:34 stargate ntpd[5702]: tls connect failed: 2607:f8b0:4009:808::2004 (www.google.com): connect: No route to host May 31 09:08:35 stargate ntpd[15803]: tls connect failed: 2607:f8b0:4009:808::2004 (www.google.com): connect: No

Re: Supermicro X11SSL-F freezes probing USB 3

On Tue, Mar 29, 2016 at 5:55 PM, Stuart Henderson wrote: > Make sure it's set to stop redirecting after boot in BIOS, then when > you hit the boot-loader, you should be able to 'stty com0 ' and > 'set tty com0'. Ahha! Who would have thought... com0 was the ticket. Thanks

Re: Supermicro X11SSL-F freezes probing USB 3

On Tue, Mar 29, 2016 at 9:13 PM, Paul B. Henson wrote: > Hmm, that sounds broken. Are you sure you've got the right serial port > and baud rate? Once you switch the boot loader to serial, it's no longer > a matter of "forwarding", it's direct serial access as far as the >

Re: Supermicro X11SSL-F freezes probing USB 3

On Tue, Mar 29, 2016 at 6:15 PM, Paul B. Henson wrote: > stty com1 115200 > set tty com1 Yes, tried that with no luck, SOL still stops forwarding. The box does have a physical serial port, so I ordered a serial to USB adapter cable (don't have any other systems left with serial

Re: Supermicro X11SSL-F freezes probing USB 3

On Mon, Mar 28, 2016 at 9:48 PM, Paul B. Henson wrote: > I'm installing via an IPMI virtual serial port so the lack > of keyboard isn't really an issue for me, Unfortunately that option isn't available for me. The IPMI SOL on this Dell stops forwarding the console once the system

Re: Supermicro X11SSL-F freezes probing USB 3

On Mon, Mar 28, 2016 at 9:48 PM, Paul B. Henson wrote: > Could I trouble you to be more specific as to the duration of "long > enough" :)? I think my patience ran out after about 15-20 minutes. I think it was just around that - 15 or 20 minutes, but I really didn't time it. I had

Re: Supermicro X11SSL-F freezes probing USB 3

On Mon, Mar 28, 2016 at 2:36 PM, Sonic <sonicsm...@gmail.com> wrote: > Exact same problem here with a Dell PowerEdge R230 and snapshot > downloaded today. If I wait long enough the install will finally finish booting but the keyboard (no ps2 ports) doesn't work. Disabling xhci via

Re: Supermicro X11SSL-F freezes probing USB 3

On Mon, Mar 7, 2016 at 12:48 AM, Paul B. Henson wrote: xhci probe won > xhci0 at pci0 dev 20 function 0 "Intel 100 Series xHCI" rev 0x31: msi probing for usb* usb probe returned 1 usb probe won > usb0 at xhci0: USB revision 3.0 probing for uhub* uhub

Re: mongodb

On Fri, Nov 22, 2013 at 5:18 PM, Chris Smith wrote: > Wondering if mongodb is operational with -current? Reviving old thread. Mongodb, yes, no? Thanks, Chris

Re: ftp-proxy man page out of date?

On Mon, Jan 4, 2016 at 1:04 PM, Jason McIntyre wrote: > these are dynamically inserted rules. and they must be > redirects. so you don't have to change them. divert-to > would be incorrect. Divert-to is the proper way to send the packets to the

Re: High interrupt load using 5.8 Release GENERIC i386 on Acer Aspire 3630 laptop

No clue if it's related but I recently built a new firewall with a Supermicro SYS-5018A-MLTN4 and see an unusually high interrupt load (none of my other systems have exhibited this issue). load averages: 0.08, 0.12, 0.10 firewall.example.com 14:59:42 38 processes: 37

pax: pledge: Invalid argument

-current not building: ./icdb.h -> ./icdb.ph pax: pledge: Invalid argument *** Error 1 in gnu/usr.bin/perl (Makefile.bsd-wrapper:112 'install') *** Error 2 in gnu/usr.bin (:48 'realinstall') *** Error 2 in gnu (:48 'realinstall') *** Error 2 in . (:48 'realinstall') *** Error 2 in /usr/src

Re: pax: pledge: Invalid argument

On Mon, Dec 7, 2015 at 2:41 PM, Theo de Raadt wrote: > Your mistake. Yes, my mistake. Sorry for the noise.

Re: serious watchdog timeout issues with em driver

On Fri, Nov 20, 2015 at 8:12 AM, Martin Pieuchot wrote: > I just committed a revert to 1.305 keeping the API changes needed for > the driver to build. > > This should bring your stability back, please let us know if that's not > the case. The kernel/driver builds with those

Re: serious watchdog timeout issues with em driver

On Fri, Nov 20, 2015 at 12:37 PM, Mark Kettenis wrote: > Thanks Martin. All is fine now. System booted with no errors and no watchdog timeouts. Thanks to all. Chris

serious watchdog timeout issues with em driver

Have serious problems for over 7 weeks now with em driver, specifically any rev of if_em.c > 1.305. Starting with rev 1.306, released on 2015/09/30 and continuing to -current, watchdog timeouts rue the day. Unfortunately rev 1.305 no longer builds with -current as it appears the patch in rev

Re: em(4) watchdog timeouts

On Wed, Nov 11, 2015 at 9:20 AM, Gregor Best wrote: > I've done some further testing and I think I've narrowed it down to the > "Unlocking em(4) a bit further"-patch [0]. That was the start of it for me. When I could revert to rev 1.305 for if_em.c and rev 1.57 for if_em.h

Re: dhcpd exiting with strange error message.

On Sun, Nov 8, 2015 at 3:35 PM, Jeremy wrote: > No I only have one instance running. > > # ps aux | grep dhcp > _dhcp 7784 0.0 0.1 756 1340 ?? Ss 9:00AM0:00.00 > /usr/sbin/dhcpd em0 Interesting a bit that the log shows two different PID's - it changes

Re: em(4) watchdog timeouts

On Wed, Nov 4, 2015 at 2:51 PM, Sonic <sonicsm...@gmail.com> wrote: > Is there anything else I can provide to assist in finding a cure for this > issue? Not sure this helps at all but the specific error I get is "em0: watchdog timeout -- resetting". In this case em0 is t

Re: em(4) watchdog timeouts

On Mon, Nov 2, 2015 at 11:19 PM, Sonic <sonicsm...@gmail.com> wrote: > Sorry to report that the diff does not solve the timeout problem here. > > All was working fine with the if_em* versions from 2015/09/29 (I > downgraded to this version per Stuarts post on 10-14): > &quo

Re: /bsd: em0: watchdog timeout -- resetting

On Mon, Oct 5, 2015 at 10:41 AM, Theo de Raadt wrote: >> On Sun, Oct 4, 2015 at 12:00 PM, Stuart Henderson >> wrote: >> > I'm hoping it isn't this, but please try backing out the last commits to >> > if_em.c and if_em.h ("cd /sys/dev/pci; cvs up -D

Re: crash with -current

On Mon, Nov 2, 2015 at 12:19 PM, Martin Pieuchot wrote: > Do you have an idea how to reproduce this crash? Which program are you > running that uses bpf? Not using bpf at all (that I know of), just a straightforward firewall - pf, dhcpd, unbound. The nasty little "em0:

Re: Watchdog timeouts with em on recent snapshots

On Sun, Nov 1, 2015 at 12:11 PM, Gregor Best wrote: > I just upgraded one of my routers to todays snapshot and I'm seeing > > em0: watchdog timeout -- resetting I'm seeing these again (reported on 10-4-15) after upgrading to -current. Chris

Re: em(4) watchdog timeouts

On Mon, Nov 2, 2015 at 3:29 PM, Gregor Best wrote: > On Mon, Nov 02, 2015 at 08:11:30PM +0100, Mark Kettenis wrote: >> Can those that are experiencing watchdog timeouts check if the diff >> below gets rid of them? >> [...] Hello, For whatever reason I see this reply but not

Re: em(4) watchdog timeouts

On Mon, Nov 2, 2015 at 2:11 PM, Mark Kettenis wrote: > Can those that are experiencing watchdog timeouts check if the diff > below gets rid of them? Sorry to report that the diff does not solve the timeout problem here. All was working fine with the if_em* versions from

crash with -current

Upgraded -current earlier today, and system has crashed: = Nov 1 22:23:55 stargate /bsd: uvm_fault(0x818f9920, 0xfff7818adf60, 0, 1) -> e Nov 1 22:23:55 stargate /bsd: fatal page fault in supervisor mode Nov 1 22:23:55 stargate /bsd: trap

error compiling -current kernel if_em.c

Hello, I'm getting this error during -current kernel compile, x64: ci/if_em.c cc1: warnings being treated as errors ../../../../dev/pci/if_em.c: In function 'em_ioctl': ../../../../dev/pci/if_em.c:674: warning: implicit declaration of function 'arp_ifinit' *** Error 1 in

Re: error compiling -current kernel if_em.c

it was due to the fact that I backed out revision 1.305 that caused annoying watchdog timeouts and loss of network connectivity with em0 earlier this month ok now, thanks On Sat, Oct 31, 2015 at 5:52 PM, Ossi Herrala <oherr...@gmail.com> wrote: > On Sat, Oct 31, 2015 at 05:00:51PM -04

Re: syslogd: Syscall 28 (SYS_sendmsg) in 18 October (i386) snapshot

On Sun, Oct 18, 2015 at 3:22 PM, Scott Vanderbilt wrote: > Another pledge(2) related issue, this time in syslogd. No clue if my bug is related. Attempting to upgrade -current today and I get: Oct 18 14:29:39 stargate /bsd: ksh(4880): syscall 131 Oct 18 14:29:46 stargate

Re: requesting help working around boot failures with supermicro atom board

On Mon, Oct 5, 2015 at 1:18 PM, dewey.hyl...@gmail.com wrote: > but their non-support of this brand-new motherboard When the other OS's work fine is does seem to point to an OpenBSD issue, but that's not always a reliable conclusion to arrive at. Either way it would be

Re: /bsd: em0: watchdog timeout -- resetting

t ids uhid0 at uhidev3 reportid 1: input=1, output=0, feature=0 uhid1 at uhidev3 reportid 2: input=1, output=0, feature=0 uhid2 at uhidev3 reportid 3: input=3, output=0, feature=0 vscsi0 at root scsibus2 at vscsi0: 256 targets softraid0 at root scsibus3 at softraid0: 256 targets root on s

Re: /bsd: em0: watchdog timeout -- resetting

On Sun, Oct 4, 2015 at 12:00 PM, Stuart Henderson wrote: > I'm hoping it isn't this, but please try backing out the last commits to > if_em.c and if_em.h ("cd /sys/dev/pci; cvs up -D 2015/09/29 if_em*") to > see if it makes a difference. Same issue here. Reverting now and

Re: /bsd: em0: watchdog timeout -- resetting

On Mon, Oct 5, 2015 at 10:54 AM, Josh Grosse wrote: > I'm using the em(4) NIC as a vlandev, which may be a contributing factor. Nothing special here, using OpenBSD as a simple IPV4 firewall/router, no VLAN's etc. Last -current update was on the 3rd (October) and it

Re: requesting help working around boot failures with supermicro atom board

Any progress on this issue? On Thu, Sep 17, 2015 at 1:26 PM, Mike Larkin wrote: > On Thu, Sep 17, 2015 at 12:40:12PM +, Dewey Hylton wrote: >> Dewey Hylton gmail.com> writes: >> >> > >> > Mike Larkin azathoth.net> writes: >> > >> > > >> > > On Tue, Sep 15, 2015 at

  1   2   >