bukka
Newbie
Posts: 8
|
 |
« on: 02 March 2011, 07:55:57 pm » |
|
I have had my sheevaplug for about a week. When it arrived the first thing I did was to flash it with debian squeeze. So I did not try ssh tunnelling with the standard ubuntu image. My problem is I can putty into the sheevaplug fine but when I try to tunnel my browser traffic the putty session freezes and the browser takes a very long time to resolve and load. I have tried a different network cable but with no luck. I even thought it might be dhcp so I assigned a static ip but still the same issue.
I tried different nameservers but still nothing. Could the network port be faulty? Or am I missing a config value or something?
Any help would be much appreciated as I was hoping to direct my ssh tunnelling traffic to the sheeva rather than through my nas.
b.
|
|
|
|
|
Logged
|
|
|
|
Confusticated
New IT customer
Hero Member
Posts: 510
|
|
« Reply #1 on: 02 March 2011, 08:29:15 pm » |
|
There are many configuration issues that can affect tunnelling.
When the tunnel does work but takes a considerable time to come up the fault is most commonly related to name resolving.
Run the tunnel with debug switched on, and run a packet sniffer (wireshark is a good one to choose).
|
|
|
|
|
Logged
|
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!
|
|
|
bukka
Newbie
Posts: 8
|
|
« Reply #2 on: 04 March 2011, 05:28:54 pm » |
|
Thanks for your post. I ran putty with logging on and all I could see was that there was a lot of 'Event Log: Forwarded port closed'. It gets to the stage were the browser is just timing out. It's really weird as I've setup ssh and proxy switcher the exact same way as I have done before on my nas.
Any idea's of what I should be looking for in wireshark?
b.
|
|
|
|
|
Logged
|
|
|
|
Confusticated
New IT customer
Hero Member
Posts: 510
|
|
« Reply #3 on: 04 March 2011, 10:56:59 pm » |
|
Where your DNS requests are going, and whether you are getting any replies.
|
|
|
|
|
Logged
|
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!
|
|
|
bukka
Newbie
Posts: 8
|
|
« Reply #4 on: 06 March 2011, 12:43:07 pm » |
|
Seems IE doesn't have a problem. I surf over the tunnel fine without it freezing just having issues with chrome and firefox. Not sure if this means anything.
I ran ssh in debug mode but I didn't see anything out of the ordinary. I'll upload it to pastebin for you to check in a min.
|
|
|
|
|
Logged
|
|
|
|
bukka
Newbie
Posts: 8
|
|
« Reply #5 on: 07 March 2011, 11:30:51 am » |
|
I did a fresh flash yesterday even using the newit rootfs version of debian. I haven't changed any setting completely left it as standard and I still experience the same thing.
Are there any newit staff who can help? Do they look at this forum? As I bought the sheeva for ssh tunnelling and at the minute its not fit for its purpose.
Is there a support email as the site does not list one?
|
|
|
|
|
Logged
|
|
|
|
|
NewIT_Marcus
|
|
« Reply #6 on: 07 March 2011, 05:47:01 pm » |
|
Are there any newit staff who can help? Do they look at this forum? As I bought the sheeva for ssh tunnelling and at the minute its not fit for its purpose.
Is there a support email as the site does not list one?
This is the correct place to ask. Unfortunately, I don't know much about tunnelling. If you explain exactly what it is that you are doing, we can replicate your tests and let you know if we obtain the same results. |
|
|
|
|
Logged
|
|
|
|
bukka
Newbie
Posts: 8
|
|
« Reply #7 on: 07 March 2011, 07:18:14 pm » |
|
Putty into the sheevaplug with a dynamic port setup. Then in your browser you setup a socks5 host forwarding it to localhost:port. Then all your browser traffic is securely tunnelled through the sheeva.
I've never had an issue before setting up ubuntu/debian servers and being able to tunnel traffic through them. I've tried different network cables, different ports on my router and switch. I've tried three different rootfs, even your own debian one thinking that perhaps I'd forgotten to install something. Putty just freezes and then the browser times out or on the rare occasion loads but with missing content. Have I a faulty network port on my week and half old sheeva?
|
|
|
|
|
Logged
|
|
|
|
|
NewIT_Marcus
|
|
« Reply #8 on: 07 March 2011, 07:49:02 pm » |
|
Putty into the sheevaplug with a dynamic port setup. Then in your browser you setup a socks5 host forwarding it to localhost:port. Then all your browser traffic is securely tunnelled through the sheeva.
Please be specific about the commands. |
|
|
|
|
Logged
|
|
|
|
bukka
Newbie
Posts: 8
|
|
« Reply #9 on: 07 March 2011, 08:03:44 pm » |
|
I use putty. I don't connect via terminal so I wouldn't know the commands that putty generates.
|
|
|
|
|
Logged
|
|
|
|
|
NewIT_Marcus
|
|
« Reply #10 on: 07 March 2011, 08:23:19 pm » |
|
Please explain what you are doing - in detail - so that we can replicate it.
|
|
|
|
|
Logged
|
|
|
|
|
|
bukka
Newbie
Posts: 8
|
|
« Reply #12 on: 08 March 2011, 08:43:20 am » |
|
Step 3 in the above tutorial is exactly how I set up putty for ssh tunnelling. Then in your browser of choice you set up socks5 to point to localhost:7070.
|
|
|
|
|
Logged
|
|
|
|
Confusticated
New IT customer
Hero Member
Posts: 510
|
|
« Reply #13 on: 08 March 2011, 05:48:14 pm » |
|
And how have you set up the sheevaplug ?
|
|
|
|
|
Logged
|
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!
|
|
|
bukka
Newbie
Posts: 8
|
|
« Reply #14 on: 09 March 2011, 01:07:53 pm » |
|
Nothing apart from making sure that openssh-server and openssh-client is installed. There is no config required as long as you can create an ssh connection.
|
|
|
|
|
Logged
|
|
|
|
|
