I found out when looking at ifconfig when I saw the uap8 entry with the IP and I stumbled over some Internet stuff saying Dreamplug comes with AccessPoint-configuration.
To deactivate you have to edit /root/init_setup.sh
root@ubuntu:~# vi /root/init_setup.sh
I excluded all lines from modprobe uab8xxx towards /etc/init.d/bluetooth start. This shellscript is called whilst startup and initializes the Access Point. If excluded, the initialization isn't done and therefore no IP conflict will happen again.
Altered init_setup.sh:
#!/bin/sh
# This is called from /etc/rc.local to perform the initial setup.
# We always bootup in AP mode. Delete any stale files
rm -f /etc/wlanclient.mode
SSID=DreamPlug-uAP-`ifconfig uap0 | awk -F ":" '/HWaddr/ {print $6$7}'`
#modprobe uap8xxx
#ifconfig uap0 192.168.1.1 up
#/usr/bin/uaputl sys_cfg_ssid $SSID
#/usr/bin/uaputl bss_start
#iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
#iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE
#echo 1 > /proc/sys/net/ipv4/ip_forward
#/etc/init.d/udhcpd start
#/etc/init.d/dnsmasq start
#iptables -A INPUT -i uap0 -p tcp -m tcp --dport 80 -j ACCEPT
# Re-enable bluetooth. In the earlier case, it didn't find the firmware.
# rmmod libertas_sdio libertas btmrvl_sdio btmrvl bluetooth 2>/dev/null
rmmod btmrvl_sdio btmrvl
#/etc/init.d/bluetooth start
modprobe btmrvl_sdio
hciconfig hci0 up
hciconfig hci0 piscan
blinkled >> /dev/null
# Set leds
echo 1 > `eval ls /sys/class/leds/guruplug\:green\:wmode/brightness`
echo 0 > `eval ls /sys/class/leds/guruplug\:red\:wmode/brightness`
Now just save the file and and restart the dreamplug. The accesspoint shouldn't be setup any more.
Keine Kommentare:
Kommentar veröffentlichen