Matthias Andree said:
> On Tue, 16 Sep 2003, James Yonan wrote:
>
> > While I do believe that the majority of Windows users will prefer a tap
> > interface, I say this simply because in my experience _most_ Windows users
> > prefer the option that is the easiest to configure. Once you stop
> >
On Tue, 16 Sep 2003, James Yonan wrote:
> While I do believe that the majority of Windows users will prefer a tap
> interface, I say this simply because in my experience _most_ Windows users
> prefer the option that is the easiest to configure. Once you stop
> automatically routing broadcasts and
On Tue, 16 Sep 2003, James Yonan wrote:
> > I'd like to challenge the "better" claim:
>
> I mean "better" only in the sense of simpler configuration -- i.e. not needing
> to set up a WINS server to make cross-subnet browsing work. I agree that tun
> is more scalable, secure, etc.
After being th
Matthias Andree said:
> On Mon, 15 Sep 2003, James Yonan wrote:
>
> > Yes, this is a problem. For OpenBSD to talk to Windows over OpenVPN, we
> > need
> > either a tun driver for Windows or a tap driver for OpenBSD.
> >
> > My guess is that the easier and better solution would be to solve the
On Mon, 15 Sep 2003, James Yonan wrote:
> Yes, this is a problem. For OpenBSD to talk to Windows over OpenVPN, we need
> either a tun driver for Windows or a tap driver for OpenBSD.
>
> My guess is that the easier and better solution would be to solve the tap on
> OpenBSD problem, rather than th
