Hi,
On Mon, Jun 23, 2014 at 12:12:38PM +0100, David Woodhouse wrote:
> > Another side effect is that if the TAP Windows driver is being
> > initialized with 255.255.255.255 netmask then there's no way
> > to convince windows to route packets through that interface.
>
> If this isn't considered a bug in the Windows tap driver, (and I suspect
> it isn't, because they're working around some true horridness in the
> Windows network stack),
Well, for Windows, a tap interface is an ethernet interface in good
standing - and not a point-to-point thing like a tun on other platforms
where there really is no "subnet" but "my IP, and what's on the other side".
So, as you can't put 255.255.255.255 on normal ethernet interfaces, you
can't do that on the tap driver either. I'm not sure whether .254 would
work - which is why OpenVPN's net30 always wasted a /30 in the old
days, or uses a larger subnet now.
There is not very much we can do to "fix" that in the tap driver,
especially as the ifconfig is done outside the driver in the generic
IP part of the stack...
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany gert at greenie.muc.de
fax: +49-89-35655025 gert at net.informatik.tu-muenchen.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 291 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20140623/6f5f2632/attachment.sig>
