This message was deleted.
# citrix-netscalers
Slackbot
02/24/2020, 5:12 PMThis message was deleted.
l
Leee Jeffries
02/24/2020, 5:22 PMTo the best of my knowledge it is indeed.
c
Cormac Long
02/24/2020, 5:34 PMcheers Leee, would be nice to be able to do this. I dont know why Citrix restrict this for the gateway, licensing i guess...
l
Leee Jeffries
02/24/2020, 5:37 PMI think it's more the complexity of checking the packets as they come through and then spitting them out to the correct gateway. It may actually not be possible at all. That being said, I'm not 100÷ sure.
c
Carl Behrent
02/24/2020, 6:00 PM@Cormac Long yip definitely only one Gateway and multiple LB VIPs upto v13. I’ve just recently been looking into this and the latest Citrix docs confirmed it.
c
Cormac Long
02/24/2020, 6:03 PMThanks a lot for confirming it Carl
👍 1
j
Julian Mooren
02/24/2020, 6:24 PMThere is a workaround but it is not officially supported 🙂
l
Leee Jeffries
02/24/2020, 6:27 PMThis the the TCP based services load balancing a gateway right?
j
Julian Mooren
02/24/2020, 6:30 PMc
CTXMike
02/24/2020, 6:51 PMYeah theoretically you could get creative, but remember if it breaks you'll have a tough time getting support to understand how you did something that's not supposed to work
j
Julian Mooren
02/24/2020, 6:55 PMFound this in my notes. If you want to use it in your home lab
Julian Mooren
02/24/2020, 6:55 PMGateway VIP: 192.168.2.104
Dummy VIP: 192.168.2.105
add service svc_gateway2_dummy_ssl 192.168.2.105 SSL 443 -gslb NONE -maxClient 0 -maxReq 0 -cip DISABLED -usip NO -useproxyport YES -sp OFF -cltTimeout 180 -svrTimeout 360 -CKA NO -TCPB NO -CMP NO
add service svc_gateway2_dummy_any 192.168.2.104 ANY 443 -gslb NONE -maxClient 0 -maxReq 0 -cip DISABLED -usip NO -useproxyport NO -sp OFF -cltTimeout 120 -svrTimeout 120 -CKA NO -TCPB NO -CMP NO
add lb vserver lb_vsrv_gateway2_workaround_ssl_443 SSL 0.0.0.0 0 -persistenceType NONE -cltTimeout 180
add lb vserver lb_vsrv_gateway2_workaround_any_443 ANY 192.168.2.105 443 -persistenceType NONE -cltTimeout 120
bind lb vserver lb_vsrv_gateway2_workaround_ssl_443 svc_gateway2_dummy_ssl
bind lb vserver lb_vsrv_gateway2_workaround_any_443 svc_gateway2_dummy_any
add cs action cs_act_gateway2_dummy -targetLBVserver lb_vsrv_gateway2_workaround_ssl_443
add cs policy cs_pol_gateway2_dummy -rule "HTTP.REQ.HOSTNAME.EQ(\"apps2.domain.com\")" -action cs_act_gateway2_dummy
c
Cormac Long
02/24/2020, 7:15 PMThx @Julian Mooren I will mess around with it in the lab first. I tend to go with @CTXMike view about keeping it supported by ctx in production for a customer.
j
Julian Mooren
02/24/2020, 7:24 PMYes wouldn’t use it in production. If there is only one public IP go with a custom port
👍 2
c
Cormac Long
02/25/2020, 8:53 PMHey @Julian Mooren you wouldn’t have any docs/blogs around setting up the custom port with single PIP by any chance? I haven’t done it before...
j
Julian Mooren
02/25/2020, 9:00 PMJust create a second gateway with the same VIP but another port. Lets say 4443 and attach your needed authentication and Session policies.
Don’t forget to add the custom port when creating the gateway object in the Citrix StoreFront console.
If you need further assistance feel free to ask 👍🏽
👍 2
c
Cormac Long
02/25/2020, 9:07 PMLegend! I get it. Thanks a lot, will do.
j
Julian Mooren
02/25/2020, 9:08 PMHave fun 🤓
👍 1
c
Cormac Long
02/26/2020, 5:12 PMI think i am still missing something here. I get the gateway config but not the routing to the right gateway based on the url the user enters. Is it the firewall handles this or another feature on ADC i am not familiar with?
j
Julian Mooren
02/26/2020, 5:20 PMyou enter the url with custom port
Https://apps.domain.com:4443
Julian Mooren
02/26/2020, 5:20 PMDNAT from Public IP to VIP for this port
c
Cormac Long
02/26/2020, 5:22 PMI was afraid that was the case😂 thanks again Julien.
j
Julian Mooren
02/26/2020, 5:22 PM✌🏼
3 Views