Re: [leaf-wisp] Zebra/ospf

Hi,

Sorry for not being clear. I meant that ESSID should be the same 
everywhere.

If it is so, then the client should have a problem finding the access 
point even if it was not available previously.

Ray Gwinn wrote:
> I apologize for being such a novice, but asking questions is the best way to overcome "being a 
> novice".
> 
> 
>>Make sure that ESSID is set correctly on the station in MANAGED mode.
> 
> 
> I am not sure what you mean by the above.  I currently have the same ESSID everywhere.  Are 
> you saying they should be different, or is there something special about the ESSID on a 
> MANAGED interface?
> 
> Ray
> 
> On 15 Jun 2004 at 20:56, Vladimir Ivaschenko wrote:
> 
> 
>>Make sure that ESSID is set correctly on the station in MANAGED mode.
>>
>>OSPF will work fine on machines with multiple IPs on an interface as 
>>long as the primary IP is from the same subnet on both of the machines.
>>
>>Ray Gwinn wrote:
>>
>>>>One of them should be in MANAGED mode.
>>>
>>>
>>>The above seems to have done the trick.  I now see zebra additions to the
>>>route table "ip route".  I am also able to ssh from one box to another.  Now
>>>that I have something working in a basic form, I can experiment on my own. 
>>>Thank you, Vladimir, for your assistance and your creating wisp-disp.
>>>
>>>For anyone that is lurking out there, here are some things that I have seen
>>>using ospf. Most are thanks to Vladimir.
>>>
>>>1 - One of the radios must be in MASTER mode, and the other in MANAGED mode.
>>>
>>>2 - The node that is in MASTER mode must be up an running before the MANAGED
>>>node is started.  This seems like a bug, but I am not sure.  If the MANAGED
>>>node is started first, then zebra/ospf seems not to work.
>>>
>>>3 - The radios(s) interface that are used to link between two nodes cannot
>>>have multiple IP addresses.
>>>
>>>4. - The IP addresses of the linking radios interfaces must be in the same
>>>network, and have the same netmask.
>>>
>>>5 - The default wisp-disp zebra.conf and ospfd.conf work, no matter what IP
>>>address you choose to use (so long as they meet the above conditions).
>>>
>>>Ray
>>>
>>>On 15 Jun 2004 at 9:35, Vladimir Ivashchenko wrote:
>>>
>>>
>>>
>>>>You shouldn't set both radios to MASTER unless you want to WDS. 
>>>>One of them should be in MANAGED mode.
>>>>
>>>>Ray Gwinn wrote about "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
>>>>
>>>>-- 
>>>>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
>>>
>>
>>
>>-- 
>>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
> 


-- 
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