I did that and used some other techniques to permanently change the hostname and that sort of worked, the network still recognizes the old name. I also had to add an A record in my DNS on the network and that seemed to work for now. the problem here is that the old name is still accessible.
What about editing /etc/hostname? > The domainname is set by looking up your IP, so you can set it by adding > a complete entry for a static IP in /etc/hosts. > I actually tried batman several months ago (before I had to start over from scratch) and If I remember, I had some issues getting it to work back then (I couldn't tell you what happened, I just do not remember). I Like OLSRD for the plugins - specifically the dot mapping one. I used olsrd back then as well. It seems to me one would use batman > today. OK,... this one is defiantly new to me on Linux - never set up vpns before. > WPA/WPA2 is not supported over ad-hoc to my knowledge. > WEP ist trivially breakable nowadays. > I'd just use unencrypted links and run VPNs/secured connections where > necessary. > The mesh will not have access to the internet unless the end user has that transport specifically setup for them. What I am trying to accomplish is creating the "last mile" of a transport system to remove all wires from the house, business, etc... For now, this network is isolated completely. The only way I am even doing apt updates are with an internal apt repo. If you use the mesh as an 'internal' network, WEP won't protect you, if > it is just a transfer network to the next internet gateway, be aware > e.g. HTTP will just be plain readable once it leaves your protected > mesh anyway. > Interesting, I was not aware of that. Olsrd, if I remember correctly, just meant to use iwconfig and bring the > interface into ad-hoc mode + place an ssid, then starting olsrd > (configured on these interfaces, ofc). > - John
_______________________________________________ Voyage-linux mailing list [email protected] http://list.voyage.hk/mailman/listinfo/voyage-linux
