Does anyone have a sample OLSR.conf file for getting UBUNTU set up as a node. I actually have it running, and my WRT54GL node shows up in the links screen, but when I connect to the node there it is not showing me as a neighbor. Also having trouble (I think) with nameservice,

Running 1.1.2 on the WRT54 and also on the MAP. I can access the node fine even from my Samsung G5. Just can't seem to get the node fully running on my laptop!

Dick Hanna

K3VYY

k3vyy@arrl.net

Interesting.

I see in both packet sets a DHCP discover from the laptop (normal), a DHCP offer from the Linksys (normal)  but no response (abnormal) from the laptop when its plugged in direct but when your going through the HP the Sony responds (correctly) with a DHCP ACK.

I'm not really sure why that is the case at the moment.  From the packet log though it appears the laptop is choosing not to respond to the packets and not that the Linksys node is having an issue directly.

I don't see any obvious connection stopper on first glance (will have to dig deeper to see if the packet has any issues in the offer to be sure)  but even that seems unlikely as it works through a different switch but not through the direct.

Is your PC reporting line drops or interface resets at all or are the lights on the connection going out when they should be staying solid to imply that the laptop is loosing a link layer connection?   We really didn't mess with anything down at that level... but that would be the only thing I can think of based on this packet return is that the laptop thinks the connection has dropped and doesn't process the packet (even though it received the packet)

I tried to attach the files, but it said "not allowed".  Hopefully you can retrieve them here.

KJ4AJP.pcap will be with the Sony/Realtek laptop connected to the node, the Sony doing the capture not getting an IP.

KJ4AJP_2.pcap is for your reference.  One of our network admins set aside 3 ports in a private VLAN on the HP 2610-48 here, a "virtual dumb hub" if you will.  With the HP switch between the Sony and the node the Sony doing the capture was issued an IP almost immediately. 

The capture with the HP was the second time, since when it first happened (we set this up before we connected directly to the node) we were surprised it worked and wanted to try again after we confirmed connecting directly to the node failed.

Linksys builds are based on OpenWRT 7.09.

OpenWRT 12.09 does not support WRT54 hardware so installing that will be a no go.

A network capture (tcpdump/wireshark) would do me a lot more good than creating a list of devices you have working and not working if you wanted this to be investigated further and confirmed as a bug.

FWIW, W7BDB and I have been emailing about the issue, and I've started a list of what's working and not.  If someone has a Realtek RTL8102E or RTL8139/8102 that a v1.1.2 node is giving an IP to, let us know.  I'm working on how to find out what ethernet controller is in the two Wanscam JW008 IP cameras I have that are not getting an IP, W7BDB has a Kavass HD P2P camera that also doesn't connect.

BBHN->ticket:51 and BBHN->ticket:52

A tcpdump/wiresharek capture of the devices (from the node and from the laptop) may yield some additional information.

I can't see why this would work in 1.0 and not 1.1.2 as nothing should of changed in this lower level to affect this. I don't think I have any broadcom chips in my network at the moment only realtek (aside from the  Linksys node)

Also I assume your testing using the same port that works on one pc to rule out any bad ports on the device.

I upgraded 7 nodes no issues, but to of them I cant get to the Set up page, I have the correct user name and password, I have reset my PC it just never takes me to the set up page when I select on two units.

I fear they may be hosed .... any ideas?

thank you,

Marcus

 think it may have been a browser issue, switched PC's and its working ... sorry.

A mesh network is different than a traditional WIFI network in many ways.

In the case of BBHN when we speak of a backbone its a link from one area to another area. This could be on any band.

In the case of the mesh packets take the best route to get where they are going (lowest cost.) Packets that are local will stay local, packets that need to get to another area will take the least cost path to get here. In some cases this could actually mean staying on Band A the entire time (because areas can fuse together)  and in other cases this may mean that the primary path is to go from band A to band B back to band A through some nodes (Example: a mountain top hilltop that acts as a backbone feeder)  In this case you want all the areas to be able to reach each other (the mesh protocol handles this).

So yes you would use an unmanaged switch to combine the setup as described.

Also are we talking Linksys or Ubiquiti devices.

3rd PC is seen.  

<chuckle> Maybe BH 1.1.2 only works with Dells? That's what the Win7 desktop used for the flash and the newly attached XP laptop are.

Problem laptop is a Sony Vaio with Win7, I did the release & renew as well as a shutdown and startup with no discovery.  Also a 4th device, an IP cam, is not discovered.

How about if you bring a 3rd pc into the mix?

I'm inclined to believe  it is something going on with the laptop most likely, or you have plugged  more than the number of devices DHCP leases were configured for in and no leases are left.

The fact that one PC works tends to imply that the DHCP server is functioning.

Did  you force the laptop to release (ipconfig /release) and make sure all the cables are connected then ipconfig /renew?   Windows can be a bit stubborn sometimes if it brings up the interface without an address on eventually obtaining a new proper address.