SRX 5308 - Protocol binding does not work

Question

I have two WANs up and running and selected NAT and Load balancing with weighted LB. I defined a protocol binding for FTP for WAN2 but it routes through WAN1?

The default outbound policy is "block always" and i only have one policy that allows all trafic and NAT IP is set to AUTO. Why is it not working? The only way to get outgoing traffic for specific service to specific WAN port is to define an outbound policy for each and define NAT IP accordingly, for example WAN2. If I understand correct the protocol binding should work without any outbound policies?

Firmware: 4.3.3-6

DaneA · Answer

Hi&nbsp;dproxximo,
&nbsp;
Welcome to the community! :)&nbsp;
&nbsp;
The outbound policy is needed to be defined for the protocol binding to work. &nbsp;
&nbsp;
&nbsp;
Regards,

DaneA
NETGEAR Community Team

dproxximo · Answer

Do you mean NAT IP = AUTO is enough or do I need to define one outbound policy for each service (but what good is protocol binding in that case if I control everything with policies)?

DaneA · Answer

Hi&nbsp;dproxximo,

&nbsp;

Kindly try to remove the protocol binding that is configured&nbsp;then just define an outbound policy in the firewall rules and observe. &nbsp;Let us check if the outbound policy will just work without configuring protocol binding on the SRX5308.

&nbsp;

Regards,

&nbsp;

DaneA

NETGEAR Community Team

dproxximo · Answer

I can confirm that protocol binding is useless or not working. I have now disabled them.

Outbound policies works and is easy to define. I just have one outbound policy for ALL services that is defined to WAN1 and I only need to define the services I want for WAN2 and put them before the other policy. If that matches then it ignores the policies below and routes to WAN2 as it should.

Thank you!

DaneA · Answer

Hi&nbsp;dproxximo,
&nbsp;
I am glad to know that&nbsp;the outbound policies you have configured are working fine as per your network requirements. :) &nbsp;
&nbsp;
I have inquired your concern&nbsp;to&nbsp;a higher tier of &nbsp;NETGEAR Support and I found out that once a protocol binding rule is setup it is not necessary to create an outbound rule. &nbsp;(My bad about my reply to you: "The outbound policy is needed to be defined for the protocol binding to work." :( )&nbsp; &nbsp; If the protocol binding does not work, it is possible that its not properly configured. &nbsp;For example,&nbsp;incorrect&nbsp;source or destination details and the PC they test from is not included in the protocol binding rule.
&nbsp;
It is also&nbsp;ok&nbsp;if you will just define&nbsp;outbound policies since you find it easy to define and its proven working on your end. &nbsp;If ever you still wish to try to get protocol binding to work, I suggest you to open an online case with&nbsp;NETGEAR Support&nbsp;at anytime for further assistance. &nbsp;
&nbsp;
&nbsp;
Regards,
&nbsp;
DaneA
NETGEAR Community Team

Forum Discussion

SRX 5308 - Protocol binding does not work

5 Replies

Related Content

fvs336gv3 protocol binding

SRX5308 Protocol Binding Services PORT 443 LB

SMB Protocol

gss116E Disable Spanning Tree Protocol (STP) and forward Bridge Protocol Data Units (BPDUs)

Is SMB protocol faster than AFP ?

NETGEAR Academy

ProSupport for Business