meshtastic --tunnel -> Read TUN in a Thread failure #104

KiwiHC16 · 2021-09-04T10:12:07Z

Hi,

I'm trying to setip the tunnel for test purposes. I got an error about ifconfig.

I did the test on a VM Debian 10 and on a VM Ubuntu.

Followed the steps from pages:

After a french install of ubuntu here are the command I used as root:

$apt install python3-pip
$pip3 install --upgrade pytap2
$pip3 install --upgrade meshtastic

$ls -l /dev/ttyUSB*
crw-rw---- 1 root dialout 188, 0 Sep  4 03:00 /dev/ttyUSB0

$meshtastic -h
(I get in return all help text)

$meshtastic --tunnel
Connected to radio
INFO:root:Starting IP to mesh tunnel (you must be root for this *pre-alpha* feature to work).  Mesh members:
INFO:root:Node !f244c500 has IP address 10.115.197.0
INFO:root:Node !f244c480 has IP address 10.115.196.128
sh: 1: ifconfig: not found
Aborting due to:

After putting in debug I can identify the issue at line https://github.com/meshtastic/Meshtastic-python/blob/8380e57fa060b4cd5a46cfce7ec4fcc99019c3ed/meshtastic/tunnel.py#L102

If I do a small test.py

File

from pytap2 import TapDevice
tun = TapDevice(name="mesh")
tun.up()
tun.ifconfig(address="192.168.4.2", netmask="255.255.255.0", mtu=200)

Test

root@abeilleDev:~# python3 test.py 
sh: 1: ifconfig: not found
Traceback (most recent call last):
  File "test.py", line 3, in <module>
    tun.up()
  File "/usr/local/lib/python3.7/dist-packages/pytap2/__init__.py", line 213, in up
    raise IfconfigError()
pytap2.IfconfigError

Identical error message.

Looks like there is an issue with the lib.

I just tested with Debian on a RPI3. Same issue.

Can't any related discussion in the forum.

Any clue from anybody ?

The text was updated successfully, but these errors were encountered:

geeksville · 2021-09-04T10:28:51Z

This issue has been mentioned on Meshtastic. There might be relevant details there:

https://meshtastic.discourse.group/t/meshtastic-tunnel-sh-1-ifconfig-not-found/3818/1

KiwiHC16 · 2021-09-04T10:34:05Z

johnthagen/pytap2#8

KiwiHC16 · 2021-09-04T11:06:04Z

https://linuxconfig.org/how-to-install-missing-ifconfig-command-on-debian-linux

apt-get install net-tools

this issue looks solve but I fall into an other one:

root@host:~# meshtastic --tunnel
Connected to radio
INFO:root:Starting IP to mesh tunnel (you must be root for this *pre-alpha* feature to work).  Mesh members:
INFO:root:Node !f244c480 has IP address 10.115.196.128
INFO:root:Node !f244c500 has IP address 10.115.197.0
Exception in thread Thread-3:
Traceback (most recent call last):
  File "/usr/lib/python3.7/threading.py", line 917, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.7/threading.py", line 865, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/local/lib/python3.7/dist-packages/meshtastic/tunnel.py", line 170, in __tunReader
    p = tap.read()
  File "/usr/local/lib/python3.7/dist-packages/pytap2/__init__.py", line 144, in read
    return os.read(self._fd, num_bytes)
OSError: [Errno 9] Bad file descriptor

@geeksville which Linux distrubion do you use ?

KiwiHC16 · 2021-09-04T11:36:45Z

I'm not lucky ;-(
Now with a Fedora distro I'm getting:

[root@localhost ~]# meshtastic --tunnel
Connected to radio
INFO:root:Starting IP to mesh tunnel (you must be root for this *pre-alpha* feature to work).  Mesh members:
INFO:root:Node !f244c480 has IP address 10.115.196.128
INFO:root:Node !f244c500 has IP address 10.115.197.0
Exception in thread Thread-3:
Traceback (most recent call last):
  File "/usr/lib64/python3.8/threading.py", line 932, in _bootstrap_inner
    self.run()
  File "/usr/lib64/python3.8/threading.py", line 870, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/local/lib/python3.8/site-packages/meshtastic/tunnel.py", line 170, in __tunReader
    p = tap.read()
  File "/usr/local/lib/python3.8/site-packages/pytap2/__init__.py", line 144, in read
    return os.read(self._fd, num_bytes)
OSError: [Errno 9] Bad file descriptor

KiwiHC16 · 2021-09-04T11:37:56Z

meshtastic --reboot

works. I see the device rebooting.

KiwiHC16 · 2021-09-04T11:52:56Z

@geeksville On which firmware version tunnel was tested ?
(I have FW 1.2.45.b674054)

KiwiHC16 · 2021-09-04T12:36:17Z

Same behavior with firmware-tbeam-1.2.5.bin

KiwiHC16 · 2021-09-04T12:37:45Z

#96 ?

markbirss · 2021-09-04T13:52:12Z

@KiwiHC16

I also cant get tunnel working

KiwiHC16 · 2021-09-04T22:58:29Z

cd /usr/local/lib/python3.7/dist-packages/meshtastic
vi tunnel.py

Comment Thread and call __tunReader() around line 104:

        logging.debug(f"starting TUN reader, our IP address is {myAddr}")
        self.__tunReader()
        # self._rxThread = threading.Thread( target=self.__tunReader, args=(), daemon=True)
        # self._rxThread.start()

Launch meshtastic --tunnel

mesh0 interface is up

