On Sat, 6 Jan 2007 00:07:00 +
Mick [EMAIL PROTECTED] wrote:
I just checked and it seems that the OEM firmware on the netgear
drops all ssh attempts to connect. :(
Im sure your router's firmware isn't allowing ssh connections. The
router itself does not offer ssh access to anyone. What
On Monday 08 January 2007 09:53, Dan [EMAIL PROTECTED] wrote about 'Re:
[gentoo-user] [OT] Router for ssh tunnel/SOCKS proxy':
I am not sure what you mean by this, but I do hope you'll consider
using a normal commodity PC as your router.
He's already got a home router. Some Netgear model (see
On Mon, 8 Jan 2007 11:29:52 -0600
Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote:
if you want to take advantage of
gigabit speeds (or more than a dozen 100mbit ports) you'll definitely
want a dedicated solution -- the PCI bus just can't keep up. Maybe
there's a solution in PCIe or PCI-X,
On Monday 08 January 2007 11:43, Dan [EMAIL PROTECTED] wrote about 'Re:
[gentoo-user] [OT] Router for ssh tunnel/SOCKS proxy':
Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote:
if you want to take advantage of
gigabit speeds (or more than a dozen 100mbit ports) you'll definitely
want
On Saturday 06 January 2007 04:32, Boyd Stephen Smith Jr. wrote:
On Friday 05 January 2007 15:44, Etaoin Shrdlu [EMAIL PROTECTED]
wrote about 'Re: [gentoo-user] [OT] Router for ssh tunnel/SOCKS proxy':
On Friday 5 January 2007 21:25, Mick wrote:
OK. I don't think I need to run a full VPN
On Saturday 6 January 2007 05:32, Boyd Stephen Smith Jr. wrote:
Finally, if your email program and browser are SOCKS aware, you could
simply set them up to use your ssh connection as a SOCKS proxy.
There's specific support for this in OpenSSH, so that you don't have
to open ports
On Saturday 06 January 2007 04:06, Mick [EMAIL PROTECTED] wrote
about 'Re: [gentoo-user] [OT] Router for ssh tunnel/SOCKS proxy':
On Saturday 06 January 2007 04:32, Boyd Stephen Smith Jr. wrote:
On Friday 05 January 2007 15:44, Etaoin Shrdlu
[EMAIL PROTECTED]
wrote about 'Re: [gentoo
On 05 January 2007 14:22, Mick wrote:
Hi All,
Apologies for the off-topic post but I thought to ask here because there
have been a couple of threads in the past where embedded Linux OS' for
hardware routers were discussed and that may offer a solution to my
problem.
I would like to be able
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Uwe Thiem wrote:
What do you mean by tunnelling? Do you want an IP layer tunnelled through
ssh?
Bad idea! I means TCP over TCP which is bound to fail when the outer and
inner TCP timeouts get out of sync.
More about that here:
Why TCP over
On Friday 05 January 2007 14:17, Arturo 'Buanzo' Busleiman wrote:
Uwe Thiem wrote:
What do you mean by tunnelling? Do you want an IP layer tunnelled through
ssh? Bad idea! I means TCP over TCP which is bound to fail when the outer
and inner TCP timeouts get out of sync.
More about that
On Friday 5 January 2007 16:53, Mick wrote:
More about that here:
Why TCP over TCP is a Bad Idea
http://sites.inka.de/sites/bigred/devel/tcp-tcp.html
Hmm, that explains why running VCN through ssh gets a bit ropy at
times?
Do you mean VNC?
So, is port forwarding for browsing and
On Friday 05 January 2007 17:00, Etaoin Shrdlu wrote:
On Friday 5 January 2007 16:53, Mick wrote:
More about that here:
Why TCP over TCP is a Bad Idea
http://sites.inka.de/sites/bigred/devel/tcp-tcp.html
Hmm, that explains why running VCN through ssh gets a bit ropy at
times?
On Friday 5 January 2007 21:25, Mick wrote:
OK. I don't think I need to run a full VPN. I just want to securely
connect to my router at home while I am out about using public wifi
hot spots and thereby to be able to connect to the internet using my
ISP for browsing email. The only ports
Etaoin Shrdlu wrote:
For browsing the internet, the setup is just a little bit more complex.
At least, you need a http proxy running on the router (like squid), then
do port forwarding for ports 80, 443, etc. and set up your browser
accordingly to use the proxy. This way, your http requests
On Friday 05 January 2007 22:00, kashani wrote:
Etaoin Shrdlu wrote:
For browsing the internet, the setup is just a little bit more complex.
At least, you need a http proxy running on the router (like squid), then
do port forwarding for ports 80, 443, etc. and set up your browser
Mick wrote:
I just checked and it seems that the OEM firmware on the netgear drops all ssh
attempts to connect. :(
$ ssh 192.168.0.1
ssh: connect to host 192.168.0.1 port 22: Connection refused
Same story when I use my internet IP address (it times out). It seems that I
will have to
On Friday 05 January 2007 15:44, Etaoin Shrdlu [EMAIL PROTECTED]
wrote about 'Re: [gentoo-user] [OT] Router for ssh tunnel/SOCKS proxy':
On Friday 5 January 2007 21:25, Mick wrote:
OK. I don't think I need to run a full VPN. I just want to securely
connect to my router at home while I am
17 matches
Mail list logo
