Re: pointers to material for using netbook's wireless as access point
A little more detail, with the following pair of configurations, I get
on the boot console,
Configuring network interfaces...can't add wlan0 to bridge br0:
Operation not supported
SIOCSIFFLAGS: Cannot assign requested address
SIOCSIFFLAGS: Cannot assign requested address
Waiting for br0 to get ready (MAXWAIT is 32 seconds).
And another couple of messages I didn't get pictures of, including one
apparently from the driver, about the file already existing, and
another
probably from the kernel about not being able to set up the bridge. I think
it was the following, but I couldn't get a picture of it:
RTNETLINK answers: File exists
Failed to bring up [was it eth0 or br0?].
(And, yet, the bridge was set up and functional, even to routing the
DHCP handshake. It was only the netbook's inability to access the
internet through its own ethernet port that left me needing a better
solution.)
Those messages, by the way, were not recorded in any file under
/var/log. The only way to capture them was by taking a picture.
On Thu, Jun 8, 2017 at 9:29 AM, Joel Rees <joel.rees@gmail.com> wrote:
> [...]
>
> ---------------------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-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
> -------------------------------------------------------------
>[...]
--
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: