Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    [SOLVED]Help on turning a laptop on an AP with VitualBox or VMWare

    Scheduled Pinned Locked Moved Virtualization
    4 Posts 2 Posters 2.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Z
      zehle
      last edited by

      Edit :
      just tryied the same config with VMWare Workstation, and have the same issue… any help plz

      hi all
      hear is my config :
      laptop with 1 etherned, and 1 wifi card.
      ethenet is connected to my adsl router.

      i want to trun it to an Access Point and manage traffic through pfSense.

      1st step : enable hostednetwork (virtual wifi miniport)

      
      netsh wlan set hostednetwork mode=allow ssid=pfSense key=pfSensePWD
      netsh wlan start hostednetwork
      
      

      2nd step:sharing ethenet connection

      
      open ethernet card properties
      under "Sharing" tab - check box "Allow other network users to connect through this computer's internet connection"
      Select under "Home networking connection"   - Microsoft Virtual WiFi Miniport"
      
      

      at this point, i can connect to my wifi hostednetwork and have internet access.

      IPs clients : 192.168.137.0/24

      3rd step: installing and configuring pfSense with vitualbox

      
      VitualBox is configured with 2 cards
      - for WAN : a bridged card to ethernet
      - for LAN : a bridged card to vitrual wifi miniport 
      
      - WAN IP is automatic from dhcp
      - setting LAN IP to 192.168.137.250 (in the same scope of hostednetwork) 
      
      

      Clients can ping pfSense LAN and have access to internet. But i cant manage traffic with pfSense.
      Clients has these address config :

      
      IP : 192.168.137.x
      mask : 255.255.255.0
      dns : 192.168.137.1 
      gateway : 192.168.137.1
      dhcp : 192.168.137.1
      
      192.168.137.1 is the IP of wifi miniport
      
      

      4th step : try

      • disabled internet sharing (2nd step)
      • reconfiguring wifi miniport IP to 192.168.137.1 with mask 255.255.255.0
      • enabled DHCP over LAN interface to force clients to use pfSense as default gateway
        now clients IPs are like
      
      IP : 192.168.137.x
      mask : 255.255.255.0
      dns : 192.168.137.250 
      gateway : 192.168.137.250
      dhcp : 192.168.137.250
      
      192.168.137.250 is pfSense's IP.
      
      

      now from pfSense, i can ping clients and internet. but from clients i can only ping local, havent internet access.

      what wrong i did ?

      thanks in advance for help

      Zehle.

      1 Reply Last reply Reply Quote 0
      • Z
        zehle
        last edited by

        Solved using Microsoft loopback adapter and then disabling tcp/ip v4 and v6 over the wan

        more details http://timita.org/wordpress/2011/07/29/protect-your-windows-laptop-with-pfsense-and-virtualbox-part-1-preamble/

        thx for him.

        1 Reply Last reply Reply Quote 0
        • S
          sschaub
          last edited by

          @zehle:

          Solved using Microsoft loopback adapter and then disabling tcp/ip v4 and v6 over the wan

          more details http://timita.org/wordpress/2011/07/29/protect-your-windows-laptop-with-pfsense-and-virtualbox-part-1-preamble/

          thx for him.

          I am trying to do a similar setup, and I don't see how the loopback adapter comes into play. I read the linked article, and it seems to be for someone who is running pfsense on a standalone laptop, not a laptop intended as a wireless AP… I would really appreciate if you could share additional details on your config to help me connect the dots.

          1 Reply Last reply Reply Quote 0
          • S
            sschaub
            last edited by

            @sschaub:

            @zehle:

            Solved using Microsoft loopback adapter and then disabling tcp/ip v4 and v6 over the wan

            I am trying to do a similar setup, and I don't see how the loopback adapter comes into play.

            Ok, never mind. I think what is needed is to follow the instructions in the linked article to install the loopback adapter. Then, use internet connection sharing to share the loopback adapter with the Ad-hoc network.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.