[j-nsp] Protect router from ssh/telnet DDOS attacks, or unauthorised access.

Hi there, What I want to do is very simple and I am sure everyone has his/her own solution already. I want to limit SSH/Telnet to the router from restricted management ranges in the global inet.0 table, and do not want customers in their separate routing instances from being able to SSH/Telnet

Re: [j-nsp] EX3200 Power supplies

On 26/07/13 01:52, Doug McIntyre wrote: On Thu, Jul 25, 2013 at 09:01:15AM -0400, Paulhamus, Jon wrote: Power Supply in EX3200 Switches The power supply in EX3200 switches is a hot-removable and hot-insertable field-replaceable unit (FRU) that you can install on the rear panel without

Re: [j-nsp] Protect router from ssh/telnet DDOS attacks, or unauthorised access.

What I do is limit the ability to SSH in via certain interfaces only. i.e. create an interface-set which allows SSH, as long as it comes in on certain interfaces (fxp0, one or two transit interfaces) Any subinterface pointing towards a customer is not added to the list, and hence any

[j-nsp] JUNOS CLI

People, When you start using configuration mode on JUNOS it shows the following output: user@ROUTER# set ? Possible completions: access Network access configuration access-profile Access profile for this instance accounting-options Accounting data configuration

Re: [j-nsp] JUNOS CLI

From the JNCIA study guide When you examine the output closely, you might notice that some command options are pre- ceded with a character—either an angle bracket () or a plus sign (+). These characters, as well as their absence, carry a special meaning when you use the set command. The angle