1 Jan 2012 18:39
Re: Re: ad-hoc network assist
On Sat, Dec 31, 2011 at 07:59:48AM -0700, John Schultz wrote: > 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. Well, network name resolution ist quite different from the hostname. I'd check DNS A and PTR records as well as /etc/hosts&Co. > OK,... this one is defiantly new to me on Linux - never set up vpns before. It is not that hard. Depending on what you want to achieve you have different options. What you describe sounds like a typical 'Freifunk' setup. In a typical freifunk network, the participants take care to encrypt their traffic on application/protocol level, e.g. HTTPS, SSMTP, SMTP/TLS, IMAPS, IMAP/TLS, ircs, ssh If that's not possible for some protocol you tunnel it e.g. via - ssh with portforwarding (single ports, while networks if needed) - openvpn (networks) - tinc (networks) We run OpenVPN on Alix 2D13 encrypting 35MBit/s last time I tested. The AES crypto unit had not been in use unless it gets autodetected and autoused. > 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(Continue reading)
"Voyage Linux | { x86 Embedded Linux = Green computing }"
RSS Feed