Solved: Allowing TCP options 24-31 on PIX v6.x

marioderosa2008 · ‎12-04-2008

Hi all,

having trouble with the PIX firewall stripping the TCP options as traffic passes through. We have Citrix WAN scalers that use these options to accelerate TCP connections.

Can any one advise of the syntax to do this?

Does anyone know if PIX v7 command syntax differes from PIX v6 ?

I have command syntax for v7 below, but this does not seem to be accepted on our PIX 6 firewall.

pixfirewall(config)#access-list tcpmap extended permit tcp any any

pixfirewall(config)# tcp-map tcpmap

pixfirewall(config-tcp-map)# tcp-opt range 24 31 allow

pixfirewall(config-tcp-map)# exit

pixfirewall(config)# class-map tcpmap

pixfirewall(config-cmap)# match access-list tcpmap

pixfirewall(config-cmap)# exit

pixfirewall(config)# policy-map global_policy

pixfirewall(config-pmap)# class tcpmap

pixfirewall(config-pmap-c)# set connection advanced-options tcpmap

Thanks again guys!!

ajagadee · ‎12-04-2008

Mario,

There is a difference between Pix 6.x and 7.x. In Pix 6.x. all TCP options should pass unchanged. But, in Pix 7.x, you need the above commands to make Citrix work.

Regards,

Arul

*Pls rate if it helps*

View solution in original post

marioderosa2008 · ‎12-04-2008

can i please have some advice on this...?

has no one come accross this kind of problem before?

Does any one know whether TCP policy mapping can be done on PIX v6.0?

Tom.Weast · ‎12-04-2008

Please see the other replies on this, but no there is no way to do policies like this in 6.X like there is in 7.X. For us, it was not needed in 6.X, it just worked. We did require the change on the 7.X side.

Tom.Weast · ‎12-04-2008

We just ran into this exact problem today. One wanscaler was behind a PIX 6.3 firewall, and the other behind an ASA with version 7.X.

We found that the version 7 needed the above configuration, but the version 6 did not.

I could not find anywhere to set TCP Options in a PIX 6.X firewall. But as soon as we did the config on the 7.X firewall, it immediately started working end-to-end.

ajagadee · ‎12-04-2008

Mario,

There is a difference between Pix 6.x and 7.x. In Pix 6.x. all TCP options should pass unchanged. But, in Pix 7.x, you need the above commands to make Citrix work.

Regards,

Arul

*Pls rate if it helps*

marioderosa2008 · ‎12-04-2008

thanks for the reply.

It has helped me rule out that the PIX firewall is not cauring the issue...

thanks again!

ajagadee · ‎12-04-2008

Mario,

Your welcome. If the above posts resolves your issue, could you please update the forum that it resolved the issue and also rate if possible.

Thanks,

Arul

mkohlschmidt · ‎08-31-2009

I run into the same problem. Can u confirm 100% that pix 506 with 6.3(5) doesnt strip tcp options?

ajagadee · ‎12-04-2008

Mario,

There is a difference between Pix 6.x and 7.x. In Pix 6.x. all TCP options should pass unchanged. But, in Pix 7.x, you need the above commands to make Citrix work.

Regards,

Arul

*Pls rate if it helps*