New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Follow this tutorial
Here's the full tutorial
Hey, at least it got you to remove the rickroll.
On a more serious note, the
-D
controls the address of the local SOCKS proxy spawned by SSH, so whether that's on IPv4 or IPv6 isn't of much concern.As long as you have IPv6 on the VPS you're connecting to, any connections for IPv6 hosts should be routed through the local socks proxy and subsequently the IPv6 address.
I have an ipv6-only VPS I want to proxy through. I tried -D 0.0.0.0:1080 but it doesn't work, even with ipv6.google.com
I get all this:
channel 5: open failed: connect failed: open failed
channel 3: open failed: connect failed: open failed
channel 3: open failed: connect failed: open failed
channel 4: open failed: connect failed: open failed
channel 5: open failed: connect failed: open failed
channel 3: open failed: connect failed: open failed
channel 4: open failed: connect failed: open failed
channel 5: open failed: connect failed: open failed
channel 3: open failed: connect failed: open failed
channel 4: open failed: connect failed: open failed
channel 5: open failed: connect failed: open failed
channel 3: open failed: connect failed: open failed
channel 4: open failed: connect failed: open failed
channel 5: open failed: connect failed: open failed
channel 3: open failed: connect failed: open failed
channel 4: open failed: connect failed: open failed
channel 5: open failed: connect failed: open failed
channel 3: open failed: connect failed: open failed
channel 4: open failed: connect failed: open failed
channel 5: open failed: connect failed: open failed
channel 3: open failed: connect failed: open failed
channel 4: open failed: connect failed: open failed
channel 5: open failed: connect failed: open failed
channel 3: open failed: connect failed: open failed
channel 4: open failed: connect failed: open failed
channel 5: open failed: connect failed: open failed
channel 3: open failed: connect failed: open failed
channel 4: open failed: connect failed: open failed
channel 5: open failed: connect failed: open failed
channel 3: open failed: connect failed: open failed
channel 4: open failed: connect failed: open failed
channel 5: open failed: connect failed: open failed
channel 3: open failed: connect failed: open failed
channel 4: open failed: connect failed: open failed
channel 5: open failed: connect failed: open failed
channel 3: open failed: connect failed: open failed
channel 4: open failed: connect failed: open failed
channel 5: open failed: connect failed: open failed
I bet you get more than this.
If you seek help, share the full output of your console including the full shell prompt with the command you are executing etc. Otherwise others barely have a chance guessing what exactly you are doing. And without knowing what you are doing, nobody can tell you what you are doing wrong.
I get the thing I posted above once I actually connect to the proxy.
Do a
ssh -vvv -ND 1080 user@pass
and try to connect to the IPv6 website; that might tell us more about why you're getting those channel open errors.btw the VPS ha> @stevewatson301 said:
a bunch of this appears... could this have to do with the fact that the VPS has no IPv4? the sites I am using are ipv6, I tried ipv6.google.com
What's interesting is why there's a
dynamic-tcpip
request for142.251.37.99
and108.177.127.188
, ideally you'd seeipv6.google.com
itself. For example, in my case:What are you using to make these requests through the socks proxy?
chrome
I'm not sure what OS you use, but Chrome follows OS settings on Mac and thus I've never bothered to use it, I usually install Proxy Helper and call it a day.
How about you give it a try?
that worked, thank you!