The above works Thanks to the very talented Software Engineer that wrote
the code to do this. there is no rfc standard on how to propagate dial
pools. So it it is up to the individual company(Software Engineer) on how
they want the address pool propagated
When a user logs in and has a static IP address, the PM2's
>broadcast an
>external type E2 route for that static IP address - is this correct?
the external type 2 route is correct for dial in users per rfc standard.
FYI.
This means you can not place these access servers in a stub area and expect
it to dynamically propagate these routes, however you can place them in a
Not-So-Stubby-Area
>
>I've included some more information on my network below. If you've got a
>handle on OSPF, I'd appreciate your comments.
>
>
>
>------------------------
>NETWORK MAP
>
>
> ^ To Internet
> |
> | Ser 0
> |
>--------------------------
>| RTR-A (CISCO) |
>--------------------------
> | Eth 1 (204.212.132.1)
> |
>-[ethernet]-----------------------------------------------------------------
>-------------------
> | | |
> 204.212.132.5 | 204.212.132.6 | 204.212.132.6 |
> | | |
> ----------------------- ----------------------- ---------------------
> | RTR-B (PM2) | | RTR-C (PM2) | | HOST-A |
> ----------------------- ----------------------- ---------------------
> | | | | | | | | | | | |
> | | | | | | | | | | | |
> | | | | | | | | | | | |
>
> DIALUPS DIALUPS
> Dynamic / Static Dynamic / Static
>
>
>------------------------
>IP ADDRESS SPACE
>
>204.212.132.0/27 "Core" network
>204.212.132.32/27 Pool space for RTR-B (PM2)
>204.212.132.64/27 Pool space for RTR-C (PM2)
>
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.