-
Notifications
You must be signed in to change notification settings - Fork 12
SW_DSLite
Internet providers are increasingly moving towards only providing customers with pure IPv6 connections (DS Lite or CGN). However, the i-telex software is only IPv4-compatible. This applies not only to pure Internet communication, but also to the underlying database structures for TNS, etc. IPv6 capability for i-telex is currently not in sight.
With DS-Lite, all carrier internal traffice is done via IPv6; transition to IPv4 network is done at the carrier borders. That means that your router is not reachable from the IPv4 part of the internet, and also your piTelex device is not. To make piTelex reachable externally in this case, there are different approaches:
This option enables users without a public IPv4 address to participate in the i-Telex network. If this option is activated, the i-Telex establishes a dedicated connection to a switching server equipped with an IPv4 address. Every incoming connection is then “forwarded” via this server. The switching server is also often called Centralex.
Unfortunately, piTelex does not (yet) support the Centralex protocol. ----> Programmer wanted :-)
Because centralex is not implemented in piTelex yet, we have to find a different solution. Goal is to tunnel the piTelex IPv4 packets over an IPv6 network, i.e. encapsulate the piTelex-packets in a IPv6 transport.
There are commercial service provider on the market for this, but there is also a DIY solution for this.
Consider using release packages for software installation: https://github.com/fablab-wue/piTelex/releases
-
Local use
-
i-Telex
-
Advanced Topics
-
Tools & Gadgets
-
TW39 (current loop)
-
ED1000 (FSK modulation)
-
V.10 (TeKaDe FS200, FS220)
-
SEU-M-board based
- with Austrian AGT (Ö-AGT, current loop)
- as replacement for SEU-B card inside LO2000, LO2001, LO3000