Talk:Tunneling protocol

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Computing / Networking (Rated Start-class, Mid-importance)
WikiProject icon This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 Mid  This article has been rated as Mid-importance on the project's importance scale.
Taskforce icon
This article is supported by Networking task force (marked as Mid-importance).
 

Why is PPP over modem not considered tunneling?[edit]

Why is PPP over a POTS or ISDN modem not considered as tunneling? PPP over modem is an LLC protocol encapsulated in another. Okay, a modem behaves as if it were a circuit switched physical link (an asynchronous serial link), but modern modems include LLC sublayer, since they divide the data into blocks (some kind of packets) rather than codewords (there are no start and stop bits), and performs packet mode flow control and automatic repeat request.

I don't undertand the definition, that tunneling is encapsulation of A in B as if B were a datalink protocol. In many tunelling protocols B is a datalink protocol. Example: PPPoE, PPPoA, etc. Mange01 18:09, 15 November 2006 (UTC)

You're right.[1] ISDN, DSL, X.25, Frame Realy etc. is tunneling.[2] The statement does not match the Wikipedia ("Protocol encapsulation carried out by conventional layered protocols, in accordance with the OSI model or TCP/IP model (for example: HTTP over TCP over IP over PPP over a V.92 modem) is not considered tunneling"). e.g. DSL modem is part of the tunnel. -- 91.64.133.157 (talk) 06:01, 16 February 2011 (UTC)

Why was the web link removed by anti-vandalism bot?[edit]

User:Starunj (who I am not affiliated with) added the following external reference to Tunneling protocol: Tunneling SSH from behind an HTTP proxy server

Why was this considered as vandalism and reverted by VoABot_II ? Mange01 12:30, 5 December 2006 (UTC)

Answer at the user talk:VoABot_II page:
One regexp was too short (for deteting all consonant garbage words). Fixed.Voice-of-All 19:24, 5 December 2006 (UTC)
Okay . I revert the bot revert. Mange01 22:17, 6 December 2006 (UTC)

An SSH tunnel is not a VPN[edit]

SSH tunnel != VPN

A VPN is a totally different animal from an SSH tunnel. They should not be confused. This is like confusing HTTP and HTML. The SSH protocol does not specify anything about VPN features. It is true the OpenSSH implements a VPN feature, but this is a feature on top of the SSH protocol. And only OpenSSH versions 4.3 or later implement this feature. And you must use an OpenSSH client that implements the VPN feature to talk to an OpenSSH server that also implements the VPN feature. This VPN feature is not compatible with any other VPN clients or any other SSH clients. A VPN is an abstract concept. It is not a standard protocol and has no specification. A VPN does not even have to be encrypted.

--Noah (talk) 09:59, 7 November 2008 (UTC)

reyhan kolbastı[edit]

süper —Preceding unsigned comment added by 85.99.45.109 (talk) 11:36, 29 August 2009 (UTC)

Taint[edit]

Anyone else feel the page is tainted by having Microsoft Windows as part of the example for SSH tunneling. I mean, it's a little ironic to say the least. 206.196.158.130 (talk) 14:08, 12 May 2011 (UTC)

I find the picture confusing[edit]

Which is hosta? Which is hostb? Is the shown command run on hosta? — Preceding unsigned comment added by 65.126.15.122 (talk) 15:19, 29 May 2013 (UTC)

The example section can be improved[edit]

The example says, "Example of how to set up an SSH tunnel in bash:" but it has nothing specific to bash. It should rather read, "Example of how to set up an SSH tunnel in OpenSSH:". Also the ssh command has been unnecessarily complicated, just `ssh -D 8080 user@host` should be enough to set up the SOCKS proxy. Even -p 2222 is not strictly required as the default 22 port would probably work for most of the cases, but `-f -C -q -N` are just unnecessary — Preceding unsigned comment added by Rabisg (talkcontribs) 14:12, 9 August 2014 (UTC)

Hello there! That's a good remark, went ahead and cleaned up the section a bit. You're right that the actual selection of switches could be simplified, but I guess the original author wanted to "show off" various existing possibilities. — Dsimic (talk | contribs) 05:44, 11 August 2014 (UTC)
But that should be made clearer in the example, shouldn't it? — Preceding unsigned comment added by Rabisg (talkcontribs) 15:19, 12 August 2014 (UTC)
Hm, anyone interested in actual details can have a look at the ssh man page. Also, if a reader isn't willing to look up, he/she probably isn't actually interested in using ssh to create tunnels; prepping everything for a blind copy&paste makes little sense, in my opinion. — Dsimic (talk | contribs) 22:58, 12 August 2014 (UTC)