> > Are you saying you want OpenVPN to read configuration options from a
config
> > file rather than the command line when -f is used?
> >
> > James
> >
>
> That's right. Configuration files have some advantages from my point of
> view:
> - Only one script to start/stop VPNs. A init.d-like script t
>I don't know the openvpn data format, but if 4554 is some sort of
openvtun identifier, you/we/I could add some code that checked for
0002 followed by 4554 and then strip the first u_int_32 from
the packet and go on. Perhaps a --remote-is-bsd or something similar?
Openvpn doesn't look
On Thu, 2002-04-04 at 10:46, James Yonan wrote:
> >I don't know the openvpn data format, but if 4554 is some sort of
> openvtun identifier, you/we/I could add some code that checked for
> 0002 followed by 4554 and then strip the first u_int_32 from
> the packet and go on. Perhaps a --re
On Thu, 2002-04-04 at 10:46, James Yonan wrote:
> >I don't know the openvpn data format, but if 4554 is some sort of
> openvtun identifier, you/we/I could add some code that checked for
> 0002 followed by 4554 and then strip the first u_int_32 from
> the packet and go on. Perhaps a --re
> >Yes, but since BSD wont let you choose if you want it or not, and the
> chance of changing Linux-TUN-drivers now is slim, I guess it has to be
> the application that takes care of this. I'll try to make a patch and
> test it, and send you the diff later.
>
> Some thoughts:
>
> * probably the
>I think the solution would be to have openvpn disable TUN_NO_IP for
Linux tun devices and just not care about the actual value when
the packets arrive.
So if the linux side disables TUN_NO_PI, does the problem go away when
connecting to BSD?
James
Ok, this is tested in cleartext tunnel mode, and ssl-with-preshared-key.
Both methods work if the Linux side has "--remote-bsd" on the command
line, and they do not work without it.
(Given that the remote IS bsd of course =)
Both machines were little-endian, I haven't tested BE machines yet.
(I h
Janne,
On BSD, is there any way to ioctl away the leading AF_INET, or is it
necessary to have the linux side conform to the BSD side with --remote-bsd?
>It compiles cleanly on Linux2.4 and with 2 warnings on OpenBSD3.0.
==
gcc -g -O2 -I/usr/local/inclu