There is a number of unauthorize attempts to the Juniper device.
mx>show log messages | match LOGIN_FAILED
There are the following KBs but these for srx, how about ex/qfx and mx?
Any workaround or best practice?
For the qfx/mx device you can use the following method to avoid the ssh/telnet brute force attack. Please refer to the below document
Hope this helps
both KBs also apply to MX and I suppose to all other JUNOS platforms.
When checking those juniper resources, a few questions are caming up...
How can weird people(brute forcers) around the world know my junos devices' management ip addresses? The answer should be a ping sweep, shouldn't be?
How can be hide/not propagate or not annnouced IP addresses that are using for only internal management purpose?
How to verify this brute force attempts or requests are coming to which IP addresses on the Junos devices? I know there is no establishing but I need to know which destionation Ip address is being used by brute forcers?
If your IP management using Public IP then its normal all arround the world know. So the to perevent is just using lo0 filter such as KB mention.
I just checked my tracert to google. In the path we can see lo0 interface with its ip address. Probably lo0 is a router-id or probably it is being using for dynamic routing protocol. So if the Firewall Filter is not applied to this Lo0 interface, will my SSH attemp to this lo0 show a SSH_LOGIN_FAILED in the their message log? If the FF is applied, what might be seen?
Tracing route to dns.google [22.214.171.124]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms Bilolight [10.10.10.1]
2 17 ms 16 ms 26 ms lo0.rras2.sig11.on.ni.net [126.96.36.199]
3 19 ms 19 ms 39 ms l01.tr2.sig10.on.ni.net [188.8.131.52]
4 30 ms 32 ms 37 ms be41.tr2.sig11.on.ni.net [184.108.40.206]
5 28 ms 31 ms 43 ms be45.tr3.sgt2.on.ni.net [220.127.116.11]
6 28 ms 29 ms 30 ms be51.t3.sgt7.on.ni.net [18.104.22.168]
7 36 ms 30 ms 53 ms gw.google.com [22.214.171.124]
8 30 ms 42 ms 30 ms 126.96.36.199
9 30 ms 34 ms 28 ms 188.8.131.52
10 39 ms 29 ms 29 ms dns.google [184.108.40.206]
Other things....The Junos device mx has multiple interfaces and multiple lo(X) logical interfaces. Each traffic on the each interfaces is different as expected.
In windows we can determine which incoming source addresses to which destination address with netstat -a etc.
In Junos cli (including shell) what is the equivalent of windows command of netstat -ona 2 | find "x.x.x.x" | find "22" regartless what interfces might be.?
When you apply the firewall filter for the lo0 interface you apply the filter on the physical interface. So it doesnt matter if there are multiple logical unit associated the filter will work for all the traffic which are attempted towards the lo0.
If you want to find out the source and destination ip address from the brute force attack you may use the "log" option in the firewall filter along with count to determine the source of the brute force attack. However i am not sure if "log" option on loopback works on all the junos devices.
Also when the firewall filter is applied to the lo0 you may not see the SSH_FAILED attempt as it will be dropped before it hits the cpu.
If my answer resolved your queries then please mark it as "accepted solution" so that it can benefit others in the community.