• Announcements

    • MannDude

      Current state of vpsBoard   02/04/2017

      Dear vpsBoard members and guests:

      Over the last year or two vpsBoard activity and traffic has dwindled. I have had a change of career and interests, and as such am no longer an active member of the web hosting industry.

      Due to time constraints and new interests I no longer wish to continue to maintain vpsBoard. The web site will remain only as an archive to preserve and showcase some of the great material, guides, and industry news that has been generated by members, some of which I remain in contact to this very day and now regard as personal friends.

      I want to thank all of our members who helped make vpsBoard the fastest growing industry forum. In it's prime it was an active and ripe source of activity, news, guides and just general off-topic banter and fun.

      I wish all members and guests the very best, whether it be with your business or your personal projects.


Search the Community

Showing results for tags 'wlan'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • vpsBoard
    • Announcements & Contests
    • Industry News
  • Virtual Private Servers
    • General Talk
    • Operating a VPS Business
    • Tutorials and Guides
    • Questions and Answers
  • The Lounge
    • The Pub (Off topic discussion)
    • Coding, Scripting & Programming
    • SBC, ARM, Home Automation
  • Marketplace & Reviews
    • Reviews
    • VPS Offers
    • Other Offers
    • Service Requests

Found 2 results

  1. Install required packages: sudo apt-get install hostapd dnsmasqSet static ip to your wlan interface: nano /etc/network/interfacescontent: (check for a single wlan0 entry!) iface wlan0 inet static address netmask a configuration to hostap: nano /etc/default/hostapdcontent: (add config file line): # Defaults for hostapd initscript # # See /usr/share/doc/hostapd/README.Debian for information about alternative # methods of managing hostapd. # # Uncomment and set DAEMON_CONF to the absolute path of a hostapd configuration # file and hostapd will be started during system boot. An example configuration # file can be found at /usr/share/doc/hostapd/examples/hostapd.conf.gz # DAEMON_CONF="/etc/hostapd/hostapd.conf"If you are not sure what driver is needed check your usb devices (driver name will be disbplayed) lsusb -tlsusb -t /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M |__ Port 1: Dev 2, If 0, Class=vend., Driver=smsc95xx, 480M |__ Port 5: Dev 3, If 0, Class=vend., Driver=rtl8192cu, 480M Create hostapd.conf: nano /etc/hostapd/hostapd.confcontent: # interface for ap interface=wlan0 # driver of wlan stick driver=rtl871xdrv ctrl_interface=/var/run/hostapd ctrl_interface_group=0 # wlan ap configuration ssid=RaspberryPi channel=1 hw_mode=g ieee80211n=0 # wlan security wpa=2 wpa_passphrase=super-secure-password wpa_key_mgmt=WPA-PSK wpa_pairwise=CCMP rsn_pairwise=CCMP # country code country_code=US Add dnsmasq configuration: nano /etc/dnsmasq.confContent: (two important lines) # Configuration file for dnsmasq. # If you want dnsmasq to listen for DHCP and DNS requests only on # specified interfaces (and the loopback) give the name of the # interface (eg eth0) here. # Repeat the line for more than one interface. interface=wlan0 # Uncomment this to enable the integrated DHCP server, you need # to supply the range of addresses available for lease and optionally # a lease time. If you have more than one network, you will need to # repeat this for each network on which you want to supply DHCP # service. dhcp-range=,,,12h #set default gateway (if wanted) #dhcp-option=3, Restart services: sudo service hostapd restart sudo service dnsmasq restart Enable IP forwarding: nano /etc/sysctl.confUncomment: # Uncomment the next line to enable packet forwarding for IPv4 net.ipv4.ip_forward=1Activate settings: sudo sysctl -p Setup forwarding rules: nano /etc/network/if-up.d/apforwarding && chmod +x /etc/network/if-up.d/apforwarding content: # !/bin/sh iptables --table nat --append POSTROUTING --out-interface eth0 -j MASQUERADE iptables --append FORWARD --in-interface wlan0 -j ACCEPT Reboot your Raspberry Pi.
  2. Your own OpenVPN WLAN

    I do have some devices where I am not able to install an OpenVPN client. But I want to use an US IP for these devices. You might think that the only way to get an US IP is to root/patch the devices. The more elegant way is to have a device that is doing the OpenVPN client job. Therefore I bought a cheap second router (30$) and installed dd-wrt on it. If you log into the web interface you can go to the section: Services -> VPN -> OpenVPN Client Enter Server IP, Port, Tunnel Protocol (UDP), Tunnel Device (TUN), Encryption Cipher (Blowfish CBC), Hash Algorithm (SHA1), Use LZO Compression (enabled) and NAT (enabled). Afterwards you can enter (copy/paste): CA Cert Public Client Cert Private Client Key On some routers you have to add following command to enable masquerading: Go to Administration -> Commands enter: iptables -t nat -A POSTROUTING -j MASQUERADE and press the "Save firewall" button. That's it. Restart the second router. Now all internet traffic of this router is forwarded through the OpenVPN tunnel. Every devices connected to this router (LAN or WLAN) does not even know that it is using an OpenVPN tunnel. It is just using on US IP (depends on the localtion of your vps). I plugged my second router right into the network of my first router. This can be done through setting the connection type to "Automatic configuration - DHCP" on the submenu: Setup -> Basic Setup. This ensures that the second router is using the internet connection of the first router to establish his own OpenVPN connection.