I have made some diffs to make it compile under OpenBSD 3.0.
This does not mean that I have tested it remotely yet, since I'm still
at the "more README" stage on openvpn, but I know my way around
makefiles and includes. =)
In short, the diff fixes these things:
* NULL is already defined on my op
I have now pinged between linux2.4 with openvpn1.0.3 and openbsd3.0
running the version that comes out of my diff.
There is need for a small readme, since ifconfig differs on bsd
but apart from that, everything went smoothly after some initial
mistesting on my part. =)
It was done on an unencrypte
Either I failed before, or something happened during my tests.
My success-mail might have been a bit premature, since I can't
get it to work now at all. One of the machines is the def-gw of
the other usually, so I might have mis-configured it to not use
the tunnel somehow. 8-(
I was about to test
Sorry for "spamming" so much with my porting issues.
Now it seems that BSD (at least Free/OpenBSD) TUN devices send AF_INET
as a u_int32_t in network byte order first, which Linux tun-devs
dont.
That's why my last mail contains sending of "0002" as the first
32 bits, it's telling the other en
>Sorry for "spamming" so much with my porting issues.
Hey, I think it's great you're trying to port it! Post as much as you want.
>Now it seems that BSD (at least Free/OpenBSD) TUN devices send AF_INET
as a u_int32_t in network byte order first, which Linux tun-devs
dont.
Interesting. We shoul
On Wed, 2002-04-03 at 00:44, James Yonan wrote:
> >Sorry for "spamming" so much with my porting issues.
>
> Hey, I think it's great you're trying to port it! Post as much as you want.
>
> >Now it seems that BSD (at least Free/OpenBSD) TUN devices send AF_INET
> as a u_int32_t in network byte ord
