Ok, so I wanted to open an IPv6 tunnel from my laptop to my home Mac mini and I wanted to forward my web traffic over that ssh tunnel.
What worked:
ssh -l me -6 2002:4bbd:e752:1:211:24ff:fed6:ddb2 -L8080:127.0.0.1:8080
(plus setting my proxy in Firefox to ::1 over port 8080)
(NOTE: I could not access IPv6 only hosts via this tunnel, only IPv4 hosts. So it "half worked". I'm blaming Squid not being IPv6 aware)
What didn't work:
ssh -l me -6 2002:4bbd:e752:1:211:24ff:fed6:ddb2 -L8080:[::1]:8080
(Firefox set to either ::1 or 127.0.0.1)
A black webpage is displayed but I do not get a 404 error.
Looking at what worked I wonder if my tunnel was actually sending my 8080 bound traffic over my IPv4 loopback; it certainly looks to be configured that way and web pages do display. Using a loopback (during tunnel construction) of "::1" gives the following error "channel 2: open failed: connect failed: Connection refused".
Hum. Why. Why. Why. I'm missing something obvious.
Subscribe to:
Post Comments (Atom)
1 comment:
Whoops. Squid is not IPv6 aware. That's why my tunnel worked with the 127.0.0.1 in the loopback and not the ::1.
Post a Comment