- Pulse Secure Community
- :
- About gr_stanley
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
since
11-29-2012
10-30-2017
gr_stanley
Occasional Contributor
8
Posts
0
Kudos
1
Solution
01-16-2014
11:31:AM
Thank you! Seems so obvious now, but I must have missed it when looking for it.
... View more
01-06-2014
03:11:PM
Surely someone must have needed to do this before?
... View more
01-03-2014
04:12:PM
Hi... this is not actually for the functionality of the traffic manager itself, but rather the management interface of it. When I connect to https:// <server_IP>:9090, I get the warning for a self-signed SSL certificate. How do I change it to use a proper SSL certificate? Thanks!
... View more
10-31-2013
11:53:AM
We've managed to get this sorted out. The rule was properly defined, just not case sensitive.
... View more
10-24-2013
04:48:PM
We're trying to do the following, but it doesn't seem to be working. We have a Virtual Server "VS" with Default Traffic Pool "DEFAULT-POOL". "DEFAULT-POOL" consists of three nodes: 10.0.0.1:80 10.0.0.2:80 10.0.0.3:80 "VS" has a rule "RULE" defined as: Condition: If URL Path starts with "/EXCEPTION/" Action: Choose Pool "EXCEPTION-POOL" "EXCEPTION-POOL" consists of one node: 10.0.0.1:80 I would think that any requests being sent to VS that starts with "/EXCEPTION/" would be sent to the "EXCEPTION-POOL", but this doesn't seem to be working. I am still seeing requests starting with "/EXCEPTION/" on 10.0.0.2:80 and 10.0.0.3:80 Is something configured incorrectly, or am I misunderstanding how it is supposed to work? Thanks!
... View more
07-26-2013
11:12:AM
Thank you for the instructions. I will reference this page the next time we encounter this issue.
... View more
07-24-2013
03:31:PM
Thanks for the confirmation. We are currently using Stingray Load Balancer 8.1r1 and don't see a way to add a TrafficScript rule. How do we accomplish this?
... View more
07-23-2013
03:46:PM
We have a problem with IP Transparency and routing. Sample configuration: Traffic IP: 192.168.0.100 Pool with Single Node: 192.168.0.101 Default Gateway: 192.168.0.1 With IP Transparency disabled, everything works great. Connection from outside: Outside -> 192.168.0.1 -> 192.168.0.100 -> 192.168.0.101 192.168.0.101 -> 192.168.0.100 -> 192.168.0.1 -> Outside Connection from inside: 192.168.0.200 -> 192.168.0.100 -> 192.168.0.101 192.168.0.101 -> 192.168.0.100 -> 192.168.0.200 With IP Transparency enabled, the routing becomes a problem: Connection from outside: Outside -> 192.168.0.1 -> 192.168.0.100 -> 192.168.0.101 192.168.0.101 -> 192.168.0.1 -> Outside Because the node no longer sees the request as coming from the load balancer, the return path skips it. We were able to do a workaround by configuring the default gateway of the node to be the load balancer, which made the route symmetrical again: Outside -> 192.168.0.1 -> 192.168.0.100 -> 192.168.0.101 192.168.0.101 -> 192.168.0.100 -> 192.168.0.1 -> Outside But this doesn't work for connections from inside: 192.168.0.200 -> 192.168.0.100 -> 192.168.0.101 192.168.0.101 -> 192.168.0.200 Because the source IP is in the same subnet as the node IP, the return path of the traffic bypasses the gateway and goes directly back to the source. This seems to break the TCP connections. What is the proper way of configuring IP Transparency?
... View more
Latest Tags
No tags yet
© 2017 Pulse Secure, LLC. Use of this website assumes acceptance of our Legal Notices and Privacy Policy.
Pulse Secure has updated its Privacy Policy effective June 28, 2017.
