Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 2 subscribers
  • Views 2080 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 proxy problem after upgrade to 8.302

Robein
Hi,

i've upgraded our Astaro to version 8.302 from version 8.203 and it seems that the upgrade has broken a part of the socks proxy functionality.

We use an application named Bloomberg which uses UDP and does not seem to be able to connect to it's servers anymore.
The socks log gives the folowing output:
2012:05:04-10:14:02 fw-1 sockd[28453]: pass(1): tcp/accept [: 192.A.A.A.8277 -> 10.15.16.1.1080
2012:05:04-10:14:02 fw-1 sockd[28454]: pass(4): udp/udpassociate [: 0.0.0.0.48129 -> 0.0.0.0.0
2012:05:04-10:14:02 fw-1 sockd[28458]: pass(4): udp/udpassociate ]: 192.A.A.A.48129 -> pdir.bloomberg.net.48129: Invalid argument
2012:05:04-10:14:11 fw-1 sockd[28458]: pass(4): udp/udpassociate ]: 192.A.A.A.48129 -> sdir.bloomberg.net.48129: Invalid argument
2012:05:04-10:14:19 fw-1 sockd[28458]: pass(4): udp/udpassociate ]: 192.A.A.A.48129 -> pdir.brin.bloomberg.net.48129: Invalid argument
2012:05:04-10:14:27 fw-1 sockd[28458]: pass(4): udp/udpassociate ]: 192.A.A.A.48129 -> sdir.brin.bloomberg.net.48129: Invalid argument
2012:05:04-10:14:35 fw-1 sockd[28458]: pass(4): udp/udpassociate ]: 192.A.A.A.48129 -> pdir.bloomberg.net.48129: Invalid argument
2012:05:04-10:14:44 fw-1 sockd[28458]: pass(4): udp/udpassociate ]: 192.A.A.A.48129 -> sdir.bloomberg.net.48129: Invalid argument
2012:05:04-10:14:52 fw-1 sockd[28458]: pass(4): udp/udpassociate ]: 192.A.A.A.48129 -> pdir.brin.bloomberg.net.48129: Invalid argument
2012:05:04-10:15:00 fw-1 sockd[28458]: pass(4): udp/udpassociate ]: 192.A.A.A.48129 -> sdir.brin.bloomberg.net.48129: Invalid argument
2012:05:04-10:15:08 fw-1 sockd[28458]: pass(4): udp/udpassociate ]: 192.A.A.A.48129 -> pdir.bloomberg.net.48129: Invalid argument
2012:05:04-10:15:16 fw-1 sockd[28458]: pass(4): udp/udpassociate ]: 192.A.A.A.48129 -> sdir.bloomberg.net.48129: Invalid argument
2012:05:04-10:15:25 fw-1 sockd[28458]: pass(4): udp/udpassociate ]: 192.A.A.A.48129 -> pdir.brin.bloomberg.net.48129: Invalid argument
2012:05:04-10:15:33 fw-1 sockd[28458]: pass(4): udp/udpassociate ]: 192.A.A.A.48129 -> sdir.brin.bloomberg.net.48129: Invalid argument

Under the socks proxy tab we only configured allowed networks containing the allowed systems on the network.

Found in the manual that DNS proxy should be enabled but i cannot seem to be able to find that option.

Can anyone help?

Rudy


This thread was automatically locked due to age.
  • 0
    Whenever something seems strange, the first place to look is in the Intrusion Prevention log - anything there related to this change in behavior?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0
    Unfortunately not. Searched in all logs for corresponding ip-adresses but all were clear.
    I've created a support ticket so hopefully tech support knows the error found in the logs.
Cookie Information Banner