Open geoffmunn opened 9 years ago
Hi @geoffmunn sorry for the late response - we are wrapping up a major refactor of the subnodes project.
i haven't seen the "No DHCPOFFERS" messaging before, so i'm not sure off the top of my head. Strange it's trying to communicate w/eth0. Can you tell me more about your set up? What kind of RPi are you using and which radios exactly?
Hi there,
I think this might have been a user error on my part. I resolved it via a clean installation of Jessie, but unfortunately I never got subnodes working.
The Edimax wifi adapter you recommend now comes with the rt8192cu chipset (on Edimax EW-7811un v2.1), and this does appear to support ad-hoc networking but batman never found any neighbours.
Also (if you want to get complicated), any adapter with the rt8192cu chipset or rt8188cu chipset will support being set up as an access point, but the rt8188cu definitely doesn't support ad-hoc mode.
I tried all sorts of adapters, in order to find one with the rt5370, but it's a rare chipset these days and I couldn't find any that had this.
:(
Hi Geoff,
I can definitely recommend some adapters that will work for you. I also took out the check for rt5370 - the main thing is that the adapter works with the nl80211 driver.
The reason why i use radios that work with that driver is because they work w/raspberry pis out of the box. i've actually never had luck with edimax drivers. where did you see me recommend that? if i did recommend it somewhere, it was a mistake for sure!
This is the one i recommend using on the subnodes site: http://www.amazon.com/gp/product/B007BWFXYS/ and that one will work with the RPi and in ad hoc + AP mode.
I just updated the master branch of subnodes the other night, and tested it to make sure it was working, if you wanted to try it again. Also, we are going to push out a new release hopefully next week that separates out the chat app into its own repo and instead installs a dashboard that lets you install individual node apps for a customized subnodes build. I also would like to support other wifi adapters, after we get this next release out.
Thanks for getting in touch - let me know if my suggestions above help.
Sarah
On Tue, Nov 3, 2015 at 7:58 PM, geoffmunn notifications@github.com wrote:
Hi there,
I think this might have been a user error on my part. I resolved it via a clean installation of Jessie, but unfortunately I never got subnodes working.
The Edimax wifi adapter you recommend now comes with the rt8192cu chipset (on Edimax EW-7811un v2.1), and this does appear to support ad-hoc networking but batman never found any neighbours.
Also (if you want to get complicated), any adapter with the rt8192cu chipset or rt8188cu chipset will support being set up as an access point, but the rt8188cu definitely doesn't support ad-hoc mode.
I tried all sorts of adapters, in order to find one with the rt5370, but it's a rare chipset these days and I couldn't find any that had this.
:(
— Reply to this email directly or view it on GitHub https://github.com/chootka/subnodes/issues/11#issuecomment-153537409.
Sarah Grant Technical Lead
the_barbarian_group 112 W 20th Street, 7th floor New York, NY 10011
P: 212-599-9292 Twitter: @woolypixel
...........................................
Winner of the Inaugural Grand Prix Innovation Cannes Lion 2013
libcinder.org http://www.libcinder.org/
It's Gonna be Awesome™ barbariangroup.com
Hmmm, I could swear that the subnodes.org page used to link to an Amazon page with the Edimax adapter (it doesn't anymore).
Anyhoo, all my Raspberry Pi's are in use with a combination of custom-code and adapters that mostly work, but if another one becomes available then I'll try the new release.
Thanks for helping :)
Edimax 7811 uses Realtek chipset drivers which are in Debian repos. Try to "apt-get install firmware-realtek". Depending on the distribution (such as Raspbian) this package may or may not be in the default selection.
The installation appeared to go successfully (on a fully updated version of Weezy), but when I reboot I get the following messages:
Listening on LPF/eth0/b8:27:eb:82:ea:1d Sending on LPF/eth0/b8:27:eb:82:ea:1d Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 No DHCPOFFERS received
I have two wireless adaptors plugged into the Pi, and they both work under normal circumstances. If I edit the interfaces file, and change 'eth0' to 'wlan0' then it will receive an IP address upon reboot, however I don't think it's working as a mesh node at this point.
Any ideas?