Hi Fred, There are a few issues with your script:
On Mon, Jul 30, 2012 at 10:38 AM, fred veldini <[email protected]> wrote: > iw phy phy0 interface add mesh0 type mp mesh_id 5gsbaby adding an interface with mesh_id is actually the old API for joining / starting a mesh. You should omit that argument. > iw dev mesh0 set channel 36 HT40+ > ifconfig mesh0 172.29.29.1 netmask 255.255.255.0 up > iwconfig mesh0 channel 36 Setting the channel and type is handled by authsae in recent kernels, so this shouldn't be necessary. > /bin/sleep 1 > iw dev mesh0 mesh join 5gsbaby authsae implements a mesh peering state machine and therefore handles joining the mesh. Starting an open mesh before launching authsae almost certainly won't work. > iw dev mesh0 scan Why? :P > /bin/sleep 1 > meshd -b This is the BSD mesh daemon and is not needed. > /bin/sleep 1 > /sbin/meshd-nl80211 -c /etc/authsae.cfg -i mesh0 -s 5gsbaby > > I checked the interface and mesh0 comes up fine and connects to other mesh > nodes without authsae > > I add an IP Address to the mesh0 interface and can ping and transfer files > without any issue > > Maybe I'm starting authsae incorrectly. Please try again with the changes above. You should only have to add an interface then start authsae on it to establish a secure mesh. Thomas _______________________________________________ Devel mailing list [email protected] http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
