T60 as Pi Ethernet-WiFi-Bridge: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 39: | Line 39: | ||
== Troubleshooting Tips == | == Troubleshooting Tips == | ||
=== <tt>hostapd</tt> not working === | |||
service hostapd stop | |||
hostapd -d /etc/hostapd/hostapd.conf | |||
Read the output thoroughly. There is a clue! | |||
In my case I needed to mark the WiFi-device (<tt>wlx00e04c0f4ac0</tt>) as unmanaged in <tt>/etc/NetworkManager/NetworkManager.conf</tt>: | |||
[keyfile] | |||
unmanaged-devices=interface-name:wlx00e04c0f4ac0;interface-name:wls3 | |||
=== RF-Kill? === | |||
If you get... | |||
SIOCSIFFLAGS: Operation not possible due to RF-kill | |||
...it might mean the RF-Kill-Switch of your Thinkpad is set on. But it can also mean that you just disabled WiFi in <tt>Network Manager</tt>. | |||
---- | ---- | ||
<references/> | <references/> |
Revision as of 15:03, 18 September 2019
I used a Lenovo Thinkpad T60 (Model #2008) to supersede the Pi3.
Setup
The setup is exactly the same as this: Raspberry as Pi Ethernet-WiFi-Bridge, with a few exceptions:
enableBridge.sh
The bridge itself is setup by hostapd. But it is only linked to the WiFi-Interface. So this script is launched after hostapd:
DEVWIFI="wlx00e04c0f4ac0" DEVETH="ens2" DEVBR="br0" # generated by hostapd # 1: give the Bridge an IPA /sbin/ifconfig $DEVBR | grep inet | grep 10.178 > /dev/null 2>&1 if [ "$?" -ne 0 ]; then ifconfig br0 10.178.111.242 netmask 255.255.255.0 route add default gw 10.178.111.1 logger "Added $DEVBR IPA." fi # 2: remove ens2's IPA /sbin/ifconfig $DEVETH | grep inet | grep 10.178 > /dev/null 2>&1 if [ "$?" -eq 0 ]; then ip addr flush dev $DEVETH logger "Flushed $DEVETH IPA." fi # 3: Add Ethernet to bridge /sbin/brctl show $DEVBR | /bin/grep $DEVETH > /dev/null 2>&1 if [ "$?" -ne 0 ]; then # do it echo "Adding ethernet to the bridge..." | logger /sbin/brctl addif $DEVBR $DEVETH /bin/sleep 1 fi
Power Consumption
tbd
Troubleshooting Tips
hostapd not working
service hostapd stop hostapd -d /etc/hostapd/hostapd.conf
Read the output thoroughly. There is a clue!
In my case I needed to mark the WiFi-device (wlx00e04c0f4ac0) as unmanaged in /etc/NetworkManager/NetworkManager.conf:
[keyfile] unmanaged-devices=interface-name:wlx00e04c0f4ac0;interface-name:wls3
RF-Kill?
If you get...
SIOCSIFFLAGS: Operation not possible due to RF-kill
...it might mean the RF-Kill-Switch of your Thinkpad is set on. But it can also mean that you just disabled WiFi in Network Manager.