vpn-slice does not tunnel IP subnets about vpn-slice HOT 4 CLOSED

Work like a charm.

Thank you very much Dan

from vpn-slice.

vpn-slice uses Python's ipaddress module to parse IP network and host addresses.

192.168.37.105/31 isn't recognized as a (canonical) IPv4 network address, nor as an IPv4 host address:

>>> import ipaddress
>>> ipaddress.ip_network('192.168.37.105/31')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3.5/ipaddress.py", line 1536, in __init__
    raise ValueError('%s has host bits set' % self)
ValueError: 192.168.37.105/31 has host bits set
>>> ipaddress.ip_address('192.168.37.105/31')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3.5/ipaddress.py", line 54, in ip_address
    address)
ValueError: '192.168.37.105/31' does not appear to be an IPv4 or IPv6 address

… which is why vpn-slice default to looking it up as a hostname.

The correct canonical address for this network would be 192.168.37.104/31. But it turns out I can get ipaddress to parse it more forgivingly, simply by adding strict=False, so I should probably do that.

>>> ipaddress.ip_network('192.168.37.105/31', strict=False)
IPv4Network('192.168.37.104/31')

from vpn-slice.

Thank you very much for prompt reply.

I will try and let you know

from vpn-slice.

I've submitted an MR to OpenConnect to sanitize/fix these incorrectly-specified IPv4 networks before sending them to the vpnc-script:

https://gitlab.com/openconnect/openconnect/-/merge_requests/97

from vpn-slice.