[kwlug-disc] (IP/TCP) Port Relaying ... command is called what, again?

unsolicited unsolicited at swiz.ca
Tue Feb 4 15:00:16 EST 2014


Yes, apparently ICS (Internet Connection Sharing) is present in windows 
desktop versions, but comes with all sorts of nastiness / baggage. e.g. 
Sets up a DHCP server, requires the use of 192.168.0.0/24, have to have 
two nics, and all sorts of other nonsense.

Thank you both, will examine both netcat and sshuttle.

On 14-02-04 08:50 AM, john at vanostrand.com wrote:
>
> A proxy server is the thing generally use d for port 80. It, however,
> is probably the sledgehammer. Proxies can be big and require
> libraries and such.
>
> Net cat is useful for what you want and is lightweight.
>
> There are probably lots of options including some scripting that
> might get you through this.
>
> I thought windows had "connection sharing" specifically for Internet
> but I figured it could work for vpn too. That does Nat.
>
>
> Sent from my BlackBerry 12 neural implant. Original Message From:
> unsolicited Sent: Tuesday, February 4, 2014 7:39 AM To: Kwlug-Disc
> Reply To: KWLUG discussion Subject: [kwlug-disc] (IP/TCP) Port
> Relaying ... command is called what, again?
>
> I'm setting up a (Open)VPN which by necessity is only point to point
> (machine to machine). Because that windows 7/8 machine won't nat
> (masquerade), there is no access to machines beyond that point. (No
> access to premise routers so can't set up a port forward.)[Machine
> has cygwin installed and happy.] Bridging is an option, but I blew
> away my monthly 60GB Roger's traffic limit in 4 days when I was
> experimenting, presumably due to broadcasts. So, back to tunnelling,
> but no win 7 natting I've been able to find. Except for
> http://rusroute.com/, which I have no experience with to trust.
>
> It occurs to me I only really need port 80 from another device on
> the network, all other requirements can be satisfied with this point
> to point.
>
> So, it seems to me I only need something that will forward a port on
> a client's behalf. e.g. portforward localhost:8080 remotehost:80.
> Then the remote end of the link can just do
> http://othersideofvpnip:8080 and get on with their day.
>
> (I know ssh will do all this for the port - I'm avoiding the command
> line / script weirdnesses with this particular user.)
>
> So ... what's the command to use? netcat?
>
> Netcat being a 'swiss army knife'
> (http://en.wikipedia.org/wiki/Netcat) seems a little like using a
> sledgehammer when only a wee tap will do it.
>
> Other lighter options, or is netcat the beastie I'm looking for?
>
>
> _______________________________________________ kwlug-disc mailing
> list kwlug-disc at kwlug.org
> http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org
>
>
> _______________________________________________ kwlug-disc mailing
> list kwlug-disc at kwlug.org
> http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org
>





More information about the kwlug-disc mailing list