Alexander Arseniev writes:
>Someone is brute-forcing Your router password, and that is very common
>nowadays. Good loopback filter would prevent this.
Amen to this and all your other points, esp re: avoiding telnet in
favor of ssh.
Also you can use "system services ssh no-passwords;" to prevent
Hello,
What happens if You configure "inline-jflow source-address 2.2.2.2"
instead of 1.1.1.1?
I bet Your jflow source IP would become 2.2.2.2 and since 2.2.2.2 exists
in the LS LAB, your collector can recognise these packets carry tfc
stats from LS LAB.
By the same token, You have to
Hi Aaron,
When a telnet session is established, the process is not a telnetd dameon
after the process pass to cli process. You should be filter with grep
comand looking for "cli". Check my example:
***
tecnologia@MX240-2_LAB-RE0> show
Always a good reference:
http://www.team-cymru.org/templates.html
http://www.cymru.com/gillsr/documents/junos-template.pdf
--
Hugo Slabbert | email, xmpp/jabber: h...@slabnet.com
pgp key: B178313E | also on Signal
On Thu 2016-Nov-24 11:07:45 +, Alexander Arseniev
Hello,
Someone is brute-forcing Your router password, and that is very common
nowadays. Good loopback filter would prevent this.
In addition:
1/ You can only do "request system logout" for sessions that passed
authentication+login+got TTY assigned. If You see "unsuccessful login"
it means
5 matches
Mail list logo
