after all that, I think the problem was I embarrassingly forgot to
restart the daemon :)
Thanks again to all.
Mike
--
Please post to: Hampshire@mailman.lug.org.uk
Web Interface: https://mailman.lug.org.uk/mailman/listinfo/hampshire
LUG URL: http://www.hantslug.org.uk
Mike
If you're interested in finding out the root cause then it might be worth
backing up the router config and doing a factory reset on it just to prove
it's not something screwy in the firmware, if nothing else you will
eliminate that as a possible cause.
Try to manually configure it on
Hi Mike, you've got some useful stuff to try from others in the thread.
When you're changing sshd_config you're restarting sshd afterwards?
From an Internet-based Linux host, does nc some.dyndns.org
http://some.dyndns.org produce an openssh banner?
My next steps would be ssh -v on
On 24 June 2011 04:03, Mike Burrows testerm...@knology.net wrote:
On 6/23/11 11:12 AM, Benjie Gillam wrote:
Can you ssh -p from another computer/device on your LAN? (You may
need to use your internal IP address to do so.) If so then you at least know
SSH is working. If not, then I'd use
Can you ssh -p from another computer/device on your LAN? (You may need
to use your internal IP address to do so.) If so then you at least know SSH
is working. If not, then I'd use netcat.
is an unprivileged port (1024) so if you shut down sshd you should be
able to run
nc -v -l -p
On Thu, 23 Jun 2011 17:12 +0100, Benjie Gillam
ben...@jemjie.com wrote:
is an unprivileged port (1024) so if you shut down sshd you
should be able to run
nc -v -l -p
on the server. Then from another computer/device run
I'm no expert, but shouldn't that be `nc -vl ` to set up
I have a BT Home Hub 2 on their Infinity broadband and I've been trying to
set up something similar to get to my NAS drives from out on the Internet. I
too have been unable to get it to work no matter what I do, yesterday I
discovered there's a bug in the firmware that means you have to hard reset
On Tue, 21 Jun 2011 21:09:25 -0500
Mike Burrows testerm...@knology.net wrote:
Hi folks.
I can ssh into my debian machine on port 22 (with that port forwarded
on my router) using
ssh testerm...@some.dyndns.org
However, when i change the port to (changing the router of
course) and
What I tend to do (when it works despite bugs in the BT Home Hub firnware)
is link the incoming port number to the static IP address on my internal
network
What I do is to run my external SSH daemon configured to accept key-based
logins only.
I run it on port 22. I get *thousands* of
Incidentally, if you're moving your SSH port because of bots trying to brute
force your SSH server, don't use a guessable port number like .
I did put a honeypot PC in my DMZ for a while so that everything incoming
was forwarded to it by the router - and I have seen bots using other ports
Vic
Agreed, and the bot-driven brute force attempts are harmless enough if
you're not using password authentication.
But I take a run silent run deep attitude in that I want to reveal as
little information as possible about what I'm running on my home network
because I never know if some human
But I take a run silent run deep attitude in that I want to reveal as
little information as possible about what I'm running on my home network
because I never know if some human isn't going to look through those bot
logs and try to manually break into my systems - the less information that
Yep, that's the one.
I last used it about 3 years ago and I found it to be a bit flaky but I
think it's got a lot better since then.
Incidentally, there's nothing like being hacked to make you a bit paranoid
about security! :-)
About 8 years ago, I stupidly left an FTP server open to the
On 22 June 2011 09:28, Vic l...@beer.org.uk wrote:
That's a security through obscurity argument. It does no harm unless you
actually rely on that obscurity for your security - but in the same
breath, if you're not relying on obscurity, then it does no good either.
Yes, very true but unless
Hi Mike,
On Tue, Jun 21, 2011 at 09:09:25PM -0500, Mike Burrows wrote:
However, when i change the port to (changing the router of course)
and repeat using
ssh -p testerm...@some.dyndns.org
I get an error that the connection was reset by peer and I cannot ssh in.
What am I not
However, when i change the port to (changing the router of course)
and repeat using
ssh -p testerm...@some.dyndns.org
I get an error that the connection was reset by peer and I cannot ssh in.
What am I not doing please?
If you haven't solved it yet, try running the ssh client with
Mike
It's definitely not a BT Home Hub 2 is it? Those are the exact symptoms of
what I get with the known bug I mentioned earlier.
It might also be worth mentioning that BT Home Hubs are made by Thomson,
even though I suspect that BT have their own specific firmware for it.
Regards
Peter
On
On Wed, Jun 22 at 11:18, Mike Burrows wrote:
...
what else needs changing to allow the use of a non-standard port?
You're not running a local firewall on the server are you?
Or if you are have you poked a hole.
--
Bob Dunlop
--
Please post to: Hampshire@mailman.lug.org.uk
Web
Hi,
On Wed, Jun 22 at 11:18, Mike Burrows wrote:
...
ssh -p testerm...@some.dyndns.org
I get an error that the connection was reset by peer and I cannot ssh in.
...
- use the shell script mentioned before i get this error:
nodename nor servname provided, or not known
The nature
Hi folks.
I can ssh into my debian machine on port 22 (with that port forwarded on
my router) using
ssh testerm...@some.dyndns.org
However, when i change the port to (changing the router of course)
and repeat using
ssh -p testerm...@some.dyndns.org
I get an error that the
Which router is it?
Usually mapping WAN: to LAN:22 is should automatically remap the returns
packets. Not sure if your particular router needs an additional firewall rule,
most automatically do so per-mapping.
You could always change the sshd to too! :-)
Ian
On Wednesday 22 June
21 matches
Mail list logo
