Blueman GUI Bluetooth Network Access Point - fixing Bridging
#5
Soooooo.... big development that uses a different solution to the problem than all of my previous work

It is supposed to be working, blueman is now giving the option of a network access point, I can associate with it as a client from my laptop, but the bridge seems to not be working.
sudo apt install blueman on the pinephone
open blueman(it is in the non-mobile friendly apps)
view -> plugins -> (plugins window opens) check - NMPANSupport (this should give you the required pand and DHCP support)
next again in blueman
view -> Local Services
The Local Services window pops up
check - Network Access Point(NAP)

The Blueman UI is mostly usable with auto-resizing on, My only issue is I couldn't see all of the profiles when paired on the pinephone screen.  It works and plays well so far with the Phosh bluetooth and settings UI.

Again this is nearly done with no hand coding or added scripts required but while I have usable internet from my mobile provider on the PP and I have a network connection from my client laptop to the host PP the network bridge is not routing my traffic.  I will remove my old N900 era scripts hoping that fixes everything(done).  I still wonder if I have broken something playing with .conf settings and scripts and failing to write it in notes during late night hacking sessions.
this is 'route' on my laptopSadI have xxx'ed out mac addresses)
Code:
Kernel IP routing table
Destination    Gateway        Genmask        Flags Metric Ref    Use Iface
10.108.82.0    0.0.0.0        255.255.255.0  U    0      0        0 pan1
link-local      0.0.0.0        255.255.0.0    U    1000  0        0 pan1
ifconfig:
Code:
bnep0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::2e0:4cff:fe23:9987  prefixlen 64  scopeid 0x20<link>
        ether xx:xx:xx:xx:xx:xx  txqueuelen 1000  (Ethernet)
        RX packets 275  bytes 52277 (51.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 236  bytes 134144 (131.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 33  bytes 3167 (3.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 33  bytes 3167 (3.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

pan1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.36.225.1  netmask 255.255.255.0  broadcast 0.0.0.0
        inet6 fe80::e8ad:18ff:fe73:2bbe  prefixlen 64  scopeid 0x20<link>
        ether xx:xx:xx:xx:xx:xx txqueuelen 1000  (Ethernet)
        RX packets 275  bytes 49307 (48.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 246  bytes 135977 (132.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

here is some dmesg -w outputs form the kernel when I connect via BT
Code:
[   30.032557] 8723cs: module is from the staging directory, the quality is unknown, you have been warned.
[   30.359071] Bluetooth: Core ver 2.22
[   30.369860] NET: Registered PF_BLUETOOTH protocol family
[   30.375346] Bluetooth: HCI device and connection manager initialized
[   30.382233] Bluetooth: HCI socket layer initialized
[   30.387417] Bluetooth: L2CAP socket layer initialized
[   30.392660] Bluetooth: SCO socket layer initialized
[   30.440357] EXT4-fs (mmcblk2p1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
[   30.449185] i2c i2c-1: Added multiplexed i2c bus 5
[   30.767332] Bluetooth: HCI UART driver ver 2.3
[   30.771855] Bluetooth: HCI UART protocol H4 registered
[   30.813890] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   30.860338] Bluetooth: HCI UART protocol Broadcom registered
[   31.496152] Bluetooth: hci0: RTL: examining hci_ver=07 hci_rev=000b lmp_ver=07 lmp_subver=8703
[   31.509797] Bluetooth: hci0: RTL: chip_type status=0 type=5
[   31.519243] Bluetooth: hci0: RTL: rom_version status=0 version=1
[   31.525404] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723cs_xx_fw.bin
[   31.552417] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723cs_xx_config.bin
[   31.621383] Bluetooth: hci0: RTL: cfg_sz 63, total sz 19427
[   32.005285] Bluetooth: hci0: RTL: fw version 0xaa5ca4dc
[   32.065267] using random self ethernet address
[   32.069807] using random host ethernet address
[   32.169236] usb0: HOST MAC xx:xx:xx:xx:xx:xx
[   32.173633] usb0: MAC xx:xx:xx:xx:xx:xx
[   34.159548] zram: Added device: zram0
[   34.272174] ov5640 3-004c: firmware upload success
[   34.287234] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   34.292655] Bluetooth: BNEP filters: protocol multicast
[   34.298044] Bluetooth: BNEP socket layer initialized
[   34.328447] zram0: detected capacity change from 0 to 3067112
[   34.390779] NET: Registered PF_ALG protocol family
[   34.457459] sun8i-ce 1c15000.crypto: Fallback for ecb-aes-sun8i-ce is ecb-aes-ce
[   34.577228] ov5640 3-004c: uploaded firmware didn't start, got to 0x7f, retrying...
[   34.592765] Adding 1533552k swap on /dev/zram0.  Priority:100 extents:1 across:1533552k SSFS
[   34.905227] ov5640 3-004c: uploaded firmware didn't start, got to 0x7f
[   34.912209] ov5640 3-004c: ov5640_set_ctrl_focus: no autofocus firmware loaded
[   38.761267] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   39.905175] ps: disabling
[   39.908634] dc1sw: disabling
[   39.916931] vcc-1v2-hsic: disabling
[   39.924208] usb0-vbus: disabling
[   42.886303] hdmi-audio-codec hdmi-audio-codec.5.auto: Only one simultaneous stream supported!
[   42.894984] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22
[   42.905306]  1c22800.i2s-i2s-hifi: soc_pcm_open() failed (-22)
[   47.119843] ov5640 3-004c: firmware upload success
[   47.451638] ov5640 3-004c: uploaded firmware didn't start, got to 0x7f, retrying...
[   47.783296] usb 2-1: new high-speed USB device number 2 using ehci-platform
[   47.790492] ov5640 3-004c: uploaded firmware didn't start, got to 0x7f
[   47.797132] ov5640 3-004c: ov5640_set_ctrl_focus: no autofocus firmware loaded
[   47.970983] usb 2-1: New USB device found, idVendor=2c7c, idProduct=0125, bcdDevice= 3.18
[   47.979451] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   47.986802] usb 2-1: Product: EG25-G
[   47.990522] usb 2-1: Manufacturer: Quectel
[   48.108784] usbcore: registered new interface driver usbserial_generic
[   48.120274] usbserial: USB Serial support registered for generic
[   48.143209] usbcore: registered new interface driver cdc_wdm
[   48.197788] qmi_wwan 2-1:1.4: cdc-wdm0: USB WDM device
[   48.205395] usbcore: registered new interface driver option
[   48.222738] qmi_wwan 2-1:1.4 wwan0: register 'qmi_wwan' at usb-1c1b000.usb-1, WWAN/QMI device, 16:f9:92:73:6b:9a
[   48.232613] usbserial: USB Serial support registered for GSM modem (1-port)
[   48.240828] usbcore: registered new interface driver qmi_wwan
[   48.244015] option 2-1:1.0: GSM modem (1-port) converter detected
[   48.253938] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
[   48.261341] option 2-1:1.1: GSM modem (1-port) converter detected
[   48.268230] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1
[   48.276367] option 2-1:1.2: GSM modem (1-port) converter detected
[   48.283201] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2
[   48.290617] option 2-1:1.3: GSM modem (1-port) converter detected
[   48.297402] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB3
[   48.478802] Bluetooth: RFCOMM TTY layer initialized
[   48.483784] Bluetooth: RFCOMM socket layer initialized
[   48.496758] Bluetooth: RFCOMM ver 1.11
[   54.776907] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[   55.501462] rfkill: input handler disabled
[   67.853926] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[   71.505899] ov5640 3-004c: firmware upload success
[   71.810970] ov5640 3-004c: uploaded firmware didn't start, got to 0x7f, retrying...
[   72.127017] ov5640 3-004c: uploaded firmware didn't start, got to 0x7f
[   72.133739] ov5640 3-004c: ov5640_set_ctrl_focus: no autofocus firmware loaded
[   74.861122] ov5640 3-004c: firmware upload success
[   75.162870] ov5640 3-004c: uploaded firmware didn't start, got to 0x7f, retrying...
[   75.474871] ov5640 3-004c: uploaded firmware didn't start, got to 0x7f
[   75.481492] ov5640 3-004c: ov5640_set_ctrl_focus: no autofocus firmware loaded
[   77.780273] pan1: port 1(bnep0) entered blocking state
[   77.785514] pan1: port 1(bnep0) entered disabled state
[   77.792685] device bnep0 entered promiscuous mode
[   77.811632] pan1: port 1(bnep0) entered blocking state
[   77.816862] pan1: port 1(bnep0) entered forwarding state
[   77.822602] IPv6: ADDRCONF(NETDEV_CHANGE): pan1: link becomes ready
[   78.277707] ov5640 3-004c: firmware upload success
[   78.582950] ov5640 3-004c: uploaded firmware didn't start, got to 0x7f, retrying...
[   78.900086] ov5640 3-004c: uploaded firmware didn't start, got to 0x7f
[   78.907332] ov5640 3-004c: ov5640_set_ctrl_focus: no autofocus firmware loaded
[  243.339224] pan1: port 1(bnep0) entered disabled state
[  243.347421] device bnep0 left promiscuous mode
[  243.353867] pan1: port 1(bnep0) entered disabled state
[  459.455661] pan1: port 1(bnep0) entered blocking state
[  459.461610] pan1: port 1(bnep0) entered disabled state
[  459.468600] device bnep0 entered promiscuous mode
[  459.479536] pan1: port 1(bnep0) entered blocking state
[  459.484801] pan1: port 1(bnep0) entered forwarding state

most interesting is the (bnep0) entered blocking state, (bnep0) entered disabled state, and failed firmware loads.

It has been years since I have played with routing and dnsmasq but I assume that bluez and blueman should have the whole routing implemented so I would like to hear form others before I start breaking my system again.
  Reply


Messages In This Thread
RE: Blueman GUI Bluetooth Network Access Point - fixing Bridging - by biketool - 04-15-2022, 03:48 AM

Possibly Related Threads…
Thread Author Replies Views Last Post
  Mobile internet via cellular network mostly not working Anna 18 12,948 01-19-2024, 02:59 AM
Last Post: anonymous
  Not connecting to cellular network car46999 18 9,928 01-30-2023, 12:06 AM
Last Post: car46999
  Bluetooth audio revisited 3x5co 1 1,373 01-10-2023, 05:51 PM
Last Post: Zebulon Walton
  need help with downgradin network-manager Ferriah 0 823 11-07-2022, 04:51 PM
Last Post: Ferriah
  Exclamation point in cellular icon after update Zebulon Walton 8 5,807 06-22-2022, 05:57 PM
Last Post: albafrati
  Any fix for bluetooth crash when entering pairing password? kk22 0 1,039 06-18-2022, 07:51 PM
Last Post: kk22
  Scripting Bluetooth Hotspot for Mobian biketool 1 1,795 03-20-2022, 03:03 PM
Last Post: biketool
  Bluetooth audio support? Zebulon Walton 5 4,362 02-28-2022, 08:59 AM
Last Post: Zebulon Walton
  Mobile network mode setting not saved Zebulon Walton 3 3,563 12-05-2021, 12:12 AM
Last Post: bcnaz
  no access to webdav files (for some apps) jsch 0 1,465 11-13-2021, 09:46 AM
Last Post: jsch

Forum Jump:


Users browsing this thread: 1 Guest(s)