Re: [Binari] MIDAS ssh port from home: 6666
I feel an evil presence Frederik Delaere wrote:
Good morning,
As of now midas is listening on a different ssh port if you want to connect from home.
Before this was the default port 22 now it is: 6666 if you want to specify the port from commandline you can do it like this:
ssh -p 6666 username@midas.fvms.ugent.be
scp works like this:
scp -P 6666 /some/dir username@midas.fvms.ugent.be:/tmp
For the lazy people, you can add this to an alias in .bashrc, .bash_profile, .cshrc, ... so you don't have to type all this:
alias midas "ssh -p 6666 username@midas.fvms.ugent.be"
Windows users should look in their favourite ssh client for an option where they can change the port.
Next monday we will close the port 22 on the firewall, so you've got a few days to try it out. Connecting from the internal network to midas doesn't change.
There are hundreds of (failed) login attempts on midas on the ssh port. That's because a lot of botnets scan networks for ssh connections on the default port 22, moving to a different non default port will solve this issue. In case you where wondering why..
Enjoy, Frederik
-- ================================================================== Joost Van Den Cruyce Tel:+32 (0)9 331 38 92 fax:+32 (0)9 3313809 VIB Department of Plant Systems Biology, Ghent University Technologiepark 927, 9052 Gent, BELGIUM jocru@psb.vib-ugent.be http://www.psb.vib-ugent.be ==================================================================
Am I the only one experiencing a really slow midas today? Is a dir with 4000 files really such a problem to do ls on? Sheesh... Sofie Joost Van Den Cruyce wrote:
I feel an evil presence
Frederik Delaere wrote:
Good morning,
As of now midas is listening on a different ssh port if you want to connect from home.
Before this was the default port 22 now it is: 6666 if you want to specify the port from commandline you can do it like this:
ssh -p 6666 username@midas.fvms.ugent.be
scp works like this:
scp -P 6666 /some/dir username@midas.fvms.ugent.be:/tmp
For the lazy people, you can add this to an alias in .bashrc, .bash_profile, .cshrc, ... so you don't have to type all this:
alias midas "ssh -p 6666 username@midas.fvms.ugent.be"
Windows users should look in their favourite ssh client for an option where they can change the port.
Next monday we will close the port 22 on the firewall, so you've got a few days to try it out. Connecting from the internal network to midas doesn't change.
There are hundreds of (failed) login attempts on midas on the ssh port. That's because a lot of botnets scan networks for ssh connections on the default port 22, moving to a different non default port will solve this issue. In case you where wondering why..
Enjoy, Frederik
-- Sofie Van Landeghem PhD Student VIB Department of Plant Systems Biology, Ghent University Bioinformatics and Evolutionary Genomics Technologiepark 927, 9052 Gent, BELGIUM Tel: +32 (0)9 331 36 95 fax:+32 (0)9 3313809 Website: http://bioinformatics.psb.ugent.be
nope, going slow here as well (10 secs to open a new emacs session) :) Sofie Van Landeghem wrote:
Am I the only one experiencing a really slow midas today? Is a dir with 4000 files really such a problem to do ls on? Sheesh...
Sofie
Joost Van Den Cruyce wrote:
I feel an evil presence
Frederik Delaere wrote:
Good morning,
As of now midas is listening on a different ssh port if you want to connect from home.
Before this was the default port 22 now it is: 6666 if you want to specify the port from commandline you can do it like this:
ssh -p 6666 username@midas.fvms.ugent.be
scp works like this:
scp -P 6666 /some/dir username@midas.fvms.ugent.be:/tmp
For the lazy people, you can add this to an alias in .bashrc, .bash_profile, .cshrc, ... so you don't have to type all this:
alias midas "ssh -p 6666 username@midas.fvms.ugent.be"
Windows users should look in their favourite ssh client for an option where they can change the port.
Next monday we will close the port 22 on the firewall, so you've got a few days to try it out. Connecting from the internal network to midas doesn't change.
There are hundreds of (failed) login attempts on midas on the ssh port. That's because a lot of botnets scan networks for ssh connections on the default port 22, moving to a different non default port will solve this issue. In case you where wondering why..
Enjoy, Frederik
-- Sofie Van Landeghem PhD Student VIB Department of Plant Systems Biology, Ghent University Bioinformatics and Evolutionary Genomics Technologiepark 927, 9052 Gent, BELGIUM Tel: +32 (0)9 331 36 95 fax:+32 (0)9 3313809 Website: http://bioinformatics.psb.ugent.be ------------------------------------------------------------------------
_______________________________________________ Binari Implicitly Neglects All Recursive Iterations https://maillist.psb.ugent.be/mailman/listinfo/binari
-- ================================================================== Michiel Van Bel PhD student Tel:+32 (0)9 331 36 95 fax:+32 (0)9 3313809 VIB Department of Plant Systems Biology, Ghent University Technologiepark 927, 9052 Gent, BELGIUM mibel@psb.vib-ugent.be http://www.psb.vib-ugent.be ==================================================================
Sigh... *slowly backs away from midas* Sofie Joost Van Den Cruyce wrote:
nope, it's a global problem
Sofie Van Landeghem wrote:
Am I the only one experiencing a really slow midas today? Is a dir with 4000 files really such a problem to do ls on? Sheesh...
Sofie
Slow doesn't even come close :/ Logging in takes forever, and diskaccess last forever too .. this is no way to work :/ -Kenny On Thu, 11 Jun 2009, Sofie Van Landeghem wrote:
Am I the only one experiencing a really slow midas today? Is a dir with 4000 files really such a problem to do ls on? Sheesh...
Sofie
Joost Van Den Cruyce wrote:
I feel an evil presence
Frederik Delaere wrote:
Good morning,
As of now midas is listening on a different ssh port if you want to connect from home.
Before this was the default port 22 now it is: 6666 if you want to specify the port from commandline you can do it like this:
ssh -p 6666 username@midas.fvms.ugent.be
scp works like this:
scp -P 6666 /some/dir username@midas.fvms.ugent.be:/tmp
For the lazy people, you can add this to an alias in .bashrc, .bash_profile, .cshrc, ... so you don't have to type all this:
alias midas "ssh -p 6666 username@midas.fvms.ugent.be"
Windows users should look in their favourite ssh client for an option where they can change the port.
Next monday we will close the port 22 on the firewall, so you've got a few days to try it out. Connecting from the internal network to midas doesn't change.
There are hundreds of (failed) login attempts on midas on the ssh port. That's because a lot of botnets scan networks for ssh connections on the default port 22, moving to a different non default port will solve this issue. In case you where wondering why..
Enjoy, Frederik
-- ================================================================== Kenny Billiau Web Developer Tel:+32 (0)9 331 36 95 fax:+32 (0)9 3313809 VIB Department of Plant Systems Biology, Ghent University Technologiepark 927, 9052 Gent, BELGIUM kenny.billiau@ugent.be http://bioinformatics.psb.ugent.be ================================================================== "To do what is necessary, always is wise" - Sarek
the top-command doesn't reveal anything special going on, so i suppose it's the network again (one of the routers screwed up its BGP-protocol again :) Kenny Billiau wrote:
Slow doesn't even come close :/ Logging in takes forever, and diskaccess last forever too .. this is no way to work :/
-Kenny
On Thu, 11 Jun 2009, Sofie Van Landeghem wrote:
Am I the only one experiencing a really slow midas today? Is a dir with 4000 files really such a problem to do ls on? Sheesh...
Sofie
Joost Van Den Cruyce wrote:
I feel an evil presence
Frederik Delaere wrote:
Good morning,
As of now midas is listening on a different ssh port if you want to connect from home.
Before this was the default port 22 now it is: 6666 if you want to specify the port from commandline you can do it like this:
ssh -p 6666 username@midas.fvms.ugent.be
scp works like this:
scp -P 6666 /some/dir username@midas.fvms.ugent.be:/tmp
For the lazy people, you can add this to an alias in .bashrc, .bash_profile, .cshrc, ... so you don't have to type all this:
alias midas "ssh -p 6666 username@midas.fvms.ugent.be"
Windows users should look in their favourite ssh client for an option where they can change the port.
Next monday we will close the port 22 on the firewall, so you've got a few days to try it out. Connecting from the internal network to midas doesn't change.
There are hundreds of (failed) login attempts on midas on the ssh port. That's because a lot of botnets scan networks for ssh connections on the default port 22, moving to a different non default port will solve this issue. In case you where wondering why..
Enjoy, Frederik
-- ================================================================== Michiel Van Bel PhD student Tel:+32 (0)9 331 36 95 fax:+32 (0)9 3313809 VIB Department of Plant Systems Biology, Ghent University Technologiepark 927, 9052 Gent, BELGIUM mibel@psb.vib-ugent.be http://www.psb.vib-ugent.be ==================================================================
It's probably gone out for a drink or something... Sofie Michiel Van Bel wrote:
the top-command doesn't reveal anything special going on, so i suppose it's the network again (one of the routers screwed up its BGP-protocol again :)
Kenny Billiau wrote:
Slow doesn't even come close :/ Logging in takes forever, and diskaccess last forever too .. this is no way to work :/
-Kenny
On Thu, 11 Jun 2009, Sofie Van Landeghem wrote:
Am I the only one experiencing a really slow midas today? Is a dir with 4000 files really such a problem to do ls on? Sheesh...
Sofie
participants (5)
-
Joost Van Den Cruyce -
Kenny Billiau -
Michiel Van Bel -
Sebastian Proost -
Sofie Van Landeghem