On Thu, 18 Oct 2001, Mark Plowman wrote: > David, <..snip..> > through the Firewall works (console, X forwarding etc.), I *can't* see > the listening sockets on 127.0.0.1:13[7-9] on this Win 95 box with a > "netstat -a". > > Seems like a Win NT/Win 95 difference. I will have to investigate... Sorry. I assumed they all behaved the same way. I have only tested it on NT and 2K. <..snip..> > > If you don't want to use \\127.0.0.1\ then you can try adding MS > > Loopback as an additional adapter to your WinXX machine and give it > > a non-127.0.0.1 address probably in one of the non-routable blocks > > ie;172.16.1.1. Then you don't blow away localhost functionality of > > whatever you tunnel. > > Sorry, I don't understand the above. What do you mean with "don't > blow away localhost functionality of whatever you tunnel" ? > A service on any machine is an IP:SOCKET combination. If you have setup your local machine to be the source end of a tunnel for any port, then that service cannot be made available on the local machine too because both have the 127.0.0.1:"XXX" combination. So essentially, if you create an alias for your loopback adapter by adding an MS-Loopback device to the tcp protocol stack but with a different address, you can tunnel the ALIAS:SOCKET combination and still have local access to the LOCALHOST:SOCKET combination.
I have a "xxxxxxxxx" running on my laptop and the same thing running on my server. When I do development work on the laptop I just point to 127.0.0.1 and when I want to use "production" on the server at the end of the tunnel I use the alias address. Enjoy, dbc. > > > Greetings > > > Mark > -- David B. Cook, <[EMAIL PROTECTED]> Linux -- up 14 days because it can. 8:30pm up 14 days, 46 min, 1 user, load average: 0.00, 0.02, 0.01 _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
