Re: [j-nsp] What do for a terminal server?

MrPaul wrote: > On 6/25/07, *Leigh Porter* <[EMAIL PROTECTED] > > wrote: > > > Thats nice. Now what I would like next is for it to run `screen` > on each > RS232 port. The I can log in and see what happened and scroll back > a few > k lines. > > > Then

Re: [j-nsp] juniper-nsp Digest, Vol 55, Issue 33

consider using another term... term allow-established { from { tcp-established; } then accept; } -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Ball Sent: Wednesday, June 27, 2007 3:42 PM To: Kanagaraj Krishna Cc: juniper-nsp@p

Re: [j-nsp] What do for a terminal server?

On 6/25/07, Leigh Porter <[EMAIL PROTECTED]> wrote: > > > Thats nice. Now what I would like next is for it to run `screen` on each > RS232 port. The I can log in and see what happened and scroll back a few > k lines. Then telnet to a *nix server, run screen, then telnet to your terminal server co

Re: [j-nsp] juniper-nsp Digest, Vol 55, Issue 33

Perhaps I'm missing something obvious here(it wouldn't be the first time), but telnet is a tcp application and thus has to communicate in both directions regardless of the port involved. If you're blocking tcp on any non-telnet port(including port 80), I would imagine it's being discarded on the w

Re: [j-nsp] juniper-nsp Digest, Vol 55, Issue 33

It very likely IS allowing OUTgoing telnet, even without the adjustment in your filter. The problem is, it's not allowing the response from the (assumed) web server in the INbound direction, hence your need for the allowance in your input filter. David On 6/27/07, Kanagaraj Krishna <[EMAIL P

[j-nsp] Juniper M20 SSB board memory type

Hi there, Can anybody confirm memory type for Juniper M20 SSB board? Is that PC133/100 non-buffered ECC SODIMM(144pin) ? Hyun Hyunseog Ryu Senior Network Engineer Norlight Telecommunications, Inc./Applications Engineering 13935 Bishops Drive Brookfield, WI 53005 Phone. +1-262-792-7965 Fax. +1-

Re: [j-nsp] juniper-nsp Digest, Vol 55, Issue 33

Hi, I've applied an input filter (hardening) to protect the routing engine of an m7i by applying it on the loopback IP. Refer to the config below. The issue is that, we can't telnet port:80 to any external IP from the box itself. Obviously I've not allowed access to port 80 on my box in the i

[j-nsp] Ratelimiting ARP-Requests

Dear colleagues, I'm looking for an advice about the possibilities to ratelimit incomming ARP requests. What's the correct syntax for an effective filter rule to solve this problem ? Kind Regards Jens ___ juniper-nsp mailing list juniper-nsp@puck.n

Re: [j-nsp] MAC table size experience w/VPLS

Hello all, I have a M320 in production and around 7800 entries in its MAC address table. I am not sure if this is the right command to type in but here is its current memory state. However, I couldn't tell you in which type of memory the router stores this MAC address table. [EMAIL PROTECTED]

Re: [j-nsp] bgp.l3vpn tables

I guess it would depend on memory. I'm importing the global routing table into an L3VPN with no issues, but it's on a T640 with 2GB. You might look into the 'keep' command as well though, to dictate whether or not unused routes are kept around or not after learning them from a peer. David On

[j-nsp] bgp.l3vpn tables

any thoughts on impact of importing 1000s of routes learned from an eigrp network into a vrf. would route summarization be a better option. to restrict the number of entities in the bgp.l3vpn table. ___ juniper-nsp mailing list juniper-nsp@puck.nether

[j-nsp] MAC table size experience w/VPLS

I have 5 x T640s running JunOS 8.2 and am adding some 10/100 aggregation switches. These switches would be in a ring (say, 3 of them per ring) and 2 of those switches would have gig uplinks to different T640s. The switches would run a version of spanning tree (likely RSTP, unless they can do PV

Re: [j-nsp] Usage of Route distinguisher in VPLS

Suppose multiple sites end up using the same Site-id (VE-id) but participate in different VPLSs(differnent RTs) then RD will help distinguishing the layer-2 bgp-nlri for the layer2-routes for these sites. Isn't it? Else (if RD is same or non-existent), advertisement for one site will mask the othe

Re: [j-nsp] Usage of Route distinguisher in VPLS

Thanks for the reply. As per section 3.1.2, Route target only identifies the VPLS. Even in Juniper, if I have a configuration like this, root# show routing-instances vplsinst2 { instance-type vpls; route-distinguisher 100:4; vrf-target { import target:100:3; export targ

Re: [j-nsp] Usage of Route distinguisher in VPLS

Hi Monika On 27/06/07, Guy Davies <[EMAIL PROTECTED]> wrote: > Hi Monika, > > I haven't played around much with VPLS but a quick read of RFC 4761 > reveals the following... > > Section 3.5 of RFC 4761 appears to be the key. It refers to > multihoming mechanisms for VPLS and states the following..

Re: [j-nsp] Usage of Route distinguisher in VPLS

Hi Monika, I haven't played around much with VPLS but a quick read of RFC 4761 reveals the following... Section 3.5 of RFC 4761 appears to be the key. It refers to multihoming mechanisms for VPLS and states the following... In the case where the PEs connected to the same site are assigned th