In all counts the reality here is that the range statement
was not set specifically.
The beauty of OSPF on Portmasters is that you only need to set
the range of the local ether0 interface.
Never set a range for the dynamically assigned address pool or
for any statically assigned addresses for dialup clients or
routers. (why? see below)
IE:
Ether0:
Interface address: 192.168.100.1
Netmask: 255.255.255.224
The required commands are:
set ospf enable (if not already)
save all
reboot
....
add ospf area 0 range 192.168.100.0/27
(yes, you can create the area and set the range in one fowl swoop)
set ether0 ospf on (same as 'set ospf on')
save all
reboot
After all of this, we still recommend a reboot, especially if there
have been many attempt to bring OSPF up. Always delete the OSPF area,
save, reboot, add the new area/range, save, reboot again - for when
you are changing many things.
<or>
reset ospf
IF you are configuring OSPF for the first time and have not noodled
around, a simple 'reset ospf' can get you going.
By default all OSPF areas are set to 'external' type of areas and
to 'advertise'.
Again. NEVER set the range for your dialup address pools, because
they are AUTOMATICALLY redistributed as 'External Type 2' routes.
These routes are redistributed inthis way since they are periodic
insertions, and thus don't require every router in your network to
recalculate their Link State Databases...
See the following latest Command Line Administrators Guide (JULY 97)
for more details:
show ospf area
show ospf neighbor
show ospf links
Your Routing conscience,
Tom Fellenz
Tech Support Escalation
Livingston
At 03:07 PM 8/21/97 -0600, Stephen Fisher wrote:
>
>You probably forgot to put "advertise" at the end of the range statement
>=)
>
>On Thu, 21 Aug 1997, mike cullerton wrote:
>
>> wanye,
>>
>> well then, that's not my problem.
>>
>> i have the address/nm of the ethernet port as my range, and my neighbor
>> is set up and happy. in fact, the portmaster has received a routing table
>> from my ospf neighbor. the portmaster just isn't telling the rest of the
>> world about the address of the dialin user.
>>
>> :(
>> mike
>>
>> On Thu, 21 Aug 1997, Wayne Bouchard wrote:
>>
>> > > hello all,
>> > >
>> > > i'm trying to provide dedicated ip's to my customers using radius
and
>> > > ospf. when a customer connects to me, i want them to be able to
have the
>> > > same ip address no matter which terminal server they connect to.
>> > >
>> > > in my /etc/raddb/users file, i assign an ip address to a user. when
>> > > they dial in, they get the correct address, and a "show route" in the
>> > > portmaster shows the address in the routing table.
>> > >
>> > > but, the terminal server isn't advertising this route via ospf.
>> > >
>> > > my config for ospf includes
>> > >
>> > > set ospf enable
>> > > add ospf area 30
>> > > set ether0 ospf on
>> > >
>> > > i am confused about "set ospf area 30 range" command, and am
wondering
>> > > if this is my problem.
>> >
>> > Thats your problem. the "range" means the interfaces whose addresses
>> > are in the spoecified range will have OSFP hellos sent over them. If
>> > you do a "show ip ospf neighbor" you'll probably not see any.
>> >
>> > ----------------------------------------------------------------------
>> > Wayne Bouchard GlobalCenter
>> > web@primenet.com
>> > Primenet Network Engineering Internet Solutions for
>> > (602) 416-6422 800-373-2499 x6422 Growing Businesses
>> > FAX: (602) 416-9422
>> > http://www.primenet.com http://www.globalcenter.net
>> > ----------------------------------------------------------------------
>> >
>>
>> --
>> mike cullerton michaelc@frii.com 970.224.3668
>>
>
>
>