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
!
On 15 Jun 2004 at 11:23, bino_oetomo wrote:
> Hmmm
> I think it'll be better if you can paste :
> - ip addr
> - ospf sh run
> of both routers to your mail so we can "imagine" what you did.
>
> Sincerely
> -bino-
> ----- Original Message -----
> From: "Ray Gwinn" <[EMAIL PROTECTED]>
> To: "Vladimir Ivashchenko" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Tuesday, June 15, 2004 8:56 AM
> Subject: Re: [leaf-wisp] Zebra/ospf
>
>
> > I am wondering if I have basic radio setup problem. The two radios for
> the node to
> > hode hop are on the same channel (11) and in master mode. Is this
> correct?
> >
> > > By the way, a requirement of OSPF is that interface
> > > network/netmask should be the same on both of the routers.
> >
> > I have tried many variations. Currently the interface on one router is
> set to
> > 10.0.100.1/24, and 10.0.101.1/24 on the other router. The network is not
> the same,
> > but the netmask is. I have tried one big network 10.0.0.0/8 network also,
> with /8
> > netmask on all IPs, and still no luck.
> >
> > Ray
> >
> > On 14 Jun 2004 at 23:20, Vladimir Ivashchenko wrote:
> >
> > > Hi,
> > >
> > > You can configure the OSPF authentication key using the menu, or
> > > using command line - look at " ip ospf message-digest-key"
> > > interface subcommand.
> > >
> > > Anyway, I'm interested to see output "sh ip ospf neigh" command.
> > >
> > > By the way, a requirement of OSPF is that interface
> > > network/netmask should be the same on both of the routers.
> > >
> > > Ray Gwinn wrote about "Re: [leaf-wisp] Zebra/ospf":
> > >
> > > > > Make sure that OSPF key is the same on both nodes, and check that
> > > >
> > > > I see nothing in the default conf files, or the zebra documentation
> about an
> > > > "OSPF key". Can you give more detail?
> > > >
> > > > Ray
> > > >
> > > > On 13 Jun 2004 at 14:38, Vladimir Ivaschenko wrote:
> > > >
> > > > >
> > > > > OSPF routing should work by default.
> > > > >
> > > > > Make sure that OSPF key is the same on both nodes, and check that
> > > > > routing tables are correct by doing "ip route". Note that if OSPF is
> > > > > working you will have routes with "proto zebra" in the list.
> > > > >
> > > > > Ray Gwinn wrote:
> > > > > > Vladimir, I have one wisp-disp node up and running fine. This
> node has
> > > > > > an internet feed via eth0. All hardware is Soekris 4521.
> > > > > >
> > > > > > I have now up a second node. This second node is wireless only.
> That
> > > > > > is, the second node's internet feed is one of the radios connected
> to a
> > > > > > small beam pointing at the first (working) node. User's can
> associate
> > > > > > with the second node, but there seems to be a routing problem.
> > > > > >
> > > > > > My question is, should the default wisp-disp zebra/ospf configs
> work on
> > > > > > both nodes? If not, can you provide any clues about configuring
> > > > > > zebra/ospf for the two nodes?
> > > > > >
> > > > > > Ray
> > > > > >
> > > > > >
> > > > > >
> > > > > > -------------------------------------------------------
> > > > > > This SF.Net email is sponsored by the new InstallShield X.
> > > > > >>From Windows to Linux, servers to mobile, InstallShield X is the
> > > > > > one installation-authoring solution that does it all. Learn more
> and
> > > > > > evaluate today! http://www.installshield.com/Dev2Dev/0504
> > > > > > _______________________________________________ leaf-wisp-dist
> mailing
> > > > > > list [EMAIL PROTECTED]
> > > > > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best Regards,
> > > > > Vladimir Ivashchenko
> > > > > ThunderWorx - www.thunderworx.com
> > > > > Senior Systems Designer/Engineer
> > > > >
> > > > >
> > > > >
> > > > > -------------------------------------------------------
> > > > > This SF.Net email is sponsored by the new InstallShield X.
> > > > > >From Windows to Linux, servers to mobile, InstallShield X is the
> > > > > one installation-authoring solution that does it all. Learn more and
> > > > > evaluate today! http://www.installshield.com/Dev2Dev/0504
> > > > > _______________________________________________ leaf-wisp-dist mailing
> > > > > list [EMAIL PROTECTED]
> > > > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist
> > > >
> > > >
> > >
> > > --
> > > Best Regards,
> > > Vladimir Ivashchenko
> > > ThunderWorx - www.thunderworx.com
> > > Senior Systems Designer/Engineer
> > >
> > >
> > > -------------------------------------------------------
> > > 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
> > > _______________________________________________ leaf-wisp-dist mailing
> > > list [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist
> >
> >
> >
> >
> > -------------------------------------------------------
> > 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
> > _______________________________________________ leaf-wisp-dist mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist
> >
> >
> > __________ NOD32 1.789 (20040614) Information __________
> >
> > This message was checked by NOD32 Antivirus System.
> > http://www.nod32.com
> >
> >
>
>
>
> -------------------------------------------------------
> 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
> _______________________________________________
> leaf-wisp-dist mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist
-------------------------------------------------------
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
_______________________________________________
leaf-wisp-dist mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist
