Ok - only solution we could come up with pending better customer information
or a better design idea:
Internet-edgerouter---firewallinside
Recall that there are two internet connections terminating on the edge
router.
Policy routing on the edge router interface connecting to
How about this... Since the exit point is based on destination address,
could you use floating static routes? For example...
ip route 255.255.255.255 50
ip route 255.255.255.255 100
ip route 255.255.25.255 50
ip route 255.255.25.255 100
ip route 0.0.0.0 0.0.0.0 50
ip route 0.0.0.0
Ok - only solution we could come up with pending better customer information
or a better design idea:
Internet-edgerouter---firewallinside
Recall that there are two internet connections terminating on the edge
router.
Policy routing on the edge router interface connecting to
Thoughts inline below
| Howard's comment brings to mind a problem my Design Engineer raised when
| responding to a customer RFI.
|
| Howard's comment: . (Pause for usual mystification on why someone wants
| routing protocols to pass through
| a firewall, a fairly frequent question).
4 matches
Mail list logo
