Hi Robert, What kernel and wpa_supplicant configuration changes are required to enable a cellular connection and WiFi on Linux 14.4?
Or, do you have a page describing what is required to set up a cellular connection with/without Connman, and a WiFI connection using connman on the BeagleBone black with 14.4? Have the kernel prompt and all interfaces working to my knowledge but need to validate cellular connectivity and WiFi. thx, Tracy On Fri, Dec 15, 2017 at 12:09 PM, <tlsmith3...@gmail.com> wrote: > I'm trying to setup a WP8548 with ConnMan but I've a strange problem. > ConnMan doesn't want to interact with the wireless adapter. > > Host platform: custom hardware based on the BeagleBone Black. > > Operating system: Linux kernel ver 3.14.29ltsi on mangOh Red adapter and > Linux arm 4.14.0-rc5-bone2 on BeagleBone Black. > > mangOH Red versions: > > Firmware: SWI9X15Y_07.10.04.00 r32393 CARMD-EV-FRMWR1 2016/06/01 20:30:40 > Bootloader: SWI9X15Y_07.10.04.00 r32393 CARMD-EV-FRMWR1 2016/06/01 20:30:40 > > The WP8548 Mango red is running, I can connect to a wifi network using the > WP8548 Mango red so the wifi cellular network is working fine. I can access > the AirVantage with no issues using the SIM card AT&T. Unable to see the > wifi on the BeagleBone Black when the WP8548 Mago red is attached and > connected to cellular wifi. Trying to use ConnMan on the target BeagleBone > Black to connect to the mango red wifi network. > > Below are the results of cm sim info and cm data on the mango read. Can ping > the mangoh.io and connected with no issues. Everything set up correctly. > > root@swi-mdm9x15:~# cm sim info > Type: EXTERNAL_SLOT_1man > ICCID: 89011702272..... > Home Network Operator: AT&T > IMSI: 31017.... > Phone Number: > > > root@swi-mdm9x15:~# cm data > Index: 1 > APN: iot.aer.net > PDP Type: IPV4V6 > Connected: yes > > Below the result of the "./connmanctl technologies" command: > > debian@arm:~$ connmanctl technologies > /net/connman/technology/gadget > Name = Gadget > Type = gadget > Powered = True > Connected = False > Tethering = False > > /net/connman/technology/ethernet > Name = Wired > Type = ethernet > Powered = True > Connected = False > Tethering = False > > These are the 5 steps I understand are needed from previous posts to the TI > community for the 3.14.281.0 Yocto Linux kernel. I have questions on steps > 1, 2 and 5 in bold below. I have also posted to the TI community, but they > typically don't support the Beagle Bone Black community kernel/uboot. > > e2e.ti.com/.../544448 > > Step 1 used /etc/connman/main.conf as follows. > > Anything should be modified in main.conf to show wireless technologies? > > debian@arm:/etc/connman$ cat main.conf > [General] > > # Set input request timeout. Default is 120 seconds > # The request for inputs like passphrase will timeout > # after certain amount of time. Use this setting to > # increase the value in case of different user > # interface designs. > InputRequestTimeout = 120 > > # Set browser launch timeout. Default is 300 seconds > # The request for launching a browser for portal pages > # will timeout after certain amount of time. Use this > # setting to increase the value in case of different > # user interface designs. > BrowserLaunchTimeout = 300 > > # Enable background scanning. Default is true. > # Background scanning will start every 5 minutes unless > # the scan list is empty. In that case, a simple backoff > # mechanism starting from 10s up to 5 minutes will run. > BackgroundScanning = true > > # List of Fallback timeservers separated by ",". > # These timeservers are used for NTP sync when there are > # no timeserver set by the user or by the service. > # These can contain mixed combination of fully qualified > # domain names, IPv4 and IPv6 addresses. > # FallbackTimeservers = > > # List of fallback nameservers separated by "," used if no > # nameservers are otherwise provided by the service. The > # nameserver entries must be in numeric format, host > # names are ignored. > # FallbackNameservers = > > # List of technologies that are marked autoconnectable > # by default, separated by commas ",". The default value > # for this entry when empty is ethernet,wifi,cellular. > # Services that are automatically connected must have been > # set up and saved to storage beforehand. > # DefaultAutoConnectTechnologies = > > # List of preferred technologies from the most preferred > # one to the least preferred one separated by commas ",". > # Services of the listed technology type will be tried one > # by one in the order given, until one of them gets connected > # or they are all tried. A service of a preferred technology > # type in state 'ready' will get the default route when > # compared to another preferred type further down the list > # with state 'ready' or with a non-preferred type; a service > # of a preferred technology type in state 'online' will get > # the default route when compared to either a non-preferred > # type or a preferred type further down in the list. > # PreferredTechnologies = > > # List of blacklisted network interfaces separated by ",". > # Found interfaces will be compared to the list and will > # not be handled by connman, if their first characters > # match any of the list entries. Default value is > # vmnet,vboxnet,virbr,ifb,ve-,vb-. > # NetworkInterfaceBlacklist = vmnet,vboxnet,virbr,ifb,ve-,vb- > > # Allow connman to change the system hostname. This can > # happen for example if we receive DHCP hostname option. > # Default value is true. > # AllowHostnameUpdates = true > > # Keep only a single connected technology at any time. When a new > # service is connected by the user or a better one is found according > # to PreferredTechnologies, the new service is kept connected and all > # the other previously connected services are disconnected. With this > # setting it does not matter whether the previously connected services > # are in 'online' or 'ready' states, the newly connected service is > # the only one that will be kept connected. A service connected by the > # user will be used until going out of network coverage. With this > # setting enabled applications will notice more network breaks than > # normal. Default value is false. > SingleConnectedTechnology = false > > # List of technologies for which tethering is allowed separated by ",". > # The default value is wifi,bluetooth,gadget. Only those technologies > # listed here are used for tethering. If ethernet tethering is desired, > # then ethernet should be added to the list. The technologies listed here > # have to support tethering, currently tethering is implemented for wifi, > # bluetooth, gadget and ethernet. > # NOTE that if ethernet tethering is enabled, then a DHCP server is > # started on all ethernet interfaces. Tethered ethernet should > # never be connected to corporate or home network as it will disrupt > # normal operation of these networks. Due to this ethernet is not > # tethered by default. Do not activate ethernet tethering unless you > # really know what you are doing. > TetheringTechnologies = wifi,bluetooth,gadget > > # Restore earlier tethering status when returning from offline mode, > # re-enabling a technology, and after restarts and reboots. > # Default value is false. > PersistentTetheringMode = false > > # Automatically enable Anycast 6to4 if possible. This is not recommended, as > # the use of 6to4 will generally lead to a severe degradation of connection > # quality. See RFC6343. Default value is false (as recommended by RFC6343 > # section 4.1). > # Enable6to4 = false > > # Enable use of http get as on online status check. > # When a service is in a READY state, and is selected as default, > # ConnMan will issue an HTTP GET request to verify that end-to-end > # connectivity is successful. Only then the service will be > # transitioned to ONLINE state. > # If this setting is false, the default service will remain in READY state. > # Default value is true. > EnableOnlineCheck = true > > # List of technologies with AutoConnect = true which are always connected > # regardless of PreferredTechnologies setting. Default value is empty and > # will connect a technology only if it is at a higher preference than any > # other which is already connected. > # This setting has no effect if SingleConnectedTechnologies is enabled. > # AlwaysConnectedTechnologies = > > Step 2: How do I enable the following and are they needed when building the > wpa_supplicant on this release of Linux 4.14.0? Or, what driver > configuration is required. > > CONFIG_DRIVER_NL80211 > CONFIG_CTRL_IFACE_DBUS_NEW > CONFIG_CTRL_IFACE_DBUS_INTRO > CONFIG_CTRL_IFACE > > > Step 3: Added wpa_supplicant.conf in you fs (/etc/wpa_supplicant.conf) > Example file: > > # WPA configuration > > ctrl_interface=/var/run/wpa_supplicant > update_config=1 > fast_reauth=1 > > Step 4: The wpa_supplicant is run before starting connman by default at boot > tme > example: > /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant > > Step 5: How to I check if rfkill is enabled while building the kernel > (CONFIG_RFKILL=y)? I do not see this in the .config file when building the > kernel. Has this changed or been renamed in 4.14? > > Why do these messages appear when attempting to enable and scan wifi? > > debian@arm:/etc$ connmanctl enable wifi > Error wifi: Method "SetProperty" with signature "sv" on interface > "net.connman.Technology" doesn't exist > > debian@arm:/etc$ connmanctl scan wifi > Error /net/connman/technology/wifi: Method "Scan" with signature "" on > interface "net.connman.Technology" doesn't exist > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBone" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beaglebone/r3TD4CzIYvE/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > beaglebone+unsubscr...@googlegroups.com. > To post to this group, send email to beagleb...@googlegroups.com. > Visit this group at https://groups.google.com/group/beaglebone. > For more options, visit https://groups.google.com/d/optout. -- Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), please immediately notify the sender and delete this e-mail message. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAChUvXMFLaLrRnUWm_XXrkG2gwK5RN1BdF83fhG7OiKE4cKMfg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
