allow iodine to tunnell through other protocols

[guest]

This may be done by dividing iodine into frontend and backend. Frontend should do all communication via it's desired protocol (dns, icmp, jabber, etc), and backend do all common stuff as compression, fragmentation, error correction, interaction with tun/tap/stdin/stdout, etc.

For exampe of tunneling through the other protocols, I provide here the sources of ppp-over-jabber tunnel.

[guest]

reference implementation of ppp-over-jabber tunnel

[guest]

Another examples: tunneling over icmp

 http://p6drad-teel.net/~windo/release/  http://thomer.com/icmptx/

[guest]

VTun may be used as backend:  http://vtun.sourceforge.net/features.html

[yarrick]

This is not a small task, and I think it goes outside the scope of iodine.

The FreeBSD team attempted to build this already:  http://wiki.freebsd.org/mtund

[guest]

Iodine already has its's tunneling/compression/auth capabilities, so making it modular may force others to write thier own protocol plugings.

Anyway, it's not an easy task and should not be considered as first and foremost.

[guest]

mtund is not cross platform, unfortunally.

[yarrick]

I dont believe in "forcing" others into creating plugins. If vtun is used as backend, what ties this ticket to iodine?

Making mtund (if it actually is completed and works) run on other platforms is probably easier than rewriting it again.