Re: [j-nsp] Juniper UDP Amplification Attack - UDP port 111 ?

Yeah, not on the hypervisor. Im SR-IOV'ing that interface via an Intel 82599-based 10G port into vMX in RIOT-PERF mode The hypervisor can't see the NIC interface at that point (due to PCIe-passthrough). Anyways - as mentioned, I'll re-write my lo0.0 for "accept-useful-stuff-and-deny-all-else"

Re: [j-nsp] Juniper UDP Amplification Attack - UDP port 111 ?

On 16 Mar 2018, at 8:59, Chris Kawchuk wrote: Just a heads up; I'm probably not the first person to see this-- This is rpcbind/portmapper, FYI, which is often abused for reflection/amplification attacks. I'm assuming vMX is a virtual MX - if so, are you sure the issue isn't on the

[j-nsp] Juniper UDP Amplification Attack - UDP port 111 ?

Just noticed this today: chr...@vmx1.mel-lab1> monitor traffic interface xe-0/0/0 no-resolve size 1500 matching "not port 22" verbose output suppressed, use or for full protocol decode Address resolution is OFF. Listening on ge-0/0/0, capture size 1500 bytes 01:50:20.710920 In IP

Re: [j-nsp] Does Junos cli support colors?

Hi Martin, not exactly what you need, but if you use MacOS with iterm, you can use regex to colorize your output. I colorzied up and down interface status in a very basic way: https://abload.de/img/bildschirmfoto2018-03j4ov6.png Regards Alex Martin T schrieb: >Hi! >

[j-nsp] Does Junos cli support colors?

Hi! When I start an ash shell and use terminal escape codes, then string "Hello" is printed in red as expected: user@vMX> start shell sh $ echo $TERM screen $ echo -e "\e[31mHello\e[0m" Hello $ Is it possible to print colors in Junos cli? My cli terminal type is also "screen" according to "show

Re: [j-nsp] predicates in if statement expression in SLAX

Phil, thank you for confirming this! Martin On Wed, Mar 14, 2018 at 10:52 PM, Phil Shafer wrote: > Martin T writes: >>Is there a difference between following two if statement expressions: >>if ($node-set/foo/bar == "klm") { >>..and: >>if ($node-set[foo/bar == "klm"]) { > >