# Tor / Bluetooth Integration

_Help · started by Quackman on Wed, Nov 18, 2026 11:25 PM_

Tags: Question

---

## Original post

**Quackman** · Wed, Nov 18, 2026 11:25 PM

Hi Everyone,

Hope you are well.

I'm a hobby Reticulum enthusiast with basically no coding knowledge so please excuse my lack of depth in this field.

Could anyone please enlighten me why there is no Tor integration when connecting via TCP to an entry node? As far as i know the principle of Reticulum is to distrust every node, and this would fit in Reticulum's philosophy. Secondly, about bluetooth, even though it has no range, wouldn't it help fill the path of least resistance when used? 

Kindest Regards,

---

## Reply 1

**oatmilk!** · Wed, Nov 18, 2026 11:57 PM

**Quackman** wrote:
> [...]

hi quackman, I'm not quite sure why nomadnet doesn't support tor (but i think it may have been gone over before) but it does support the invisible Internet protocol, and Yggdrasil which both do what you're asking about. 
as far as bte goes, if i remember correctly it actually does! it's just under the default interface along with WiFi 

hope this helps

---

## Reply 2

**Quackman** · Thu, Nov 19, 2026 12:12 AM

Thanks I understood the Yggdrasil and I2P part a bit just curious about the bluetooth part, I'm not sure i see any sort of bitchat like features in any nomadnet or sideband apps built on reticulum nor any laptop to laptop or phone to phone bluetooth mesh chat. Could you expand on this?

---

## Reply 3

**oatmilk!** · Thu, Nov 19, 2026 12:24 AM

**Quackman** wrote:
> [...]

sorry, i don't know what bitchat is, so I won't be able to help you with figuring out parity with it

the default interface on rns allows you to discover other nodes on the same wifi network as you, I'd need to check, but I'm pretty sure it can also include Bluetooth off of that.

---

## Reply 4

**oatmilk!** · Thu, Nov 19, 2026 12:25 AM

(disregard, hit reply instead of edit)

---

## Reply 5

**Zenith** · Thu, Nov 19, 2026 12:56 AM

I have a modified version of the TCPClientInterface that works with hidden services used for my own network here if you want to give it a try:

https://raw.githubusercontent.com/RFnexus/SOCKSClientInterface/refs/heads/main/SOCKSClientInterface.py

It would be sweet if there was something similar included in base RNS, but you can do all of this with Custom Interfaces regardless

If you want to try accessing one of the hidden service transports:
```
  [[RNS Io 2]]
    type = SOCKSClientInterface
    enabled = true
    target_host = q6g6c22kjtna6d2ecfvju5j76nwvqa7d2h5wcbubcots4cwezystthad.onion
    target_port = 4242
    proxy_host = 127.0.0.1
    proxy_port = 9050
```

---

## Reply 6

**CarL_PetErson** · Thu, Nov 19, 2026 1:18 AM

Afaik autointerface doesn't cover Bluetooth/BLE (would be a huge surprise if it did)
But Columba has BLE functionality. Haven't played around much with it, but I was able to connect to a couple of people with it.
Torlando also has released a bluetooth interface so you can install it on your machine:
https://github.com/torlando-tech/ble-reticulum
(huh, didn't realize it was updated last month, nice!)

@Zenith
I was using this one for quite some time: https://codeberg.org/SkyGuy/reti_socks_client/src/branch/main/SOCKSClientInterface.py
Good to know that there is an alternative. Were there any changes in 1.6.1 that would impact such an interface? Just want to know I better hurry up replacing it or if I can take my time :D

---

## Reply 7

**Quackman** · Thu, Nov 19, 2026 1:33 AM

**Zenith** wrote:
> I have a modified version of the TCPClientInterface that works with hidden services used for my own network here if you want to give it a try:
> 
> https://raw.githubusercontent.com/RFnexus/SOCKSClientInterface/refs/heads/main/SOCKSClientInterface.py
> 
> It would be sweet if there was something similar included in base RNS, but you can do all of this with Custom Interfaces regardless
> 
> If you want to try accessing one of the hidden service transports:
> ```
>   [[RNS Io 2]]
>     type = SOCKSClientInterface
>     enabled = true
>     target_host = q6g6c22kjtna6d2ecfvju5j76nwvqa7d2h5wcbubcots4cwezystthad.onion
>     target_port = 4242
>     proxy_host = 127.0.0.1
>     proxy_port = 9050
> ```

works perfectly thanks

---

## Reply 8

**Zenith** · Thu, Nov 19, 2026 3:01 AM

**CarL_PetErson** wrote:
> Good to know that there is an alternative. Were there any changes in 1.6.1 that would impact such an interface? Just want to know I better hurry up replacing it or if I can take my time :D

actually updating to 1.6.1 broke something. I'll need some time to fix it so don't use it quite yet. Thanks for reminding me

---

## Reply 9

**Torlando** · Thu, Nov 19, 2026 6:13 AM

**CarL_PetErson** wrote:
> Afaik autointerface doesn't cover Bluetooth/BLE (would be a huge surprise if it did)
> But Columba has BLE functionality. Haven't played around much with it, but I was able to connect to a couple of people with it.
> Torlando also has released a bluetooth interface so you can install it on your machine:
> https://github.com/torlando-tech/ble-reticulum
> (huh, didn't realize it was updated last month, nice!)

Yup! I've forgotten the details already but one of the recent protocol enforcements Mark put in to RNS exposed a fault in my ble-reticulum interface. That and I was having some issues getting it working well on iOS so there were some minor tweaks for that too. 

Columba actually pulls in the very same python BLEInterface.py from the ble-reticulum repo, and has a driver abstraction layer with different implementations for android, Linux, and iOS. The separation of responsibilities across layers isn't _quite_ as clean as I'd like, but it does at least keep _most_ of the BLE protocol at the shared top layer, BLEInterface.py. There's even a fair bit of extra pieces to make it compatible with BLE 4.0 devices like the original raspberry pi zero W.

---

## Reply 10

**oatmilk!** · Thu, Nov 19, 2026 7:39 AM

**CarL_PetErson** wrote:
> Afaik autointerface doesn't cover Bluetooth/BLE (would be a huge surprise if it did)

huh, yeah you're right. idfk where the hell i got that from, maybe that some rnodes can bind to a phone over it? idfk :( brain not workin good rn, gonna finish up setting up my personal server and then go the hell to bed

---

## Reply 11

**Zenith** · Sat, Nov 21, 2026 1:23 AM

**Quackman** wrote:
> **Zenith** wrote:
> > I have a modified version of the TCPClientInterface that works with hidden services used for my own network here if you want to give it a try:
> > 
> > https://raw.githubusercontent.com/RFnexus/SOCKSClientInterface/refs/heads/main/SOCKSClientInterface.py
> > 
> > It would be sweet if there was something similar included in base RNS, but you can do all of this with Custom Interfaces regardless
> > 
> > If you want to try accessing one of the hidden service transports:
> > ```
> >   [[RNS Io 2]]
> >     type = SOCKSClientInterface
> >     enabled = true
> >     target_host = q6g6c22kjtna6d2ecfvju5j76nwvqa7d2h5wcbubcots4cwezystthad.onion
> >     target_port = 4242
> >     proxy_host = 127.0.0.1
> >     proxy_port = 9050
> > ```
> 
> works perfectly thanks

I've updated the interface, you can find the most recent version here:

https://codeberg.org/rfnxdev/SOCKSClientInterface
https://github.com/RFnexus/SOCKSClientInterface

Let me know if there are any issues

---
