> I'm a little confused with the meaning of "Network Range" in ospf.
OK, I'll have a go...
It is the range of addresses that the portmaster will announce to it's
neighbours as being internal to the Autonomous System using OSPF. The
portmaster (with OSPF enabled and properly configured) will also announce
OSPF external type 2 routes for:
1) Any addresses in your pool that aren't inside your configured Network
Range.
2) Any static IP users that dial into the portmaster and have their
address assigned by RADIUS.
Conidition 1 is fair enough, but I'm not really sure why it assigns static
IP users as OSPF type E2 routes regardless of whether they are in a
Network Range.
> We have our servers, borderrouter and PM's in 194.19.140.0/24
> Fixed ip's and dynamic dialins in 194.255.12.0/23
> This PM uses 194.255.13.64/26 as adress pool, and also handles calls from
> users with fixed IP (which can connect to any PM).
> These fixed ip's are neither in 194.19.140.0/24 or 194.255.13.64/26, but
> nevertheless, their routes get announced (which is good anyway)
>
> Has I misunderstood the meaning of "Network Range"?
You haven't actually said what you think it is.
> Should it contain the PM's and routers?
It should contain the range of addresses you want to announce as internal
OSPF routes. The portmaster and the other OSPF routers must be able to
route to each other in some other fashion (e.g. being on the same subnet),
otherwise they will not be able to exchange OSPF information with each
other.
> Or should it contain the fixed and dynamic ip's of the dialins?
It depends on how you want to annouce your OSPF routes. If you want your
dynamic dialup customers to be announced as internal OSPF routes then your
dialup pool will have to be in your network range. If you don't mind them
being announced as external type 2 OSPF routes then it doesn't really
matter.
> ibe10> show ospf ar
> Area Network Range Type ID Key Type Cost
> --------------- ------------------ ---- --- ---------------- -------- -------
> 0.0.0.0 *194.19.140.0/24 None External N/A
I don't think the above line is doing anything useful. If this subnet is
just full of routers and servers (i.e. no dynamic dialups) then the
portmaster doesn't really have any business in announcing routes for it
over OSPF.
> *194.255.13.64/26
The above line is worth having though, as it means that your dialup pool
with be announced as internal OSPF routes.
What does the routing table on your border router look like?
Regards,
-- Richard Morrell richard@ednet.co.uk System Administrator - edNET: Internet Access for Edinburgh - www.ednet.co.uk
- 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/>