InfrastructureAdhoc

back to http://scratchpad.wikia.com/wiki/Sasecurity {{{ Sudden problems with MeshBox

That's right... I forgot if you set the secondary interface to infrastructure (it defaults to ad-hoc), you'll get a 10.x.x.x address.

> We had this appearing, it was because the second mode in wiana was set > to infrastructure on one of the nodes

> That is either a secondary radio interface (like a box with 2 WiFi >> cards in it), or another meshbox that has not been registered with >> Wiana and is meshing with your mesh.

>> Looks like you may have a leecher trying to use your network if you >> don't have boxes with 2 interfaces. I can't think of any other >> instance that would make a 10.x.x.x interface appear.

>> BTW, each time the box that is generating that IP is rebooted, it >> will change. To keep rogue meshboxes out, you'll have to change some >> stuff in Wiana. I'll let some others comment on that - as I'm not >> sure of the exact settings.

>>> All the hardware had been working fine for over a year so didn't see >>> any reason for the cabling to be bad. the CAT5 worked fine because I >>> could ping while logged in just fine. Right now everything seems to >>> work fine and the problem seems to be related to interference.

>>> I can now ping my outside node without dropping any packets. I've >>> had interference issues before but none that have lasted 12 hours! >>> Maybe someone was on the phone all day. Earlier, I could ping out to >>> my far node intermittently with 75% to 100% packet loss. Hopefully

I >>> dont see the same thing happening tomorrow. I suppose the best thing >>> I could do is switch them over to a different channel.

>>> Can anyone please explain to me what the circle containing >>> 10.11.15.20 means in this image? >>> http://the45.net/~ryan/tp.php.png >>>

>>>> One of the assumption I found out was problem didn't have to be >>>> software or hardware related. Verify your environment. Ensure >>>> that nobody is transmitting on the same frequency and ESSID. >>>> >>>> Try to systematically eliminated outside influences first. >>>> >>>> Once that is done verify that the hardware cable etc. >>>> >>>> Sometimes it can be a bad cable. try to first swap MeshAP location >>>> and verify that it is not the units.

>>>>> I'm running an older version of the meshbox, one that is at least >>>>> a year old. 'cat /etc/VERSION' returns 25. I have been using it >>>>> just fine for all this time. >>>>> >>>>> I have 3 meshboxes and they are all indoors. 1 is in my room, it >>>>> works perfectly. 1 is in my dining room and bridges to another >>>>> apartment. Before today everything worked fine, now suddenly, >>>>> without being touched, the meshbox in my dining room has quite >>>>> functioning normally. >>>>> >>>>> I am losing ping packets to the one in my dining room but not to >>>>> any of the other ones. I have no idea how to troubleshoot this. >>>>> The pings and test transfers seem to work fine off the wire, so it >>>>> is clearly something wrong with wireless. I thought it may be a >>>>> hardware issue so I swapped out my wifi cards, this didn't fix >>>>> anything. >>>>> >>>>> The range also seems affected on the mesh. I used to be able to >>>>> walk several apartments down and use the mesh just fine, now I can >>>>> only use it and get a signal from half as far away. The thing that >>>>> most worries me is that after I reboot the box I get the normal >>>>> 1,024kbps download that I have throttled everyone to. But after a >>>>> few retransfers my transfers level off at 612kbps. >>>>> >>>>> Should I just update the software. Can the newer software mesh >>>>> with the older ones?

10,x,x,x, range
That's right... I forgot if you set the secondary interface to infrastructure (it defaults to ad-hoc), you'll get a 10.x.x.x address. > We had this appearing, it was because the second mode in wiana was set to infrastructure on one of the nodes

>> That is either a secondary radio interface (like a box with 2 WiFi >> cards in it), or another meshbox that has not been registered with >> Wiana and is meshing with your mesh.

>> Looks like you may have a leecher trying to use your network if you >> don't have boxes with 2 interfaces. I can't think of any other >> instance that would make a 10.x.x.x interface appear.

>> BTW, each time the box that is generating that IP is rebooted, it >> will change. To keep rogue meshboxes out, you'll have to change some >> stuff in Wiana. I'll let some others comment on that - as I'm not >> sure of the exact settings. >>> All the hardware had been working fine for over a year so didn't see >>> any reason for the cabling to be bad. the CAT5 worked fine because I >>> could ping while logged in just fine. Right now everything seems to >>> work fine and the problem seems to be related to interference. >>> >>> I can now ping my outside node without dropping any packets. I've >>> had interference issues before but none that have lasted 12 hours! >>> Maybe someone was on the phone all day. Earlier, I could ping out to >>> my far node intermittently with 75% to 100% packet loss. Hopefully I >>> dont see the same thing happening tomorrow. I suppose the best thing >>> I could do is switch them over to a different channel. >>> >>> Can anyone please explain to me what the circle containing >>> 10.11.15.20 means in this image? >>> http://the45.net/~ryan/tp.php.png

>>>> One of the assumption I found out was problem didn't have to be >>>> software or hardware related. Verify your environment. Ensure >>>> that nobody is transmitting on the same frequency and ESSID. >>>> >>>> Try to systematically eliminated outside influences first. >>>> >>>> Once that is done verify that the hardware cable etc. >>>> >>>> Sometimes it can be a bad cable. try to first swap MeshAP location >>>> and verify that it is not the units.

>>>>> I'm running an older version of the meshbox, one that is at least >>>>> a year old. 'cat /etc/VERSION' returns 25. I have been using it >>>>> just fine for all this time. >>>>> >>>>> I have 3 meshboxes and they are all indoors. 1 is in my room, it >>>>> works perfectly. 1 is in my dining room and bridges to another >>>>> apartment. Before today everything worked fine, now suddenly, >>>>> without being touched, the meshbox in my dining room has quite >>>>> functioning normally.

>>>>> I am losing ping packets to the one in my dining room but not to >>>>> any of the other ones. I have no idea how to troubleshoot this. >>>>> The pings and test transfers seem to work fine off the wire, so it >>>>> is clearly something wrong with wireless. I thought it may be a >>>>> hardware issue so I swapped out my wifi cards, this didn't fix >>>>> anything.

>>>>> The range also seems affected on the mesh. I used to be able to >>>>> walk several apartments down and use the mesh just fine, now I can >>>>> only use it and get a signal from half as far away. The thing that >>>>> most worries me is that after I reboot the box I get the normal >>>>> 1,024kbps download that I have throttled everyone to. But after a >>>>> few retransfers my transfers level off at 612kbps. >>>>> >>>>> Should I just update the software. Can the newer software mesh >>>>> with the older ones? }}}