topic Re: Another bug for 5.0.3 in General Topics

Another bug for 5.0.3

Retired Member — Wed, 20 Mar 2013 15:17:14 GMT

When using port with address of External Gateway on Global protect, 5.0.3 does not accept this.

it is working on 5.0.2

Re: Another bug for 5.0.3

Hithead — Wed, 20 Mar 2013 15:57:08 GMT

Hello,

why you are using the interface with a port number?

Re: Another bug for 5.0.3

Retired Member — Wed, 20 Mar 2013 15:59:49 GMT

Because 443 is busy for some of our customers.And they do not want to change port of the other service.

Re: Another bug for 5.0.3

scantwell — Fri, 29 Mar 2013 19:38:28 GMT

Ok, so you can create a public IP loopback address and then use that as your portal. I agree that it appears to be a bug, but you have a workaround that allows you to upgrade to 5.0.3 (correct?) Thanks

Re: Another bug for 5.0.3

Retired Member — Fri, 29 Mar 2013 19:42:19 GMT

No you cannot use this with (Bridge mode Modem)ppoe interface.PaloAlto does not support this.

But for other layer3 interface yes you can use loopback.

Also there is a document for that

Re: Another bug for 5.0.3

scantwell — Fri, 29 Mar 2013 21:05:30 GMT

Ok.. making an assumption here. in 5.0.2, you could have 183.23.34.45:444 as the GW. Instead of configuring your portal to send down 183.23.34.45:444, (in 5.0.3) why not have it continue to send 183.23.34.45 and just ask those new users to add the :444 port number (presuming existing GP users already have 183.23.34.45:444 in their configuration on the GP agent) Would that work. No reason why it should not. Thoughts?

Re: Another bug for 5.0.3

Retired Member — Fri, 29 Mar 2013 21:12:37 GMT

Because if you don't write any port it uses 443 as I know.if you write in portal ....45 it will use port 443 by default.

When you connect to portal you do not choose your gateway(if you don't have a license and not configured) it automaticly goes trough the gw configured with 443.

So the problem is not portal , it is gateway.