SRX Next-Gen Firewalls

I figured out what the problem was. I had not set the option no-eap-tls under [security remote-access client-config vpn-client-config] . This caused the Juniper Secure Connect client to ask for a certificate PIN before checking the existence ...

I'm stumped. Not sure where the DHCP OFFER packets are going. Your traffic monitor filter doesn't include an interface, does it? ------------------------------ Nikolay Semov ------------------------------

Thank you! Speaking of ECMP, did you happen to see this thread: https://community.juniper.net/discussion/learning-junos-and-srx340-trying-to-load-balance-across-multiple-interfaces-to-same-gateway-layer-3-lag-to-utilize-3gig-uplink? The challenge there ...

Sounds like what you need is filter-based forwarding. See this: https://www.juniper.net/documentation/us/en/software/junos/routing-policy/topics/example/firewall-filter-option-filter-based-forwarding-example.html Also very useful is to keep in mind ...

The destination IP is not fixed. It's a good list of possible IPs from Nintendo and from the other device(s) in the online eSports match. So, it would be almost random based on who they are playing against. I have fixed IPs for the Nintendo Switches ...

The egress interface for traffic is selected by the destination ip address and the active routing table and NOT the policies in play. Since you have two ISP you will need to be sure the Nintendo destination ip addresses are all set towards that desired ...

I've run into a situation where our school district Nintendo Switch policy for eSports can send the traffic out an interface to our secondary ISP and not always our primary one. Since I have to have a NAT policy to make sure they all get a given public ...