At a guess, route-to is confused by the same ip, but I haven't looked at the
internals.
Maybe try adding pair interfaces (with different addresses) to each rdomain,
and you can use route-to to select between them.
You already have default route set in each rdomain, so it will find its way
from
On 2016-12-06 12:05, Robert Szasz wrote:
I'm trying to set up an L2TP/IPSEC tunnel for roaming windows users to
tunnel in to our office network.
I'm testing with the following setup
Win10 ->obsd5.9(firewall doing nat)->{}->obsd5.9(IPSEC)
Windows needs a registry entry set for L2TP and IPSEC
Hi,
When using 'udpsockmode' in dhcpd (-u flag), it first calls
pledge("stdio rpath inet sendfd proc id", NULL) (in udpsock.c)
then tries
pledge("stdio inet route sendfd", NULL) (back in dhcpd.c)
The "route" causes it to fail.
eg.
$ doas dhcpd -u -fd pppx0
Listening on 255.255.255.255:67/udp.
d
be a minimal patch, and
would solve most of the problem. Then the options could be done in a
couple of steps.
--
Philip Higgins
ing state.
>
> This is how I got OpenBSD 4.5 working:
>
> http://scie.nti.st/2009/10/4/running-openbsd-4-5-in-kvm-on-ubuntu-linux-9-04
>
FWIW, this procedure works for 4.6 on Xen as well. The issue is probably
somewhere in the common QEMU code.
--
Philip Higgins
sending a
release packet every half hour, but it was really a renew packet.
I know I can just grab the latest code from tcpdump.org and build it,
but what's the best way to get this updated in tree?
Thanks
Philip Higgins
6 matches
Mail list logo
