Home

windows server rras record other C/S address in SSTP tunnel over ipv6

%3CLINGO-SUB%20id%3D%22lingo-sub-1176609%22%20slang%3D%22en-US%22%3Ewindows%20server%20rras%20record%20other%20C%2FS%20address%20in%20SSTP%20tunnel%20over%20ipv6%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1176609%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22fdb777a8eef629692228fdbe1ad563c%20-%20Copy.png%22%20style%3D%22width%3A%20959px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F171434i379A245349FE54C8%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22fdb777a8eef629692228fdbe1ad563c%20-%20Copy.png%22%20alt%3D%22record%20wrong%20address%20in%20sstp%20over%20ipv6%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3Erecord%20wrong%20address%20in%20sstp%20over%20ipv6%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EWe%20can%20see%20that%20Client%2FServer%20ipv6%20addresses%20in%20RRAS%20MMC%20console%20are%20not%20the%20same%20with%20netstat%20log.%3C%2FP%3E%3CP%3EIn%20rras%20SSTP%20mode%2C%20client%20connect%20to%20server%20port%20443%2Ftcp.%3C%2FP%3E%3CP%3EUsing%20packet%20capture%20tool%20such%20as%20wireshark%2C%20I%20found%20netstat%20tells%20the%20right%20address.%3C%2FP%3E%3CP%3EWhy%20RRAS%20mmc%20console%20print%20strange%20C%2FS%20addresses%2C%20with%20the%20same%20ipv6%20prefix%20%2F64%20as%20the%20netstat%20answer.%3C%2FP%3E%3CP%3ERadius%20auth%2Faccounting%20records%20are%20the%20same%20with%20rras%20mmc%20console.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20same%20problem%20found%20in%20windows%20server%202016.%3C%2FP%3E%3CP%3EWhen%20switch%20to%20IKEv2%20tunnel%20mode%2C%20addresses%20in%20MMC%20are%20the%20same%20with%20netstat.%3C%2FP%3E%3CP%3EThe%20problem%20was%20not%20found%20in%20ipv4%20tunnel.%3C%2FP%3E%3CP%3EDirectAccess%20feature%20is%20not%20enable.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20this%20C%2FS%20addresses%20transform%20a%20feature%3F%20What%20for%3F%26nbsp%3BMaybe%20Directaccess%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1176609%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Eipv6%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Errasvpn%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esstp%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

record wrong address in sstp over ipv6record wrong address in sstp over ipv6

We can see that Client/Server ipv6 addresses in RRAS MMC console are not the same with netstat log.

In rras SSTP mode, client connect to server port 443/tcp.

Using packet capture tool such as wireshark, I found netstat tells the right address.

Why RRAS mmc console print strange C/S addresses, with the same ipv6 prefix /64 as the netstat answer.

Radius auth/accounting records are the same with rras mmc console.

 

The same problem found in windows server 2016.

When switch to IKEv2 tunnel mode, addresses in MMC are the same with netstat.

The problem was not found in ipv4 tunnel.

DirectAccess feature is not enable.

 

Is this C/S addresses transform a feature? What for? Maybe Directaccess?