3CX DLL-Sideloading attack: What you need to know

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 28 subscribers
  • Views 891 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

VPN > VLANS Not Working

Stephen Martin

Hi all,

Hope someone can point me in the right direction as loosing it. 

I have just setup x3 VLANS on Port1 (LAN) which then goes to the switches then onto devices. This is all working fine internally and can hit 10.10.40.50 (VLAN 40) from 10.10.10.10.1 (Default)

But for some reason I can't get to the 10.10.40.0 range when on VPN, I have checked all rules and nothing seems to make sense why it isn't working. 

Thanks in advance



This thread was automatically locked due to age.
  • 0

    Just to add, when adding in a route on my machine to the VLAN range it works. On the log file it doesn't seem to be adding the routes in the config file only 3 of them.

  • 0 in reply to Stephen Martin

    Do you add all the networks to the VPN-Configuration?

    Do you use SSL- or IPSec VPN?

    Which client-version?


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

  • 0

    When you configure VLANs, you should add them to the VPN configuration. In a Site-To-Site scenario, Network ranges (VLANs) need to be allowed in both VPN configuration and Rules.

  • 0

    So after messing around more. And adding in manual routes on my machine through the VPN interface. When connecting it wasn’t adding in the new Vlan routes. There is a bug in the version of XB we are using which requires you to change any setting in the VPN settings which will restart the service. After that boom works fine. 

    Cheers

Unfiltered HTML