agentzulu

Ok I did some more testing and it turns out that wpa_supplicant is interfering with hostapd, so I don't have to specifically worry about network manager anymore. All i did to fix the issue was define the cards in wpa_supplicant and then it worked as planned. As for Network Manager, putting iptables over the instinctive routing path didn't change anything as I'd expected, I talked to someone that said making hard routes with the "route" command would be a better Idea and more likely to work but I've never really done that. Overall, wpa_supplicant seems to mess around with the wireless interface AP mode and encourage anyone else with a similar problem to either disable it or write in the arguments that you need.

Alright, I will see if routing the traffic to and from my other adapter will work on its own trough iptables. I wasn't sure if there was an open file in NM that had the routing rules before I just tried to do it through iptables manually. I kind of assumed it was done internally but wanted to check. I will let you know if it works.

Another quick one... What causes network manager to instinctively port traffic from a wireless interface to the ethernet interface in an access point setting? I will read up on the documentation but essentially I am thinking of setting up an access point that ports traffic to another wireless network interface.

Hello, I have just been following the instructions set up here to make an access point out of my orange pi one which has the 4.9.4-sun8i dev kernels (they are not the problem). https://learn.adafruit.com/setting-up-a-raspberry-pi-as-a-wifi-access-point/install-software When I begin the first test I get an error that is spit out by the interface I guess? (I'm relatively new to linux and am trying to get a hang of it) Configuration file: /etc/hostapd/hostapd.conf nl80211: Could not configure driver mode nl80211: deinit ifname=wlx40a5ef0eea56 disabled_11b_rates=0 nl80211 driver initialization failed. wlx40a5ef0eea56: interface state UNINITIALIZED->DISABLED wlx40a5ef0eea56: AP-DISABLED hostapd_free_hapd_data: Interface wlx40a5ef0eea56 wasn't started My hostapd.conf file is also as follows, although it looks OK to me. ssid=PI_AP interface=wlx40a5ef0eea56 hw_mode=g channel=5 driver=nl80211 logger_syslog=0 logger_syslog_level=0 wmm_enabled=1 ieee80211n=1 wpa=3 preamble=1 #wpa_psk=66eb31d2b48d19ba216f2e50c6831ee11be98e2fa3a8075e30b866f4a5ccda27 wpa_passphrase=12345678 wpa_key_mgmt=WPA-PSK wpa_pairwise=TKIP rsn_pairwise=CCMP auth_algs=1 macaddr_acl=0 noscan=1 #ht_capab=[HT40-][SHORT-GI-40][SHORT-GI-40][DSSS_CCK-40] country_code=US #ieee80211d=1 root@orangepion

Hello, Recently I bought my first orange pi one and I downloaded the xenial desktop specifically so that I could have an xserver preinstalled to what I wanted to transform into an access point. I had realized that all realtek wifi dongles would cause a kernel crash once you try to connect to an access point with them. I had followed instructions to rebuild the orange pi with the dev packages that are found on its download page, and it worked the first time, allowing me to continue with my work. Long story short I ended up re-imaging the sd card and now I can't get the dev version to work again. It won't boot once I install the packages. I am wondering if something has changed or that is just a problem for me. Also I attempted to get the mainline packages however there is no mainline u-boot package for the OrangePi One like it says here https://www.armbian.com/kernel/. It would be appreciated if I could know how to install the mainline packages if there are any / a way to get the dev packages to work again. OR if neither of those is an option It would be helpful if I could get some more help with using the legacy build with the realtek dongles I have.