Wireless Access Point not visible to other devices

[Andrew]

Hello. I have bought a USB wireless dongle with the intention to create a wireless access point in Kubuntu so other devices can share my LAN connection. I have confirmed it is capable of this by using "iw list", "AP" is listed under "supported interface types".

I go to Configure Network Connections and create a "Wi-Fi (Shared)" connection. I set it so "All users may connect to this network", set an SSID, Mode as Access Point, Restricted to the USB dongle device, NOT Hidden, and setup some Security, but when it click OK to create the network it is only visible to the device which has the USB dongle connected to it, no other devices can see it even though they are easily close enough. Any suggestions would be much appreciated.

> iw list

Wiphy phy3
      max # scan SSIDs: 4
      max scan IEs length: 2257 bytes
      Retry short limit: 7
      Retry long limit: 4
      Coverage class: 0 (up to 0m)
      Device supports RSN-IBSS.
      Device supports T-DLS.
      Supported Ciphers:
              * WEP40 (00-0f-ac:1)
              * WEP104 (00-0f-ac:5)
              * TKIP (00-0f-ac:2)
              * CCMP (00-0f-ac:4)
              * 00-0f-ac:10
              * GCMP (00-0f-ac:8)
              * 00-0f-ac:9
              * CMAC (00-0f-ac:6)
              * 00-0f-ac:13
              * 00-0f-ac:11
              * 00-0f-ac:12
      Available Antennas: TX 0x1 RX 0x1
      Configured Antennas: TX 0x1 RX 0x1
      Supported interface modes:
               * IBSS
               * managed
               * AP
               * AP/VLAN
               * monitor
               * mesh point
               * P2P-client
               * P2P-GO
               * Unknown mode (11)
      Band 1:
              Capabilities: 0x116e
                      HT20/HT40
                      SM Power Save disabled
                      RX HT20 SGI
                      RX HT40 SGI
                      RX STBC 1-stream
                      Max AMSDU length: 3839 bytes
                      DSSS/CCK HT40
              Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
              Minimum RX AMPDU time spacing: 8 usec (0x06)
              HT TX/RX MCS rate indexes supported: 0-7
              Bitrates (non-HT):
                      * 1.0 Mbps
                      * 2.0 Mbps (short preamble supported)
                      * 5.5 Mbps (short preamble supported)
                      * 11.0 Mbps (short preamble supported)
                      * 6.0 Mbps
                      * 9.0 Mbps
                      * 12.0 Mbps
                      * 18.0 Mbps
                      * 24.0 Mbps
                      * 36.0 Mbps
                      * 48.0 Mbps
                      * 54.0 Mbps
              Frequencies:
                      * 2412 MHz [1] (20.0 dBm)
                      * 2417 MHz [2] (20.0 dBm)
                      * 2422 MHz [3] (20.0 dBm)
                      * 2427 MHz [4] (20.0 dBm)
                      * 2432 MHz [5] (20.0 dBm)
                      * 2437 MHz [6] (20.0 dBm)
                      * 2442 MHz [7] (20.0 dBm)
                      * 2447 MHz [8] (20.0 dBm)
                      * 2452 MHz [9] (20.0 dBm)
                      * 2457 MHz [10] (20.0 dBm)
                      * 2462 MHz [11] (20.0 dBm)
                      * 2467 MHz [12] (20.0 dBm) (no IR)
                      * 2472 MHz [13] (20.0 dBm) (no IR)
                      * 2484 MHz [14] (20.0 dBm) (no IR)
      Supported commands:
               * new_interface
               * set_interface
               * new_key
               * start_ap
               * new_station
               * new_mpath
               * set_mesh_config
               * set_bss
               * authenticate
               * associate
               * deauthenticate
               * disassociate
               * join_ibss
               * join_mesh
               * remain_on_channel
               * set_tx_bitrate_mask
               * frame
               * frame_wait_cancel
               * set_wiphy_netns
               * set_channel
               * set_wds_peer
               * tdls_mgmt
               * tdls_oper
               * probe_client
               * set_noack_map
               * register_beacons
               * start_p2p_device
               * set_mcast_rate
               * connect
               * disconnect
               * channel_switch
               * Unknown command (104)
      Supported TX frame types:
               * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
               * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
               * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
               * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
               * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
               * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
               * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
               * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
      Supported RX frame types:
               * IBSS: 0x40 0xb0 0xc0 0xd0
               * managed: 0x40 0xd0
               * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
               * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
               * mesh point: 0xb0 0xc0 0xd0
               * P2P-client: 0x40 0xd0
               * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
               * P2P-device: 0x40 0xd0
      software interface modes (can always be added):
               * AP/VLAN
               * monitor
      valid interface combinations:
               * #{ managed, P2P-client } <= 2, #{ AP, mesh point, P2P-GO } <= 2,
                 total <= 2, #channels <= 1
      HT Capability overrides:
               * MCS: ff ff ff ff ff ff ff ff ff ff
               * maximum A-MSDU length
               * supported channel width
               * short GI for 40 MHz
               * max A-MPDU length exponent
               * min MPDU start spacing
      Device supports TX status socket option.
      Device supports HT-IBSS.
      Device supports SAE with AUTHENTICATE command
      Device supports low priority scan.
      Device supports scan flush.
      Device supports AP scan.
      Device supports per-vif TX power setting
      Driver supports full state transitions for AP/GO clients
      Driver supports a userspace MPM

[Snowhog]

What version of Kubuntu are you running?

[Andrew]

What version of Kubuntu are you running?

Kubuntu 16.04

[Andrew]

The wireless network is now visible to other devices which can now successfully connect to it, but no IP addresses are issued. These should be issued by the router on the other end of the ethernet connection, do I have to type the router IP address in somewhere?

[oshunluvr]

You're going to have to post more info if you want more help. Click the link in my sig...

[Andrew]

You're going to have to post more info if you want more help. Click the link in my sig...

I'm not exactly sure what information I can provide. My setup is basically this:

Computer B - Wireless - Computer A - Wired - Router

Computer A has working Internet via the wired connection and Computer B can connected to Computer A's wireless connection, but has no Internet. I configured Computer B's wireless connection as "Wi-Fi (Shared)", which I assumed would share my Internet connection, but this doesn't seem to be the case as an IP address isn't issued. The router should be assigning the IP address. Do I need to setup some sort of bridge between the two connections?

EDIT: Ugh, I switched the IPv4 settings to manual then back to "Shared to other computers" and it seems to be working now!

[oshunluvr]

Glad you figured it out.

Look, I'm not trying to be a jerk or anything, but none of your posts contain any information. You didn't even post what version of Kubuntu you were using until you were asked. No one here is a mind reader and it's very tiresome to have to drag the basic info out of a poster - most of us just won't bother.

In the future, you'll get a lot more responses if you take a few minutes on your first post and lay out what you are using (hardware and software), what you've tried, THEN explaining the issue. For example: "Computer A" is not information about your computer. Brand, Model, age, CPU, GPU, wireless card, etc. - whatever is or may be pertinent to the topic. I think everyone here understands you're using a computer - we're not mind readers nor will any just guess at what you're using. Wireless problems especially would REQUIRE the specific model of the wireless card because driver issues are often the root source of the problem.

Do yourself a favor, give the post linked in my sig a quick read through and consider the info in there for your next attempt at getting help. Just a friendly suggestion - take it or leave it.

Regardless, welcome to the forum.