[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: pointers to material for using netbook's wireless as access point

On Wed, Jun 7, 2017 at 2:08 PM, Joel Rees <joel.rees@gmail.com> wrote:
> On Tue, Jun 6, 2017 at 4:10 PM, didier gaumet <didier.gaumet@gmail.com> wrote:
>> Le 06/06/2017 à 03:58, Joel Rees a écrit :
>> [...]
>> can anyone point me to a good how-to?
>> [...]
>>
>> these should do the trick:
>> https://agentoss.wordpress.com/2011/10/31/creating-a-wireless-access-point-with-debian-linux/
>> https://wiki.archlinux.org/index.php/Software_access_point
>> http://oob.freeshell.org/nzwireless/LWAP-HOWTO.html
>>
>
> I'd thought I was recognized the URLs as some I had looked at before,
("had recognized" or maybe "was recognizing", erk)
> but I check now and see lots of useful information. Thanks.
>
> I'll probably have more questions when I've had a chance to work through
> them.

Okay, I have partial success. My kids can connect via wireless, but I can't
connect on the netbook in question, at all.

First thing I did was install rfkill and use it to undo whatever had the thing
believing I'd shut the wireless down by hand or something:

---------------------------
$sudo rfkill list all
0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no
1: ideapad_wlan: Wireless LAN
    Soft blocked: yes
    Hard blocked: yes

$sudo rfkill unblock wifi

$sudo rfkill unblock all

$sudo rfkill list all
0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
1: ideapad_wlan: Wireless LAN
    Soft blocked: no
    Hard blocked: no
---------------------------

My /etc/hostapd/hostapd.conf is below, along with one of the
/etc/network/interfaces files I've tried. This combination allows my children
to access the internet from my netbook's wifi, through my netbook's ethernet,
to the provider's modem. I cannot access the internet on the same
netbook. (It only has one ethernet port.

DHCP from the modem is routed through the
wireless to the children's

Should I just remove networkmanager from the system, or should I try
to solve this by the NAT approach (which I still am working through).

-- 
Joel Rees

One of these days I'll get someone to pay me
to design a language that combines the best of Forth and C.
Then I'll be able to leap wide instruction sets with a single #ifdef,
run faster than a speeding infinite loop with a #define,
and stop all integer size bugs with a bare cast.

More of my delusions:
http://reiisi.blogspot.com/2017/05/do-not-pay-modern-danegeld-ransomware.html
http://reiisi.blogspot.jp/p/novels-i-am-writing.html





clients:

---------------------hostapd.conf----------------
### Wireless network name ###
interface=wlan0

### Driver Name ###
driver=nl80211

### Set your bridge name ###
bridge=br0

### Country name code in ISO/IEC 3166-1 format. ###
# This is used to set regulatory domain.
# Set as needed to indicate country in which device is operating.
# This can limit available channels and transmit power.
### (IN == INDIA, UK == United Kingdom, US == United Stats and so on ) ###
country_code=JP

### SSID: ###
ssid=StuporInducingNetwork

### channel number (some drivers will only accept 0) ###
channel=1

### operation mode (a = IEEE 802.11a, b = IEEE 802.11b, g = IEEE 802.11g) ###
hw_mode=g
ieee80211n=1
ht_capab=[HT40+][SHORT-GI-40][DSSS_CCK-40]

### WPA mode: ###
wpa=2

### passphrase (WiFi password): ###
wpa_passphrase=something!wouldn0t$#0wHER3

## Key management algorithms ##
wpa_key_mgmt=WPA-PSK

## Set cipher suites (encryption algorithms) ##
## TKIP = Temporal Key Integrity Protocol
## CCMP = AES in Counter mode with CBC-MAC
wpa_pairwise=TKIP
rsn_pairwise=CCMP
## Shared Key Authentication ##
auth_algs=1
## Accept all MAC address ###
macaddr_acl=0

-------------------------------------------------------

-------------------interfaces-v1------------------------
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo br0
#auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
#iface eth0 inet dhcp
# iface eth0 inet static
iface eth0:0 inet manual

iface eth0:1 inet static
     address 172.19.138.147
    netmask 255.255.255.128
    gateway 172.19.138.179
    broadcast 172.19.138.191
#
dns-nameservers 172.19.138.179 208.67.222.222 8.8.4.4



wireless wlan0
allow-hotplug wlan0
#iface wlan0 inet static
iface wlan0 inet manual

# Setup bridge
iface br0 inet manual
    bridge_ports wlan0 eth0:0
    address 172.19.138.177
    netmask 255.255.255.192
    network 172.19.138.160
    broadcast 172.19.138.191
## isp router 172.19.138.179 also runs DHCPD ##
    gateway 172.19.138.179
    dns-nameservers 172.19.138.179 208.67.222.222 8.8.4.4
-------------------------------------------------------------

This next interfaces file tries to make the default route explicit, but gives
similar results:

-------------------interfaces-v2------------------------
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo br0
#auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
#iface eth0 inet dhcp
# iface eth0 inet static

iface eth0 inet static
     address 172.19.138.147
    netmask 255.255.255.192
    gateway 172.19.138.179
    up route add -net default gw 172.19.138.179
    down route del -net default gw 172.19.138.179
    broadcast 172.19.138.191
iface eth0:1 inet manual
#
dns-nameservers 172.19.138.179 208.67.222.222 8.8.4.4

wireless wlan0
allow-hotplug wlan0
#iface wlan0 inet static
iface wlan0 inet manual

# Setup bridge
iface br0 inet manual
    bridge_ports wlan0 eth0:1
    address 172.19.138.177
    netmask 255.255.255.192
    network 172.19.138.160
    broadcast 172.19.138.191
## isp router 172.19.138.179 also runs DHCPD ##
    gateway 172.19.138.179
    dns-nameservers 172.19.138.179 208.67.222.222 8.8.4.4
-------------------------------------------------------------

Simply commenting out the bridge allows my netbook to access the
interent:

-------------------interfaces-holdoff-----------------
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo br0
#auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
#iface eth0 inet dhcp
# iface eth0 inet static

iface eth0 inet static
     address 172.19.138.147
    netmask 255.255.255.192
    gateway 172.19.138.179
    up route add -net default gw 172.19.138.179
    down route del -net default gw 172.19.138.179
    broadcast 172.19.138.191
#iface eth0:1 inet manual
#
dns-nameservers 172.19.138.179 208.67.222.222 8.8.4.4


wireless wlan0
#allow-hotplug wlan0
#iface wlan0 inet static
iface wlan0 inet manual

# Setup bridge
#iface br0 inet manual
#    bridge_ports wlan0 eth0:1
#    address 172.19.138.177
#    netmask 255.255.255.192
#    network 172.19.138.160
#    broadcast 172.19.138.191
## isp router 172.19.138.179 also runs DHCPD ##
#    gateway 172.19.138.179
#    dns-nameservers 172.19.138.179 208.67.222.222 8.8.4.4
------------------------------------------------------------

Should I just remove networkmanager from the system, or should I try
to solve this by the NAT approach (which I still am working through
the reading on). Ultimately, I want to NAT the wireless anyway.

-- 
Joel Rees

One of these days I'll get someone to pay me
to design a language that combines the best of Forth and C.
Then I'll be able to leap wide instruction sets with a single #ifdef,
run faster than a speeding infinite loop with a #define,
and stop all integer size bugs with a bare cast.

More of my delusions:
http://reiisi.blogspot.com/2017/05/do-not-pay-modern-danegeld-ransomware.html
http://reiisi.blogspot.jp/p/novels-i-am-writing.html
Reply to: