Sonicwall filter ospf routes
Hi all,
we are moving from old cisco router to new sonicwall devices.
We have multiple locations, connected via mpls, each location has it's own internet access. For routing through the mpls network ospf is used. With sonicwall (NSA-2400 and NSA-220, all 5.8.1, by the way) I check redistribute connected networks to distribute the lan at X0. But in this case the WAN-Network at X1 is also distributed.
Is there a way to filter routing information to or from ospf process, or say just redistribute connected LAN networks? With cisco we used distribute-list <acl> <in|out>
Kind regards
we are moving from old cisco router to new sonicwall devices.
We have multiple locations, connected via mpls, each location has it's own internet access. For routing through the mpls network ospf is used. With sonicwall (NSA-2400 and NSA-220, all 5.8.1, by the way) I check redistribute connected networks to distribute the lan at X0. But in this case the WAN-Network at X1 is also distributed.
Is there a way to filter routing information to or from ospf process, or say just redistribute connected LAN networks? With cisco we used distribute-list <acl> <in|out>
Kind regards
Enable the multicast support under the SonicWALL Interface advanced configuration. OSPF needs musticast traffics to be traversed for ospf adjacency.
ASKER
I activated it on both ends, but don't know how it changes things.
OSPF is up and running, the problem is it is running too good for me.
OSPF is up and running, the problem is it is running too good for me.
Please check this Here
ASKER
I cannot reach my lab over christmas and will do more testing next year. My lab mpls emulating was used as spare part, so now I have only access to the main office sonicwall :-(
In my case it was this:
Tunnel created as in Route based VPN. See also my other question: https://www.experts-exchange.com/questions/28322181/Sonicwall-Site-To-Site-MPLS-and-VPN.html?anchorAnswerId=39735045#a39735045
ospf should only be used on X2, which is used for mpls on both ends.
If ospf is disabled: default route directs to gateway of each ISP. Main location has two of it, connected to VLAN-interfaces of X1. VPN tunnel goes up, everything is fine.
If ospf is enabled: default route still directs to gateway of each ISP, but the WAN address range is propagated by branch location sonicwall through MPLS to main location sonicwall. Since the subnet mask is more specific (0 <-> 29 in my lab) this route gets a higher priority, even so its metric is higher (20 <->110). It seems the VPN tunnel packages should be routed through X2 (MPLS) of both routers, which is prohibited through firewall and vpn bind option and thus the vpn tunnel gets disconnected.
No problem in an ordinary believe-in-failover scenario (mpls up, ospf routes active, workload routing ok / / mpls down, ospf routes vanish, vpn up, workload-routing ok). But we need the vpn tunnel up all the time.
The only way working seems to be a custom defined routing policy with source and destination defined as host ip directing to the gateway for each branch office and each ISP at the main office.
In my case it was this:
Tunnel created as in Route based VPN. See also my other question: https://www.experts-exchange.com/questions/28322181/Sonicwall-Site-To-Site-MPLS-and-VPN.html?anchorAnswerId=39735045#a39735045
ospf should only be used on X2, which is used for mpls on both ends.
If ospf is disabled: default route directs to gateway of each ISP. Main location has two of it, connected to VLAN-interfaces of X1. VPN tunnel goes up, everything is fine.
If ospf is enabled: default route still directs to gateway of each ISP, but the WAN address range is propagated by branch location sonicwall through MPLS to main location sonicwall. Since the subnet mask is more specific (0 <-> 29 in my lab) this route gets a higher priority, even so its metric is higher (20 <->110). It seems the VPN tunnel packages should be routed through X2 (MPLS) of both routers, which is prohibited through firewall and vpn bind option and thus the vpn tunnel gets disconnected.
No problem in an ordinary believe-in-failover scenario (mpls up, ospf routes active, workload routing ok / / mpls down, ospf routes vanish, vpn up, workload-routing ok). But we need the vpn tunnel up all the time.
The only way working seems to be a custom defined routing policy with source and destination defined as host ip directing to the gateway for each branch office and each ISP at the main office.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Not exactly what I wanted, but since no one provided a sonicwall-replacement for distribute-in and distribute-out acl it is at least working for us. Though the routing lists gets very full, the disturbing entries are not there any more since disabling redistribute connected networks on the mpls interface and enabling ospf passive service at the lan interface.