For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Amit_Bhatnagar_'s avatar
Amit_Bhatnagar_
Icon for Nimbostratus rankNimbostratus
Aug 19, 2013
Solved

IPHTTPS with DirectAccess Not working with F5

I am helping a client implement DirectAccess 2012 using IPHTTPS as the Protocol. The setup is   ISP Firewall----Client Firewall------F5 (Big IP) ----DA Servers---Internal Network.   The ISP...
availability
BIG-IP Access Policy Manager (APM)
deployment
directaccess
security
  • Martijn_65080's avatar
    Martijn_65080
    Aug 19, 2013

    True Mac spoofing is not needed.

     

    I see two strange things. 1. Teredo interfaces are being enabled. Setup 2 interfaces behind edge device normally skips this step as Teredo only works with Public IPv4 addresses on the DA servers. 2. The pseudo network adapter is not getting an address assigned.

     

    What is the output of the powershell command "get-NetDnsTransitionConfiguration" ?

     

    Martijn

     

Amit_Bhatnagar_'s avatar
Amit_Bhatnagar_
Icon for Nimbostratus rankNimbostratus
Aug 19, 2013

Ok...so Loopback Pseudo-Interface 1 is the problem...It is not getting the IP now in the third server. Two are working within NLB so that is the good news. Windows8-RT-KB2859347-x64 is the key here which is a Hotfix for this issue although, is there a way by which I can fix this issue without breaking NLB? I mean reset the adapters and then let the configuration Policy assign the correct IPs and all?

 

If not then I will have to break the NLB anyways which I am keeping as the last option?