Re: installing openbsd on raspberry pi 4

Hello, I'm not Sure but shouldn't it be cd: /mnt/usr/share/zoneinfo instead of: cd: /mnt/user/share/zoneinfo ? regards Am 13. September 2021 15:48:02 MESZ schrieb Sandeep Gupta : >Hello, > > I am stuck on installing openbsd 6.8 (or 6.9) on rpi 4. I am able to >boot the openbsd installer off

Re: ipsec with default route and routing of internal networks

On 2021-09-13, Hrvoje Popovski wrote: > On 13.9.2021. 14:08, Tom Smyth wrote: >> Can you do  an exception for the ranges ...  so internet - private ips >> you dont want over the tunnel) >> >> ike esp from 10.90.0.0/24 to any encrypt   >> and  >> >>  10.90.0.0/24

installing openbsd on raspberry pi 4

Hello, I am stuck on installing openbsd 6.8 (or 6.9) on rpi 4. I am able to boot the openbsd installer off of USB drive using UEFI boot loader (on sd card). However the installer fails at the step "What timezone are you in?". It doesn't like any timezone I input. Just before this step I get

Re: Why is tmpfs not working on OpenBSD?

On Wed, Sep 08, 2021 at 09:54:52AM -0700, Chris Bennett wrote: > On Mon, Sep 06, 2021 at 12:44:59AM +, iio7 wrote: > > > > Why isn't it removed? It is kinda "misguiding". > > > > > > Shucks, you must feel terrible about our decision. > > > > Well, compared to the fact that you, back in 2016,

Re: ipsec with default route and routing of internal networks

On 13.9.2021. 14:08, Tom Smyth wrote: > Can you do  an exception for the ranges ...  so internet - private ips > you dont want over the tunnel) > > ike esp from 10.90.0.0/24 to any encrypt   > and  > >  10.90.0.0/24 to   NOT  [networks you dont want >

Re: ipsec with default route and routing of internal networks

Can you do an exception for the ranges ... so internet - private ips you dont want over the tunnel) ike esp from 10.90.0.0/24 to any encrypt and 10.90.0.0/24 to NOT [networks you dont want over the tunnel) ? On Mon, 13 Sept 2021 at 13:02, Hrvoje Popovski wrote: > Hi, > > On 13.9.2021.

Re: ipsec with default route and routing of internal networks

Hi, On 13.9.2021. 12:58, Tom Smyth wrote: > Hi Hrvoje,  > > is 10.90.0.0/24 local to your firewall, and if I > understand your rule, > ike esp from 10.90.0.0/24  to any    you are saying   > encrypt all traffic comming from 10.90.0.0/24

Re: ipsec with default route and routing of internal networks

Hi Hrvoje, is 10.90.0.0/24 local to your firewall, and if I understand your rule, ike esp from 10.90.0.0/24 to anyyou are saying encrypt all traffic comming from 10.90.0.0/24 should the tunnel be more specific ? like from 10.90.0.0/24 to another network across the tunnel ike esp from

Re: OpenSMTPd: Ignoring /etc/hosts file?

> do you have "lookup file bind" record in your /etc/resolv.conf file? This option is not available in the current debian version. And I have to admit I have no clue what did the dns resolving. NetworkManager was disabled, systemd-resolved was disabled, ... Changes to the /etc/resolv.conf file

Resolved: OpenSMTPd: Ignoring /etc/hosts file?

I managed to resolve this issue with some strange workaround. I must confess, I dont exactly know which service was handling DNS before, as NetworkManager and systemd-resolved were both disabled. /etc/resolv.conf was overwritten by each DHCP request. So I did the following. I configured

ipsec with default route and routing of internal networks

Hi all, I have a firewall that routes few internal networks, 10.90/24, 10.91/24, 10.92/24. And i have some static routes to other firewalls, but i don't think that is relevant to this problem. For network 10.90/24 i have ipsec tunnel, and i need to push any traffic from that network to the

Re: OpenSMTPd: Ignoring /etc/hosts file?

do you have "lookup file bind" record in your /etc/resolv.conf file? On Mon, Sep 13, 2021 at 10:20:30AM +0200, Simon Hoffmann wrote: > > > > Has been reported previously - > > https://github.com/OpenSMTPD/OpenSMTPD/issues/1115 > > Thanks for the link, this did not come up in my searches. > >

Re: OpenSMTPd: Ignoring /etc/hosts file?

> Has been reported previously - > https://github.com/OpenSMTPD/OpenSMTPD/issues/1115 Thanks for the link, this did not come up in my searches. However, > The link also contains a workaround which may be useful for you. the only "workaround" I could find was to specify the internal IP

Re: npppd - changing clients' route table

On 2021-09-12, Radek wrote: > Sorry for the late reply, adding ":framed-ip-netmask=255.255.255.0:" doesn't > solve the problem. Tested on Win10. framed-ip-netmask controls addition of the route on the npppd machine, not the client. You only use it if you have multiple addresses behind one VPN