Roy
PS. Yes, you can route based on the destination/source pair but that's
policy based routing and far beyond the simple scope of this scenario.
Scott Rosen wrote:
>
> We are trying to implement OSPF on our network and have run into a
> bit of a snag. In addition to our regular dialup pool, we are also
> running a cablemodem system that uses assymetric routing.
>
> The cablemodem customers dialup to our portmaster, and we assign
> them an IP address from a special pool. These addresses have been
> statically routed out to the cable headend, and then on to the cable
> system. So, from a customer point of view, all of their data goes
> *out* their analog modem, and it comes *in* via their cablemodem.
>
> This has been working fine with static routes. However, as soon as
> we turned on OSPF, the portmaster started announcing the route to
> the dialup customer, so the data comes back in via their analog modem
> (instead of being bounced out to the cable office).
>
> Is there a way to tell the portmaster to *NOT* announce certain
> addresses using OSPF? Or to have it announce a lower priority? Any
> suggestions?
>
> TIA,
>
> Scott Rosen
> Frazier Mountain Internet Service
> -
> To unsubscribe, email 'majordomo@livingston.com' with
> 'unsubscribe portmaster-users' in the body of the message.
> Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>