Is Anyone Able to Post from Behind Untangle?
-
@scottalanmiller said:
Specifically here in MangoLassi. We've had so many reports that posting from behind an Untangle device just does not work. Is there anyone with an example of it actually working? I am unaware of anyone having gotten this to work.
Untangle is suspected of mangling the ioSocket traffic causing the problem.
No idea here.
-
I can view but not post from behind a watchguard at one client. I do not manage it though so cannot test.
-
@JaredBusch said:
I can view but not post from behind a watchguard at one client. I do not manage it though so cannot test.
That's what I've heard about both Watchguard and Untangle. My guess is that both are mangling Socket.io calls in the same way.
-
-
Just found another Watchguard user that can't access the site. That reinforces that quite a bit.
-
Testing!
-
-
Testing a second time.
-
Seems the proxy on the Watchguard makes things a bit wonky. I just created a simple packet filter to pass traffic from my ip to the mangolassi ip and BAM. Now things work.
Just to clarify, we pass http/https traffic though a proxy. I am not sure if its the ripping apart/reassembly or the application control or something else that is causing the problem. I figure it was just as easy to not let that crap touch the traffic and let it pass though. My assumption ended up being correct.
-
Thanks for testing and great to finally have you able to join us!
-
Just what I need, another "tool" to distract, me!
-
@g.jacobse installed Untangle yesterday and was instantly cut off from ML.
-
I can at least read ML - I'm determined to find an answer,..
-
It is definitely something with the web sockets stuff on the Watchguard series firewalls. I can read and even sign in (most of the time). But the notifications and unread counters never update right. As well as being unable to post.
-
On suggestion - Turned off all the UT Rack items other than Firewall...
Able to read, and post to ML. Chat and notifications work. Now to go back and find out WHY -
-
Turn them back on one by one to identify which one it is. Chances are it is a proxy.
-
I have, I've cycled through all the modules -
-
Web Filter Lite
*Added site to pass list - did not allow. -
Virus Blocker Lite
*Added site to pass list - did not allow. -
Intrusion Prevention
-
Ad Blocker
-
Not currently used or active:
Application Control
Captive Portal
Variations of the the above doesn't seem to matter - they all block that level of access to ML. The only modules running right now are:
- Spam Blocker
- Phish Blocker
- Firewall
- Reports
Still researching.
-
-
Created two ByPass rules
Source with 162.242.243.171
Destination with 162.242.243.171Able to access / post / etc.
Of course - all that does is bypass it.. Pretty sure I'm looking another option..
-
Everyone seems to have to bypass the proxy stage to get it to work.
-
Seems like the latest forum update has resolved this issue.
