[Olsr-users] OLSR daemon starting and running issues. Causing an error.
John Schultz
(spam-protected)
Sun Dec 16 23:53:34 CET 2012
Crap man... I have not relocated the node yet (need a wrench that I do not
have). I've enabled bole wlan cards and placed them in the conf file, Im
still not showing a link nor can I ping. An ifconfig shows the correct cell
id and essid, but that's just about it.
-----Original Message-----
From: Henning Rogge [mailto:(spam-protected)]
Sent: Sunday, December 16, 2012 2:54 PM
To: John Schultz
Cc: olsr users mailing list
Subject: Re: [Olsr-users] OLSR daemon starting and running issues. Causing
an error.
I don't know, but WEP is not really a security measurement today.
Henning Rogge
On Sun, Dec 16, 2012 at 10:50 PM, John Schultz <(spam-protected)>
wrote:
> Im going to try and move node0 further away and see if that resolves
> the situation.
>
> BTW, is it possible to use 256bit wep on an ad-hoc network or even
> wpa_supplicant?
>
> -----Original Message-----
> From: Henning Rogge [mailto:(spam-protected)]
> Sent: Sunday, December 16, 2012 2:33 PM
> To: John Schultz
> Cc: olsr users mailing list
> Subject: Re: [Olsr-users] OLSR daemon starting and running issues.
> Causing an error.
>
> Olsr can only work if your nodes form a continuous mesh. That means
> there must be a path of nodes to the destination who each can ping the
> next/previous node along the path.
>
> If some parts of your network (in this case Node 0) cannot ping any
> node of the rest of the network, Olsr cannot help you.
>
> I suggest you check your link-layer (hop-by-hop) connectivity.
>
> Henning
>
> On Sun, Dec 16, 2012 at 10:28 PM, John Schultz
> <(spam-protected)>
> wrote:
>> I cannot ping any of the devices wirelessly from node0. I have also
>> tried changing the configuration to use wlan0, in case the antenna
>> was disconnected.
>>
>> -----Original Message-----
>> From: Henning Rogge [mailto:(spam-protected)]
>> Sent: Sunday, December 16, 2012 2:19 PM
>> To: John Schultz
>> Cc: olsr users mailing list
>> Subject: Re: [Olsr-users] OLSR daemon starting and running issues.
>> Causing an error.
>>
>> All three nodes are running with the simplified config file?
>>
>> Can Node 0 ping Node 1 OR Node 2 (that should work without Olsrd).
>>
>> Henning
>>
>> On Sun, Dec 16, 2012 at 10:14 PM, John Schultz
>> <(spam-protected)>
>> wrote:
>>> OK, nodes 1 and 2 are linked, noode 0 (the gw) does not see them or
>>> do they see it.
>>>
>>> -----Original Message-----
>>> From: Henning Rogge [mailto:(spam-protected)]
>>> Sent: Sunday, December 16, 2012 2:03 PM
>>> To: John Schultz
>>> Cc: olsr users mailing list
>>> Subject: Re: [Olsr-users] OLSR daemon starting and running issues.
>>> Causing an error.
>>>
>>> Please do me a favor...
>>>
>>> remove your whole olsrd.conf and start with the
>>> "olsrd.conf.minimal_freifunk" configuration. Just use "wlan1"
>>> instead of "wlan0".
>>>
>>> Henning Rogge
>>>
>>> On Sun, Dec 16, 2012 at 10:01 PM, John Schultz
>>> <(spam-protected)>
>>> wrote:
>>>> Disregard.... Found it in olsrd.conf for the interface settings.
>>>>
>>>> -----Original Message-----
>>>> From: Henning Rogge [mailto:(spam-protected)]
>>>> Sent: Sunday, December 16, 2012 1:56 PM
>>>> To: John Schultz
>>>> Cc: olsr users mailing list
>>>> Subject: Re: [Olsr-users] OLSR daemon starting and running issues.
>>>> Causing an error.
>>>>
>>>> What is this ????
>>>>
>>>>> Ip4Broadcast 255.0.0.0
>>>>
>>>> Henning Rogge
>>>>
>>>> On Sun, Dec 16, 2012 at 9:51 PM, John Schultz
>>>> <(spam-protected)>
>>>> wrote:
>>>>> Also the tcpdump for wlan1 returns the following:
>>>>>
>>>>> tcpdump: verbose output suppressed, use -v or -vv for full
>>>>> protocol decode listening on wlan1, link-type EN10MB (Ethernet),
>>>>> capture size
>>>>> 65535 bytes
>>>>> 13:49:34.879550 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:35.881533 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:36.553726 ARP, Request who-has 255.255.0.0 tell 10.2.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:36.596202 ARP, Request who-has 255.255.0.0 tell 10.1.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:36.883538 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:37.555722 ARP, Request who-has 255.255.0.0 tell 10.2.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:37.598203 ARP, Request who-has 255.255.0.0 tell 10.1.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:38.557749 ARP, Request who-has 255.255.0.0 tell 10.2.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:38.600200 ARP, Request who-has 255.255.0.0 tell 10.1.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:40.187554 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:41.189545 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:41.862737 ARP, Request who-has 255.255.0.0 tell 10.2.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:42.191550 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:42.865748 ARP, Request who-has 255.255.0.0 tell 10.2.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:43.867729 ARP, Request who-has 255.255.0.0 tell 10.2.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:44.209200 ARP, Request who-has 255.255.0.0 tell 10.1.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:45.210194 ARP, Request who-has 255.255.0.0 tell 10.1.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:46.212194 ARP, Request who-has 255.255.0.0 tell 10.1.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:48.100575 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:49.101565 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:49.418202 ARP, Request who-has 255.255.0.0 tell 10.1.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:49.673966 ARP, Request who-has 255.255.0.0 tell 10.2.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:50.103579 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:50.420202 ARP, Request who-has 255.255.0.0 tell 10.1.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:50.675748 ARP, Request who-has 255.255.0.0 tell 10.2.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:51.422199 ARP, Request who-has 255.255.0.0 tell 10.1.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:51.677748 ARP, Request who-has 255.255.0.0 tell 10.2.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:53.407582 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:54.409573 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:54.727202 ARP, Request who-has 255.255.0.0 tell 10.1.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:55.083769 ARP, Request who-has 255.255.0.0 tell 10.2.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:55.411576 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:55.730200 ARP, Request who-has 255.255.0.0 tell 10.1.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:56.085758 ARP, Request who-has 255.255.0.0 tell 10.2.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:56.732201 ARP, Request who-has 255.255.0.0 tell 10.1.0.1,
>>>>> length
>>>>> 28
>>>>> 13:49:57.087758 ARP, Request who-has 255.255.0.0 tell 10.2.0.1,
>>>>> length
>>>>> 28
>>>>> 13:50:00.692780 ARP, Request who-has 255.255.0.0 tell 10.2.0.1,
>>>>> length
>>>>> 28
>>>>> 13:50:01.520602 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>> 13:50:01.693775 ARP, Request who-has 255.255.0.0 tell 10.2.0.1,
>>>>> length
>>>>> 28
>>>>> 13:50:02.522103 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>> 13:50:02.536201 ARP, Request who-has 255.255.0.0 tell 10.1.0.1,
>>>>> length
>>>>> 28
>>>>> 13:50:02.695765 ARP, Request who-has 255.255.0.0 tell 10.2.0.1,
>>>>> length
>>>>> 28
>>>>> 13:50:03.523596 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>> 13:50:03.538200 ARP, Request who-has 255.255.0.0 tell 10.1.0.1,
>>>>> length
>>>>> 28
>>>>> 13:50:04.540202 ARP, Request who-has 255.255.0.0 tell 10.1.0.1,
>>>>> length
>>>>> 28
>>>>> 13:50:06.729618 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>> 13:50:07.731603 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>> 13:50:08.402791 ARP, Request who-has 255.255.0.0 tell 10.2.0.1,
>>>>> length
>>>>> 28
>>>>> 13:50:08.733602 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>> 13:50:09.405786 ARP, Request who-has 255.255.0.0 tell 10.2.0.1,
>>>>> length
>>>>> 28
>>>>> 13:50:10.407787 ARP, Request who-has 255.255.0.0 tell 10.2.0.1,
>>>>> length
>>>>> 28
>>>>> 13:50:10.951204 ARP, Request who-has 255.255.0.0 tell 10.1.0.1,
>>>>> length
>>>>> 28
>>>>> 13:50:11.954198 ARP, Request who-has 255.255.0.0 tell 10.1.0.1,
>>>>> length
>>>>> 28
>>>>> 13:50:12.238623 ARP, Request who-has 255.255.0.0 tell 10.3.0.1,
>>>>> length
>>>>> 28
>>>>>
>>>>> -----Original Message-----
>>>>> From: Henning Rogge [mailto:(spam-protected)]
>>>>> Sent: Sunday, December 16, 2012 1:42 PM
>>>>> To: John Schultz
>>>>> Cc: olsr users mailing list
>>>>> Subject: Re: [Olsr-users] OLSR daemon starting and running issues.
>>>>> Causing an error.
>>>>>
>>>>> Are you seeing OLSR packets (UDP port 698) leaving your computer
>>>>> (check with tcpdump)?
>>>>>
>>>>> Do you have layer-2/3 connectivity with your neighbors (check with
>> ping)?
>>>>>
>>>>> Henning Rogge
>>>>>
>>>>> On Sun, Dec 16, 2012 at 12:15 PM, John Schultz
>>>>> <(spam-protected)>
>>>>> wrote:
>>>>>> OK.... did that, olsrd appears to be running, but there are no
>>>>>> links
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Henning Rogge [mailto:(spam-protected)]
>>>>>> Sent: Sunday, December 16, 2012 12:55 AM
>>>>>> To: John Schultz
>>>>>> Cc: olsr users mailing list
>>>>>> Subject: Re: [Olsr-users] OLSR daemon starting and running issues.
>>>>>> Causing an error.
>>>>>>
>>>>>> I would suggest removing this section:
>>>>>>
>>>>>> IpcConnect
>>>>>> {
>>>>>> MaxConnections 1
>>>>>> Host 127.0.0.1
>>>>>> Net 10.0.0.0 255.0.0.0
>>>>>> }
>>>>>>
>>>>>> You don't need it anyways unless you want to try to use the GTK
>>>>>> gui (which might contain quite some bugs because nobody cared
>>>>>> about the code for years).
>>>>>>
>>>>>> Henning Rogge
>>>>>>
>>>>>> --
>>>>>> Steven Hawkings about cosmic inflation: "An increase of billions
>>>>>> of billions of percent in a tiny fraction of a second. Of course,
>>>>>> that was before the present government."
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Olsr-users mailing list
>>>>>> (spam-protected)
>>>>>> https://lists.olsr.org/mailman/listinfo/olsr-users
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Steven Hawkings about cosmic inflation: "An increase of billions
>>>>> of billions of percent in a tiny fraction of a second. Of course,
>>>>> that was before the present government."
>>>>>
>>>>>
>>>>> --
>>>>> Olsr-users mailing list
>>>>> (spam-protected)
>>>>> https://lists.olsr.org/mailman/listinfo/olsr-users
>>>>
>>>>
>>>>
>>>> --
>>>> Steven Hawkings about cosmic inflation: "An increase of billions of
>>>> billions of percent in a tiny fraction of a second. Of course, that
>>>> was before the present government."
>>>>
>>>
>>>
>>>
>>> --
>>> Steven Hawkings about cosmic inflation: "An increase of billions of
>>> billions of percent in a tiny fraction of a second. Of course, that
>>> was before the present government."
>>>
>>>
>>> --
>>> Olsr-users mailing list
>>> (spam-protected)
>>> https://lists.olsr.org/mailman/listinfo/olsr-users
>>
>>
>>
>> --
>> Steven Hawkings about cosmic inflation: "An increase of billions of
>> billions of percent in a tiny fraction of a second. Of course, that
>> was before the present government."
>>
>>
>> --
>> Olsr-users mailing list
>> (spam-protected)
>> https://lists.olsr.org/mailman/listinfo/olsr-users
>
>
>
> --
> Steven Hawkings about cosmic inflation: "An increase of billions of
> billions of percent in a tiny fraction of a second. Of course, that
> was before the present government."
>
>
> --
> Olsr-users mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-users
--
Steven Hawkings about cosmic inflation: "An increase of billions of billions
of percent in a tiny fraction of a second. Of course, that was before the
present government."
More information about the Olsr-users
mailing list