[Olsr-users] 3 PCs setup for OLSR
Markus Kittenberger
(spam-protected)
Tue Sep 8 14:31:06 CEST 2009
On Tue, Sep 8, 2009 at 8:42 AM, <(spam-protected)> wrote:
> Hi Markus,
> thanks Markus.....:)
>
thanks for the feedback *G
> You were right as I was getting some other outputs in #ip rule
> command as I was having some force entries for routing table select.
>
you can also change them, so that the table olsrd uses gets used fo this
parts of your routing you want him to get used for *G
> I changed the olsrd/conf file and commented the RtTable entries to
> select kernel default table by olsrd.
> Now in setup PC1<-------->(eth0)PC2(eth1)<----------->PC3, We are
> able to ping PC1 frpm PC3 and vice-versa.
> Now I have to run a vedio streaming from PC1 to PC3. Do you have any
> idea to do it?
use any software you like,..
.
or the maybe easiest solution:
attach an ip webcam (with its own http server) on one olsr node, and
announce the ip of the webcam via hna (olsr config-option) to the other
nodes
Markus
> Vijai
>
>
> -----Original Message-----
> From: Markus Kittenberger [mailto:(spam-protected)] On
> Behalf Of Markus Kittenberger
> Sent: Monday, August 24, 2009 6:12 PM
> To: Vijai Kumar (WT01 - Joint CEO Office)
> Subject: Re: [Olsr-users] 3 PCs setup for OLSR
>
> Am 24.08.2009, 14:05 Uhr, schrieb <(spam-protected)>:
>
> > Thanks again Markus for help.
> > I tried your suggestions ann now I am able to ping pc1 and pc2 from
> pc2.
> > but even after running I am not able to ping PC1 from PC3 and
> > vice-versa.
> > I have the setup as follows with bmf plugin running with olsrd. I
> > disabled the firewall at all the PCs.I attached the below output from
> > olsrd.
> >
> > I hope to get any clue from you...:)
> >
> > PC1<-------->(eth0)PC2(eth1)<----------->PC3
> >
> > PC1:Eth0:
> > IP Address: 10.105.12.200
> > Bcast Address: 10.105.12.255
> > Subnet mask: 255.255.255.0
> > Def Gateway: 10.105.12.1
> > Default route: 10.105.12.1
> > Primary DNS: 10.105.51.100
> > Primary DNS: 10.105.50.100
> >
> > PC2:Eth0:
> > IP Address: 10.105.12.201
> > Bcast Address: 10.105.12.255
> > Subnet mask: 255.255.255.0
> > Def Gateway: 10.105.12.1
> > Default route: 10.105.12.1
> > Primary DNS: 10.105.51.100
> > Primary DNS: 10.105.50.100
> >
> > Other subnet:
> > PC2:Eth1:
> > IP Address: 10.105.10.202
> > Bcast Address: 10.105.10.255
> > Subnet mask: 255.255.255.0
> > Def Gateway: 10.105.12.1
> > Default route: 10.105.12.1
> > Primary DNS: 10.105.51.100
> > Primary DNS: 10.105.50.100
> >
> > PC3:Eth0:
> > IP Address: 10.105.10.203
> > Bcast Address: 10.105.10.255
> > Subnet mask: 255.255.255.0
> > Def Gateway: 10.105.12.1
> > Default route: 10.105.12.1
> > Primary DNS: 10.105.51.100
> > Primary DNS: 10.105.50.100
> >
> > While I ping PC1 from PC3 I am getting the follwing message in
> > wireshark at PC1----
> > Source: 10.105.10.203 Dest: 10.105.10.200, protocol: ICMP, msg: Echo
> > (ping) request.
> > Source: MAC address of PC3 Dest: broadcast, protocol: ARP, msg: who
> > has 10.105.12.1? Tell 10.105.10.200
>
> this means that pc3 searches for its (possible wrong) Default gateway
> which it only does if there no olsr routes which mach better than the
> default route
>
> > The same message is displayed in wireshark at PC2:eth0 interface
> >
> > The fillowings are the output of olsrd at 3 PCs--->
> >
> > Setup:
> > PC1:0.105.12.200<-------->0.105.12.201:(eth0)PC2(eth1):0.105.10.202<--
> > --
> > ------->10.105.10.203:PC3
> > ############################ PC1 OLSR out put
> > #######################################################
> > --- 15:58:18.761360
> > ----------------------------------------------------
> > LINKS
> >
> > IP address hyst LQ ETX
> > 10.105.12.201 0.000 0.988/0.988 1.024
> >
> > --- 15:58:18.761408 ----------------------- TWO-HOP NEIGHBORS
> >
> > IP addr (2-hop) IP addr (1-hop) Total cost
> > 10.105.10.203 10.105.12.201 2.048
> >
> > --- 15:58:18.761445 -------------------------------------------------
> > TOPOLOGY
> >
> > Source IP addr Dest IP addr LQ ETX
> > 10.105.12.200 10.105.12.201 0.988/0.988 1.024
> > 10.105.12.201 10.105.12.200 0.988/0.988 1.024
> > 10.105.12.201 10.105.10.203 0.988/0.988 1.024
> > 10.105.10.203 10.105.12.201 0.988/0.988 1.024
> > ######################################################################
> > ##
> > ###############################
> >
> > PC1:0.105.12.200<-------->0.105.12.201:(eth0)PC2(eth1):0.105.10.202<--
> > --
> > ------->10.105.10.203:PC3
> > ############################ PC2 OLSR out put
> > ###########################################################
> > --- 15:58:46.944567
> > ----------------------------------------------------
> > LINKS
> >
> > IP address hyst LQ ETX
> > 10.105.10.203 0.000 0.988/0.988 1.024
> > 10.105.12.200 0.000 0.988/0.988 1.024
> >
> > --- 15:58:46.944622 ----------------------- TWO-HOP NEIGHBORS
> >
> > IP addr (2-hop) IP addr (1-hop) Total cost
> >
> > --- 15:58:46.944641 -------------------------------------------------
> > TOPOLOGY
> >
> > Source IP addr Dest IP addr LQ ETX
> > 10.105.12.200 10.105.12.201 0.988/0.988 1.024
> > 10.105.12.201 10.105.12.200 0.988/0.988 1.024
> > 10.105.12.201 10.105.10.203 0.988/0.988 1.024
> > 10.105.10.203 10.105.12.201 0.988/0.988 1.024
> looks correct, but as it doens`t work,...
>
> check (for exampl eon pc3) what
> #ip route
> (should contain routes to the other olsr routers) and #ip rule (should
> be only 3 lines) print out
>
>
> and pls leave the bmf plugin away (at least for the moment)
>
>
> if ip route doen`s print the expected routes configure httpinfo (or
> txtinfo), and check there if the links get symmetric, and if the olsr
> wants to create routes (i mean if it list routes there)
>
> lg Markus
>
> Please do not print this email unless it is absolutely necessary.
>
> The information contained in this electronic message and any attachments to
> this message are intended for the exclusive use of the addressee(s) and may
> contain proprietary, confidential or privileged information. If you are not
> the intended recipient, you should not disseminate, distribute or copy this
> e-mail. Please notify the sender immediately and destroy all copies of this
> message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses. The
> company accepts no liability for any damage caused by any virus transmitted
> by this email.
>
> www.wipro.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20090908/1abeecb9/attachment.html>
More information about the Olsr-users
mailing list