Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 2 subscribers
  • Views 1409 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

SOCKS IP address

Kemela
according to the known issues list (ASL 3.2), the SOCKS proxy may select the wrong outgoing source IP address..   Does this affect the proxy's normal operation, or is it generally a 'cosmetic' issue?

I would like to use several IPs on the ASL 3.2 external interface, with SOCKS proxy, but would it work?


This thread was automatically locked due to age.
Parents
  • 0
    Hmm.. To answer my own question, in case someone here is interested.

    According to Astaro, there will be a newer release of ASL3.2 that would address at least part of this issue (i.e. SOCKS proxy taking on incorrect IP address).  I don't have a firm date on this, but hopefully it will be soon.

    Let me know if anyone has any other info about this.
  • 0 in reply to Kemela
    In the recently announced 3.202 there is an appropriate fix for this issue. In fact, taking the wrong IP could kill your connection request e.g. if there is a dmz interface with a private network IP and socks will use this IP for outgoing traffic, your packets will never return   [:(] 

    Note: This behavior is(was) possible - not general!
Reply
  • 0 in reply to Kemela
    In the recently announced 3.202 there is an appropriate fix for this issue. In fact, taking the wrong IP could kill your connection request e.g. if there is a dmz interface with a private network IP and socks will use this IP for outgoing traffic, your packets will never return   [:(] 

    Note: This behavior is(was) possible - not general!
Children
No Data