Re: [j-nsp] Urgent

2009-12-17 Thread Masood Shah
Here you go...
 
http://www.juniper.net/techpubs/software/junos/junos91/swconfig-system-basics/configuring-a-dhcp-server.html
 
 



From: juniper-nsp-boun...@puck.nether.net on behalf of chandrasekaran iyer
Sent: Thu 12/17/2009 6:39
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] Urgent



Hi,

How to enable DHCP server in MX240:MX480:MX960 platforms

--
Thanks with regards

Shekar.B
--
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] ad1 msg on Juniper M series

2009-11-04 Thread Masood Shah
TENSION-Not:) The write cache is disabled by default. If you're a Unix guy then 
mpt manpage holds more information.
Just keep in mind that turning the disk's write cache on puts your data at 
risk. :-(

Regards,
Masood



From: juniper-nsp-boun...@puck.nether.net on behalf of Shankar
Sent: Wed 11/4/2009 13:33
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] ad1 msg on Juniper M series



Hi All, Of late I had replaced the Internal compact flash on Juniper M7is
and Juniper 10is. The root is mounted on ad0 (CF), but found that 'write
cache' is disabled on ad1...has anyone seen this before..No impact on box
performance...
truncated o/p of 'show system boot-messaged
sio3 at port 0x2e8-0x2ef irq 7 on isa0
sio3: type 16550A
fxp0: Ethernet address 00:a0:a5:5c:3c:66
fxp1: Ethernet address 02:00:00:00:00:04
DEVFS: ready to run
*ad0: 999MB SILICONSYSTEMS INC 1GB [2030/16/63] at ata0-master PIO4
ad1: found HTS548020M9AT00, disabling write cache
ad1: 19077MB HTS548020M9AT00 [38760/16/63] at ata0-slave UDMA33*
Mounting root from ufs:/dev/ad0s1a

Cheers
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Block traceroute and Allow Ping

2009-09-30 Thread Masood Shah
Truman is correct, blocking traceroute is not straightforward...

To block traceroute on Linux, start by DROPping ports 33434 to 33600. Of 
course, Truman makes a good point that this range can be overridden, for 
example in Linux with the -p option. If you are REALLY paranoid, you can DROP 
all UDP traffic and then only open the ports that you have services running on. 
Sometimes this is easier said than done though.

Windows uses normal ICMP echo requests with low TTL values. And the replies 
are ICMP type 11 (TTL exceeded), or ICMP type 0 (echo reply, when the 
destination has been reached). 

So if you want to block both Windows and *NIX traceroutes, you need to either:
-block outgoing messages destined to UDP ports 33434 to 33534, AND outgoing 
ICMP echo-request messages 
or
-block incoming ICMP type 11 and type 0 messages

To avoid a long discussion on this topic I would add that UNIX version of 
Tracert performs the same function as the Windows version except that the IP 
payload is a UDP packet. According to RFC1393, traceroute implementations are 
supposed to use the ICMP protocol. Indeed, the windows implementation does use 
ICMP. However, by default, the Linux implementation uses UDP, unless you apply 
the -I option, in which case it will use ICMP.

Regards,
Masood
Blog: http://weblogs.com.pk/jahil/



-Original Message-
From: juniper-nsp-boun...@puck.nether.net on behalf of Truman Boyes
Sent: Wed 9/30/2009 10:34
To: Iftikhar Ahmed
Cc: juniper-nsp@puck.nether.net; Pekka Savola
Subject: Re: [j-nsp] Block traceroute and Allow Ping
 
This will block some types of traceroute, but a client can always use  
different ports.

Why do you want to block traceroute?

On 29/09/2009, at 8:42 PM, Iftikhar Ahmed wrote:

 Atif,

 Try to apply a filter to loop-back interface with somthing like


 term traceroute {   /* permit traceroute udp packets */
from {
 protocol udp;
destination-port 33434-33678;
}
then {
 count traceroute;
discard;
}
 term default
 then {
 accept
 }
 }



 Regards,
 iftikhar Ahmed

 On Tue, Sep 29, 2009 at 3:23 PM, Pekka Savola pek...@netcore.fi  
 wrote:

 On Tue, 29 Sep 2009, Muhammad Atif Jauahar wrote:

 I want to block traceroute transit traffic on router but I want to  
 allow
 ping transit traffic. Kindly let me know ICMP Type and Code for  
 traceroute
 and kindly let me know procedure to block traceroute but allow ping.


 You can't if you want to support all flavours of traceroute as some  
 of
 those use the equivalent of ping.  Maybe you could match by both  
 TTL and
 ICMP type/code but that would be hackish.  To learn more about how
 traceroute works, see:

 http://en.wikipedia.org/wiki/Traceroute

 --
 Pekka Savola You each name yourselves king, yet the
 Netcore Oykingdom bleeds.
 Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

 ___
 juniper-nsp mailing list juniper-nsp@puck.nether.net
 https://puck.nether.net/mailman/listinfo/juniper-nsp

 ___
 juniper-nsp mailing list juniper-nsp@puck.nether.net
 https://puck.nether.net/mailman/listinfo/juniper-nsp


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] EX4200 and Broadcom NICs on Linux Server

2009-09-26 Thread Masood Shah
what kind of routing issue this is? 

-Original Message-
From: juniper-nsp-boun...@puck.nether.net on behalf of Shane Ronan
Sent: Sat 9/26/2009 23:54
To: juniper-nsp
Subject: [j-nsp] EX4200 and Broadcom NICs on Linux Server
 
Has any else experienced routing issues with Broadcom NICS on a Linux  
Server connected to an EX4200?


Shane

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] E120 Configure single domain to authenticate from adifferent RADIUS

2009-08-12 Thread Masood Shah
You can use one RADIUS server (cluster as well) for all the domains and decide 
on the RADIUS instead of RAS/BRAS. You can use your primary RADIUS as n proxy 
for particular domain,user,subnet  to redirect/out-source the auth,authrozn,acc 
of dial-in user,realm etc to another RADIUS server, which is more scalable and 
reliable than having a separate server for a specific domain. And this way 
server farm can act as both a primary and backup at the same time.
 
Regards,
Masood
 
 


From: juniper-nsp-boun...@puck.nether.net on behalf of Jason Alex
Sent: Wed 8/12/2009 9:13 AM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] E120 Configure single domain to authenticate from adifferent 
RADIUS



Dear All,
   How can i configure on the E120 Router to make some users with a
specific doman (i.e .com) to authenticate from a different RADIUS
Servers using pppoe other than the RADIUS Server used by all the other users

Appreciate your help

Thanks
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp