jeltz/hostap
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
hostap/wpa_supplicant/examples/p2p-action.sh

97 lines
2.6 KiB
Bash
Raw Normal View History

P2P: wpa_cli action calls for P2P group started/removed events
2010-07-18 23:30:26 +02:00
#!/bin/sh
IFNAME=$1
CMD=$2
kill_daemon() {
NAME=$1
PF=$2
if [ ! -r $PF ]; then
return
fi
PID=`cat $PF`
if [ $PID -gt 0 ]; then
if ps $PID | grep -q $NAME; then
kill $PID
fi
fi
rm $PF
}
if [ "$CMD" = "P2P-GROUP-STARTED" ]; then
GIFNAME=$3
if [ "$4" = "GO" ]; then
kill_daemon dhclient /var/run/dhclient-$GIFNAME.pid
rm /var/run/dhclient.leases-$GIFNAME
kill_daemon dnsmasq /var/run/dnsmasq.pid-$GIFNAME
ifconfig $GIFNAME 192.168.42.1 up
P2P: Use alternative way of starting dnsmasq if needed Some other dnsmasq users (like libvirt) seem to be binding the DHCP server to all interfaces which prevents the previously used mechanism here from working (bind on the DHCP socket fails). If a failure is noticed, try to start dnsmasq with -z option to avoid that.
2010-11-26 14:47:13 +01:00
if ! dnsmasq -x /var/run/dnsmasq.pid-$GIFNAME \
P2P: wpa_cli action calls for P2P group started/removed events
2010-07-18 23:30:26 +02:00
-i $GIFNAME \
P2P: Use alternative way of starting dnsmasq if needed Some other dnsmasq users (like libvirt) seem to be binding the DHCP server to all interfaces which prevents the previously used mechanism here from working (bind on the DHCP socket fails). If a failure is noticed, try to start dnsmasq with -z option to avoid that.
2010-11-26 14:47:13 +01:00
-F192.168.42.11,192.168.42.99; then
# another dnsmasq instance may be running and blocking us; try to
# start with -z to avoid that
dnsmasq -x /var/run/dnsmasq.pid-$GIFNAME \
-i $GIFNAME \
P2P: Disable DNS server from dnsmasq This avoids issues with multiple instances of dnsmasq running, e.g., with one on eth0 and the other one for the P2P group. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
2013-12-04 04:42:14 +01:00
-F192.168.42.11,192.168.42.99 --listen-address 192.168.42.1 -z -p 0
P2P: Use alternative way of starting dnsmasq if needed Some other dnsmasq users (like libvirt) seem to be binding the DHCP server to all interfaces which prevents the previously used mechanism here from working (bind on the DHCP socket fails). If a failure is noticed, try to start dnsmasq with -z option to avoid that.
2010-11-26 14:47:13 +01:00
fi
P2P: wpa_cli action calls for P2P group started/removed events
2010-07-18 23:30:26 +02:00
fi
if [ "$4" = "client" ]; then
kill_daemon dhclient /var/run/dhclient-$GIFNAME.pid
rm /var/run/dhclient.leases-$GIFNAME
kill_daemon dnsmasq /var/run/dnsmasq.pid-$GIFNAME
P2P: Add support for IP address assignment in 4-way handshake This new mechanism allows P2P Client to request an IPv4 address from the GO as part of the 4-way handshake to avoid use of DHCP exchange after 4-way handshake. If the new mechanism is used, the assigned IP address is shown in the P2P-GROUP-STARTED event on the client side with following new parameters: ip_addr, ip_mask, go_ip_addr. The assigned IP address is included in the AP-STA-CONNECTED event on the GO side as a new ip_addr parameter. The IP address is valid for the duration of the association. The IP address pool for this new mechanism is configured as global wpa_supplicant configuration file parameters ip_addr_go, ip_addr_mask, ip_addr_star, ip_addr_end. For example: ip_addr_go=192.168.42.1 ip_addr_mask=255.255.255.0 ip_addr_start=192.168.42.2 ip_addr_end=192.168.42.100 DHCP mechanism is expected to be enabled at the same time to support P2P Devices that do not use the new mechanism. The easiest way of managing the IP addresses is by splitting the IP address range into two parts and assign a separate range for wpa_supplicant and DHCP server. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
2013-03-16 18:13:31 +01:00
ipaddr=`echo "$*" | sed 's/.* ip_addr=\([^ ]*\).*/\1/'`
ipmask=`echo "$*" | sed 's/.* ip_mask=\([^ ]*\).*/\1/'`
goipaddr=`echo "$*" | sed 's/.* go_ip_addr=\([^ ]*\).*/\1/'`
if echo "$ipaddr$ipmask$goipaddr" | grep -q ' '; then
ipaddr=""
ipmask=""
goipaddr=""
fi
if [ -n "$ipaddr" ]; then
sudo ifconfig $GIFNAME "$ipaddr" netmask "$ipmask"
sudo ip ro re default via "$goipaddr"
exit 0
fi
P2P: wpa_cli action calls for P2P group started/removed events
2010-07-18 23:30:26 +02:00
dhclient -pf /var/run/dhclient-$GIFNAME.pid \
-lf /var/run/dhclient.leases-$GIFNAME \
-nw \
$GIFNAME
fi
fi
if [ "$CMD" = "P2P-GROUP-REMOVED" ]; then
GIFNAME=$3
if [ "$4" = "GO" ]; then
kill_daemon dnsmasq /var/run/dnsmasq.pid-$GIFNAME
ifconfig $GIFNAME 0.0.0.0
fi
if [ "$4" = "client" ]; then
kill_daemon dhclient /var/run/dhclient-$GIFNAME.pid
rm /var/run/dhclient.leases-$GIFNAME
ifconfig $GIFNAME 0.0.0.0
fi
fi
P2P: Add support for cross connection If enabled, cross connection allows GO to forward IPv4 packets using masquerading NAT from the P2P clients in the group to an uplink WLAN connection. This is disabled by default and can be enabled with "wpa_cli p2p_set cross_connect 1" on the P2P device interface.
2010-07-10 19:19:34 +02:00
if [ "$CMD" = "P2P-CROSS-CONNECT-ENABLE" ]; then
GIFNAME=$3
UPLINK=$4
# enable NAT/masquarade $GIFNAME -> $UPLINK
iptables -P FORWARD DROP
iptables -t nat -A POSTROUTING -o $UPLINK -j MASQUERADE
iptables -A FORWARD -i $UPLINK -o $GIFNAME -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables -A FORWARD -i $GIFNAME -o $UPLINK -j ACCEPT
sysctl net.ipv4.ip_forward=1
fi
if [ "$CMD" = "P2P-CROSS-CONNECT-DISABLE" ]; then
GIFNAME=$3
UPLINK=$4
# disable NAT/masquarade $GIFNAME -> $UPLINK
sysctl net.ipv4.ip_forward=0
iptables -t nat -D POSTROUTING -o $UPLINK -j MASQUERADE
iptables -D FORWARD -i $UPLINK -o $GIFNAME -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables -D FORWARD -i $GIFNAME -o $UPLINK -j ACCEPT
fi
Reference in a new issue Copy permalink