| | 1 | = Introduction = |
| | 2 | |
| | 3 | The OpenVPN management interface is used heavily by Access Server, but also by many OpenVPN clients. This page tracks the status of IPv6 support in the management interface. Much of the content here is blatantly copy-pasted from cron2's test description with only minor edits. |
| | 4 | |
| | 5 | = Current status = |
| | 6 | |
| | 7 | = What works = |
| | 8 | |
| | 9 | The status output displays IPv6 just: |
| | 10 | |
| | 11 | {{{ |
| | 12 | status 0 |
| | 13 | >LOG:1365538567,D,MANAGEMENT: CMD 'status 0' |
| | 14 | OpenVPN CLIENT LIST |
| | 15 | Updated,Tue Apr 9 22:16:07 2013 |
| | 16 | Common Name,Real Address,Bytes Received,Bytes Sent,Connected Since |
| | 17 | cron2-ithing,2001:608:4:0:c1d7:de3:555d:a36b,5710,5891,Tue Apr 9 22:10:15 2013 |
| | 18 | ROUTING TABLE |
| | 19 | Virtual Address,Common Name,Real Address,Last Ref |
| | 20 | fd12:3456:7890::/48,cron2-ithing,2001:608:4:0:c1d7:de3:555d:a36b,Tue Apr 9 22:10:15 2013 |
| | 21 | 10.0.1.0/24,cron2-ithing,2001:608:4:0:c1d7:de3:555d:a36b,Tue Apr 9 22:10:15 2013 |
| | 22 | 194.97.145.74,cron2-ithing,2001:608:4:0:c1d7:de3:555d:a36b,Tue Apr 9 22:10:15 2013 |
| | 23 | 2001:608:3:814::1000,cron2-ithing,2001:608:4:0:c1d7:de3:555d:a36b,Tue Apr 9 22:10:15 2013 |
| | 24 | GLOBAL STATS |
| | 25 | Max bcast/mcast queue length,0 |
| | 26 | END |
| | 27 | }}} |
| | 28 | |
| | 29 | = What does not work = |
| | 30 | |
| | 31 | '''NOTE:''' These should be split into tickets if we deem them important to fix. |
| | 32 | |
| | 33 | Commands ''"status 2"'' and ''"status 3"'' show a column for "Virtual Address" in the CLIENT_LIST, which only lists IPv4 (since there is just one column), but the IPv6 stuff is there in ROUTING_TABLE just fine. Is this a significant problem that needs a format change (adding one column for "Virtual Address v6")? |
| | 34 | |
| | 35 | Also, ''"kill IP:port"'' will fail for IPv6 addresses: |
| | 36 | |
| | 37 | {{{ |
| | 38 | kill 2001:608:3:814::1000:1194 |
| | 39 | >LOG:1365538844,D,MANAGEMENT: CMD 'kill 2001:608:3:814::1000:1194' |
| | 40 | ERROR: client at address 0.0.7.209:608 not found |
| | 41 | }}} |
| | 42 | |
| | 43 | The ''client-pf'' is not working, but that's larger than "management" - that PF stuff is functionality that is not in the 2.3 core at all for IPv6 yet. |
| | 44 | |
| | 45 | = What has not been tested = |
| | 46 | |
| | 47 | * All the config commands should be configurable as if configured in the local config file |
| | 48 | * the management interface itself might not bind to IPv6 sockets |
