Re: [leaf-wisp] Zebra/ospf

"bino_oetomo" <[email protected]>
Newsgroups gmane.linux.leaf.wisp-dist
Message-ID <018c01c4529c$b6ceabb0$0300a8c0@indoaksesbno>
Hi.
Did you ever try to set OSPF neighbor manualy ?
I'm not sure if WISP Zebra pkg come with neighbor discovery.

Sincerely
-bino-
----- Original Message -----
From: "Ray Gwinn" <[email protected]>
To: "bino_oetomo" <[email protected]>
Cc: <[email protected]>
Sent: Tuesday, June 15, 2004 12:41 PM
Subject: Re: [leaf-wisp] Zebra/ospf


> I have reduced the hardware to the simplest setup.  The setup is currently
1 radio on both
> units.  The radios are both set to channel 1, and in master mode.
>
> My intent is that the 172.16.xx.xx/12 ip address are area 0.  The
10.0.0.0/24 address are
> for dhcp to assign to users.  I have tried specifically setting area 0 to
172.16.0.0/12
> instead of 0.0.0.0/0.  I read the area 0 ip of 0.0.0.0/0 to say "route
anything from
> anywhere".
>
> The "ip addr" of the node with the internet connection is first, the
remote wireless only
> node then follows.
>
> The "ospf sh run" seems to only echo the ospfd.conf file.  The ospfd.conf
file is the same
> on both nodes, and is the default shipped with wisp-disp, except for the
password and
> hostname.  The ospfd.conf follows the ip addr outputs.
>
> 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 scope host lo
> 2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop
>     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
> 3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
>     link/ether 00:00:24:c1:b9:bc brd ff:ff:ff:ff:ff:ff
>     inet 199.250.240.253/24 scope global eth0
>     inet 172.16.6.73/12 scope global eth0
> 4: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 100
>     link/ether 00:00:24:c1:b9:bd brd ff:ff:ff:ff:ff:ff
> 5: netcs0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
>     link/ether 00:02:6f:08:21:df brd ff:ff:ff:ff:ff:ff
>     inet 10.0.100.1/24 scope global netcs0
>     inet 172.16.6.65/12 scope global netcs0
>
>
> 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 scope host lo
> 2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop
>     link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
> 3: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 100
>     link/ether 00:00:24:c1:78:40 brd ff:ff:ff:ff:ff:ff
> 4: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 100
>     link/ether 00:00:24:c1:78:41 brd ff:ff:ff:ff:ff:ff
> 5: netcs0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
>     link/ether 00:02:6f:08:09:6a brd ff:ff:ff:ff:ff:ff
>     inet 10.0.101.1/24 scope global netcs0
>     inet 172.16.6.81/12 scope global netcs0
>
> !
> ! Zebra configuration saved from vty
> !   2002/05/02 15:28:04
> !
> hostname win-msu-0.100.0
> password itsme$
> enable password itsme$
> log file /var/log/ospfd.log
> !
> !
> !
> interface lo
> !
> interface eth0
>  ip ospf message-digest-key 1 md5 wisp
> !
> interface eth1
>  ip ospf message-digest-key 1 md5 wisp
> !
> interface eth2
>  ip ospf message-digest-key 1 md5 wisp
> !
> interface netcs0
>  ip ospf message-digest-key 1 md5 wisp
> !
> interface netcs1
>  ip ospf message-digest-key 1 md5 wisp
> !
> interface netcs2
>  ip ospf message-digest-key 1 md5 wisp
> !
> router ospf
>  redistribute connected
>  redistribute rip
>  network 0.0.0.0/0 area 0
>  area 0 authentication message-digest
> !
> access-list vtylist permit 127.0.0.1/32
> access-list vtylist deny any
> !
> line vty
>  access-class vtylist
> !
>
>




-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.