Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 2306 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

Ssl vpn

strayduck
Hi all
 
I am getting the below errors on firewall when using SSL VPM
 
"MULTI: bad source address from client xx.xx.xx.xx(pc ip address), packet dropped"

Anyone know how to resolve issue?  Is it something to do with routing tables on laptop?
 
Many Thanks
 
Hayley


This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to Jack Daniel
    Are the local and remote IP address spaces the same or overlapping (such as 192.168.0.0/24 at each end)?  Traffic will not flow in this case and could lead to IP address duplication and conflicts.


    I'm seeing a lot of this too.

    userx/x.x.x.x:43693 MULTI: bad source address from client [y.y.y.y], packet dropped 

    x.x.x.x = users public IP.
    y.y.y.y = users private IP behind their firewall.
    They are no where near overlapping.

    Any suggestions?
  • 0 in reply to tdubb5
    One of my customers is seeing this too... we have a case open with Astaro, we'll see what they come up with.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • 0 in reply to BrucekConvergent
    What about the SSL VPN pool? Has that definition been changed? Make sure the same network range isn't used for the SSL pool, and another vpn pool as well. And make sure that no interface network ranges are used as the ssl vpn pool (i.e. the Internal(network) definition)
  • 0 in reply to crashtestdummy
    What about the SSL VPN pool? Has that definition been changed? Make sure the same network range isn't used for the SSL pool, and another vpn pool as well. And make sure that no interface network ranges are used as the ssl vpn pool (i.e. the Internal(network) definition)


    Not in my case.  Only one VPN pool and pool is a seperate subnet from any of the ones on the interfaces.  It's seeing the users local IP address and not thier vpn address based on the messages.
Cookie Information Banner