ifconfig
mesh0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 200
        inet 10.115.197.0  netmask 255.255.0.0  destination 10.115.197.0
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 500  (UNSPEC)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1  bytes 48 (48.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Ping is ok:

# ping 10.115.197.0
PING 10.115.197.0 (10.115.197.0) 56(84) bytes of data.
64 bytes from 10.115.197.0: icmp_seq=1 ttl=64 time=0.022 ms
64 bytes from 10.115.197.0: icmp_seq=2 ttl=64 time=0.034 ms
64 bytes from 10.115.197.0: icmp_seq=3 ttl=64 time=0.033 ms

KiwiHC16 · 2021-09-05T00:17:51Z

Modification done into tunnel.py

Around line 100:

        from pytap2 import TapDevice
        self.tun = TapDevice(name="mesh")
        self.tun.up()
        self.tun.ifconfig(address=myAddr, netmask=netmask, mtu=200)
        logging.info(f"starting TUN reader, our IP address is {myAddr}")

        self._rxThread = threading.Thread( target=self.__tunReader, args=(), daemon=True)
        self._rxThread.start()

With modification:

        from pytap2 import TapDevice
        self.tun = TapDevice(name="mesh")
        self.tun.up()
        self.tun.ifconfig(address=myAddr, netmask=netmask, mtu=200)
        logging.info(f"starting TUN reader, our IP address is {myAddr}")
        while True:
            p = self.tun.read()
            logging.info(f"IP packet received on TUN interface, type={type(p)}")
            destAddr = p[16:20]
            if not self._shouldFilterPacket(p):
                self.sendPacket(destAddr, p)
        # self._rxThread = threading.Thread( target=self.__tunReader, args=(ttaapp,), daemon=True)
        # self._rxThread.start()

Then everything work. I can ping, ssh and http a web page.

Seams to confirm an issue in relation with the Thread.

KiwiHC16 · 2021-09-05T00:23:44Z

Can't move TUN creation in the __tunReader function as also needed in the write. So the question is how do we pass the tun to the thread ?

jdstroy · 2021-09-05T12:03:23Z

Take a look at #106; see if that works for you.

markbirss · 2021-09-05T15:29:52Z

@jdstroy

#106;, fixed the issue for me, thank you

KiwiHC16 · 2021-09-05T17:39:49Z

You PR looks so simple !
I'll test it as soon as I can.

KiwiHC16 · 2021-09-05T18:27:36Z

I just tested between:
RPI3 - USB - TBeam - Lora - TBeam - USB - VM Debian

Pings work in both directions.

Thanks a lot.

@geeksville please inject the PR in the Trunk.

I'm closing the issue.

marek22k · 2023-12-05T09:56:48Z

On Linux distributions ifconfig is no longer up to date and ip should be used. The only legitimate purpose for ifconfig would be on BSD systems.

KiwiHC16 mentioned this issue Sep 4, 2021

ifconfig error johnthagen/pytap2#8

Closed

KiwiHC16 changed the title ~~meshtastic --tunnel -> sh: 1: ifconfig: not found~~ meshtastic --tunnel -> OSError: [Errno 9] Bad file descriptor Sep 4, 2021

KiwiHC16 changed the title ~~meshtastic --tunnel -> OSError: [Errno 9] Bad file descriptor~~ meshtastic --tunnel -> Read TUN in a Thread failure Sep 5, 2021

KiwiHC16 closed this as completed Sep 5, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

meshtastic --tunnel -> Read TUN in a Thread failure #104

meshtastic --tunnel -> Read TUN in a Thread failure #104

KiwiHC16 commented Sep 4, 2021 •

edited

geeksville commented Sep 4, 2021

KiwiHC16 commented Sep 4, 2021

KiwiHC16 commented Sep 4, 2021

KiwiHC16 commented Sep 4, 2021 •

edited

KiwiHC16 commented Sep 4, 2021

KiwiHC16 commented Sep 4, 2021

KiwiHC16 commented Sep 4, 2021

KiwiHC16 commented Sep 4, 2021 •

edited

markbirss commented Sep 4, 2021

KiwiHC16 commented Sep 4, 2021

KiwiHC16 commented Sep 5, 2021

KiwiHC16 commented Sep 5, 2021 •

edited

jdstroy commented Sep 5, 2021

markbirss commented Sep 5, 2021 •

edited

KiwiHC16 commented Sep 5, 2021

KiwiHC16 commented Sep 5, 2021

marek22k commented Dec 5, 2023

meshtastic --tunnel -> Read TUN in a Thread failure #104

meshtastic --tunnel -> Read TUN in a Thread failure #104

Comments

KiwiHC16 commented Sep 4, 2021 • edited

geeksville commented Sep 4, 2021

KiwiHC16 commented Sep 4, 2021

KiwiHC16 commented Sep 4, 2021

KiwiHC16 commented Sep 4, 2021 • edited

KiwiHC16 commented Sep 4, 2021

KiwiHC16 commented Sep 4, 2021

KiwiHC16 commented Sep 4, 2021

KiwiHC16 commented Sep 4, 2021 • edited

markbirss commented Sep 4, 2021

KiwiHC16 commented Sep 4, 2021

KiwiHC16 commented Sep 5, 2021

KiwiHC16 commented Sep 5, 2021 • edited

jdstroy commented Sep 5, 2021

markbirss commented Sep 5, 2021 • edited

KiwiHC16 commented Sep 5, 2021

KiwiHC16 commented Sep 5, 2021

marek22k commented Dec 5, 2023

KiwiHC16 commented Sep 4, 2021 •

edited

KiwiHC16 commented Sep 4, 2021 •

edited

KiwiHC16 commented Sep 4, 2021 •

edited

KiwiHC16 commented Sep 5, 2021 •

edited

markbirss commented Sep 5, 2021 •

edited