hello,
i am interested in peoples recommendations for mpls vpn and te provisioning
tools. whatever it is it must support or be extendable to support cisco and
juniper hardware and software.
i'm particularly interested in home-grown and publicly available tools,
especially open source. i'd be qu
you may want to check out DPS's IAM product. We use it and it's been
reliable.
They have also been willing to customize things for us in the past-
http://dpstele.com/
Regards, Keith
-Original Message-
From: Allan Liska [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2003 5:46
We have just released a new version of the scanner that has addressed
some reporting inaccuracies. We have also included a MD5 checksum. It
is available here:
http://www.iss.net/support/product_utilities/Xfrpcss.php
Regards,
===
Daniel Ingevaldson
Engineering Manage
-BEGIN PGP SIGNED MESSAGE-
Hash: MD5
Hello Jeffrey,
Thursday, September 11, 2003, 5:50:40 PM, you wrote:
JM> I may be missing something, but don't monitoring systems (ie, Nagios)
JM> have the built-in ability to send out pages w/ a locally attached modem,
JM> or SMS (if you setup an ema
Alan,
Try QPAGE.
ciao.
Shon Elliott
Systems Engineer;
OptiGate Networks, Inc.
Allan Liska wrote:
I am looking for a hardware/software solution to a problem and I am
hoping someone has implemented something similar:
A monitoring system notices an error and sends an alert to a system (the
alert
> Even if a switch floods all ports, it does not change the fact the packet
> will not have the correct MAC address and his NIC should never pass it
> up the stack. Switches do not rewrite the Ethernet addresses on packets.
Correct, ethernet switches do not. The question is, what were the system
Gregory Hicks wrote:
>
> > Date: Thu, 11 Sep 2003 13:35:37 -0700
> > From: Crist Clark <[EMAIL PROTECTED]>
> >
> > Mike Lewinski wrote:
> > >
> [...snip...]
> > OS's IP stack is misbehaving badly, Zone Alarm should not see the traffic
> > on the LAN that does not have his MAC address on it.
> >
>
I am looking for a hardware/software solution to a problem and I am
hoping someone has implemented something similar:
A monitoring system notices an error and sends an alert to a system (the
alert can be sent over POTS or SMTP). The system recevies the alert and
sends out a message (Pager/PO
> Date: Thu, 11 Sep 2003 13:35:37 -0700
> From: Crist Clark <[EMAIL PROTECTED]>
>
> Mike Lewinski wrote:
> >
[...snip...]
> OS's IP stack is misbehaving badly, Zone Alarm should not see the traffic
> on the LAN that does not have his MAC address on it.
>
> How would a switch/router be deciding
Mike Lewinski wrote:
>
> Christopher Bird wrote:
>
> > This seems strange to me since they are arriving at an IP address that
> > is different from mine.
>
> That's the function of a hub, and the reason why you don't ever want to
> send out sensitive information in plaintext. Your neighbor in t
Richard Cox wrote:
The other good news is that all those blocks have now been either
returned to Aker Kvaerner Group (successors-in-title to Trafalgar
House Group) or returned to ARIN for reuse, as appropriate. Any
filters you routing people may have put in place to prevent abuse
from those bloc
On Thu, 11 Sep 2003, Kai Schlichting wrote:
> AT&T, for lack of presenting any TRO forcing them to keep routing this,
> appears to willingly conspire with the Empire Towers IP space hijackers
> while presented with overwhelming evidence that whatever forged documents
> Empire Towers and Thomas Cow
On Thu, 11 Sep 2003 16:32 UTC John Payne <[EMAIL PROTECTED]> wrote:
| I stopped seeing 157.112.0.0/16 announced via AT&T earlier this week.
So did many people. That route came back again soon afterwards.
I have received an assurance directly from senior AT&T management that
the route has - in
On Thu, Sep 11, 2003 at 12:32:58PM -0400, John Payne wrote:
> --On Thursday, September 11, 2003 11:52 AM -0400 Kai Schlichting
> <[EMAIL PROTECTED]> wrote:
>> From the [Hijacked] list:
>>> The ARIN information has been updated to have up-to-date contact info for
>>> the original owner, the ori
--On Thursday, September 11, 2003 11:52 AM -0400 Kai Schlichting
<[EMAIL PROTECTED]> wrote:
From the [Hijacked] list:
The ARIN information has been updated to have up-to-date contact info for
the original owner, the original owners' ISP is announcing 4 /18s but
AT&T is still announcing 157.112
>From the [Hijacked] list:
> The ARIN information has been updated to have up-to-date contact info for
> the original owner, the original owners' ISP is announcing 4 /18s but AT&T
> is still announcing 157.112.0.0/16. Can whoever's been bugging AT&T to stop
> announcing it to bug them some more?
Christopher Bird wrote:
This seems strange to me since they are arriving at an IP address that
is different from mine.
That's the function of a hub, and the reason why you don't ever want to
send out sensitive information in plaintext. Your neighbor in the next
room over could run a packet snif
Please see our X-Force Alert for more information about the new set of
MSRPC issues. We have published a free CLI tool to scan for computers
vulnerable to MS03-039.
X-Force Alert:
http://xforce.iss.net/xforce/alerts/id/152
Free Scanner:
http://www.iss.net/support/product_utilities/Xfrpcss.php
Whoa stop press! You connected a computer to a public IP and zone alarm starts
buzzing away.. FBI!
Depends on how the hotel system works, it may be broadcasting or doing some
other IP weirdness, either way its not surprising.
But there is no security threat from some left over packets from o
Hi,
we've seen this.. yuo need to make sure you filter the nachi worm 92 byte icmp
echo's on your interfaces and it will be fine. The problem seems to be input
buffers which use all the memory up for some reason.
Steve
On Wed, 10 Sep 2003, Richard J.Sears wrote:
>
> Hey Everyone -
>
> We ha
Hello all-
We are trying to move all of our DSL aggregation off of a Redback SMS1000
to a Cisco 7513. We are using the PA-A3-T3 card on the Cisco to talk to
our DSL subscribers. We are currently running rfc1483 routed and bridged
customers on the same ATM DS3 on the Redback. We're trying to fig
21 matches
Mail list logo