Re: Question about /etc/resolvd.conf and local resolver

On 2022-04-13, J Doe wrote: > For people reading this thread ... > > /etc/resolv.conf is the traditional file for configuring the system > resolver(s) while /etc/resolvd.conf is the configuration file for the > resolvd *daemon*, which is also involved in the configuration of the > system resolv

Re: How do I report a kernel panic occuring on install media?

On 2022-04-13, misc.99...@aleeas.com wrote: > I'm trying to boot OpenBSD 7.0 i386 image (sha256: > 2423307414df1800537063b3cafd9ae788b46711074b7f94d855c8a3de622f51) from a USB > flash drive on HP Mini, Intel Atom N2600 1.60 GHz machine. Before I could > install, unfortunately I'm facing a kerne

Re: How do I report a kernel panic occuring on install media?

On 4/12/22 9:39 PM, misc.99...@aleeas.com wrote: I'm trying to boot OpenBSD 7.0 i386 image (sha256: 2423307414df1800537063b3cafd9ae788b46711074b7f94d855c8a3de622f51) from a USB flash drive on HP Mini, Intel Atom N2600 1.60 GHz machine It sounds like you're trying to use the 32bit OpenBSD inst

Re: Question about /etc/resolvd.conf and local resolver

On 2022-03-27 07:05, Stuart Henderson wrote: On 2022-03-27, Peter J. Philipp wrote: Some fun facts about DNS. A DNS packet can be 0x hex (or 65535 bytes dec) maximally. This is true for TCP DNS packets which serve an unsigned short indicator of length before the packet segment. With UDP

re0: watchdog timeout

Hi all, I have a Realtek physical net interface in a laptop that I used as a home server: re0 at pci2 dev 0 function 1 "Realtek 8168" rev 0x12: RTL8411B (0x5c80), msi, address 08:97:98:6e:16:eb rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0 I have been plagued by by the issue: re0: watchdog timeout

Re: IKEV2 two devices can connect but only one can make traffic

Den tis 12 apr. 2022 kl 15:30 skrev Łukasz Moskała : > I remember talking with network engineer at one company I used to work at. > We used fortigate firewalls, and I asked why are we using SSLVPN instead of > ipsec-based vpn, as both were supported. > He said something along the lines of "ipsec d

Re: IKEV2 two devices can connect but only one can make traffic

Issue solved updating my linux strongswan client!!! Sorry for the trouble... Thanks to everybody 😊

Re: IKEV2 two devices can connect but only one can make traffic

On Tue, Apr 12, 2022 at 01:03:55AM +0200, Ettore Tagarelli wrote: > If I use the "dynamic keyword I get this error: "no IP address found for > dynamic" though "config address 192.168.98.1/24" is there. > Using 0.0.0.0/32 instead of 0.0.0.0/0 causes that traffic is not routed > ('cause /32 restrict

Re: IKEV2 two devices can connect but only one can make traffic

Dnia Tue, Apr 12, 2022 at 03:06:50PM +0200, Ettore Tagarelli napisał(a): > Updated to 7.0 > ...same problem 🙁 I remember talking with network engineer at one company I used to work at. We used fortigate firewalls, and I asked why are we using SSLVPN instead of ipsec-based vpn, as both were suppor

Re: IKEV2 two devices can connect but only one can make traffic

On Tue, Apr 12, 2022 at 03:06:50PM +0200, Ettore Tagarelli wrote: > Updated to 7.0 > ...same problem 🙁 What does the updated config look like? "from 0.0.0.0/0 to dynamic" should work in 7.0.

Re: IKEV2 two devices can connect but only one can make traffic

Updated to 7.0 ...same problem 🙁

Re: IKEV2 two devices can connect but only one can make traffic

On 2022-04-11, Ettore Tagarelli wrote: > If I use the "dynamic keyword I get this error: "no IP address found for > dynamic" though "config address 192.168.98.1/24" is there. > Using 0.0.0.0/32 instead of 0.0.0.0/0 causes that traffic is not routed > ('cause /32 restrict the only address possible