+- OpenMarine (https://forum.openmarine.net)
+-- Forum: OpenPlotter (https://forum.openmarine.net/forumdisplay.php?fid=1)
+--- Forum: Bug Reports (https://forum.openmarine.net/forumdisplay.php?fid=4)
+--- Thread: AP Issues (/showthread.php?tid=139)
AP Issues - robbiedeloose - 2016-06-14
Hi all,
I'm experiencing a new problem with the AP.
OP 0.8, Rasp 3, no openGL, internal wifi and dongle. The dongle does not support AP Mode.
I configure the internal wifi WLAN0 as an AP and share the internet connection of WLAN1. All works fine and continous to work fine, no craches.
From time to time if I power on the raspberry i don't get my AP. If i connect the rasp to hdmi display and check AP setting i see that the devices have change place.
If I change AP to WLAN1 and share internet from WLAN0 it works again. It seems that the wifi numbering is not consistent.
Possibly rather a raspberry bug than a OP bug.
Does anybody else gets this kind of behaviour? Is there a way to stop them from changing numbers?
extra info
Code:
pi@openplotter:~ $ ifconfig
eth0 Link encap:Ethernet HWaddr b8:27:eb:05:c3:b0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:6745 errors:0 dropped:0 overruns:0 frame:0
TX packets:6745 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:410823 (401.1 KiB) TX bytes:410823 (401.1 KiB)
wlan0 Link encap:Ethernet HWaddr 00:e0:4d:05:52:cf
inet addr:192.168.10.135 Bcast:192.168.10.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4219 errors:0 dropped:3 overruns:0 frame:0
TX packets:3238 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1925335 (1.8 MiB) TX bytes:602042 (587.9 KiB)
wlan1 Link encap:Ethernet HWaddr b8:27:eb:50:96:e5
inet addr:10.10.10.1 Bcast:10.10.10.255 Mask:255.255.255.0
inet6 addr: fe80::1157:2b52:3687:395f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5883 errors:0 dropped:1264 overruns:0 frame:0
TX packets:4802 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:840903 (821.1 KiB) TX bytes:2810988 (2.6 MiB)
pi@openplotter:~ $ lsusb
Bus 001 Device 007: ID 0403:fd49 Future Technology Devices International, Ltd ShipModul MiniPlex-4xUSB-AIS NMEA Multiplexer
Bus 001 Device 006: ID 148f:7601 Ralink Technology, Corp.
Bus 001 Device 005: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 001 Device 004: ID 046d:c52e Logitech, Inc.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubKind regards,
Robbie
RE: AP Issues - SkipperEarly - 2016-06-21
Let my try to jump in as I experienced the same difficulty.
Thats what I did and now its stable:
Make sure the wlan0 settings for the AP are set in the /boot/config.txt file, including the share=wlan1 parameter
Configure in menu/preferences/network connections the wlan1 for the i/net gateway (make sure you use the correct wlan mac address for wlan1)
when you now reboot the wlan0 should be the AP and wlan1 the i/n share.
Hope this helps!