> Sending 5, 100-byte ICMP Echos to 10.1.4.81, timeout is 2 seconds:
> IPSEC(crypto_map_check)-3: Looking for crypto map matching 5-tuple:
> Prot=1, saddr=10.20.1.2, sport=29733, daddr=10.1.4.81, dport=29733
> IPSEC(crypto_map_check)-5: Checking crypto map CARIBOU-VPN-1 10:
skipping
> incomplete m
This report has been generated at Fri Jul 8 21:12:24 2011 AEST.
The report analyses the BGP Routing Table of AS2.0 router
and generates a report on aggregation potential within the table.
Check http://www.cidr-report.org for a current version of this report.
Recent Table History
Date
BGP Update Report
Interval: 30-Jun-11 -to- 07-Jul-11 (7 days)
Observation Point: BGP Peering with AS131072
TOP 20 Unstable Origin AS
Rank ASNUpds % Upds/PfxAS-Name
1 - AS17974 38582 2.8% 21.6 -- TELKOMNET-AS2-AP PT
Telekomunikasi Indonesia
2 - AS9829
On Jul 7, 2011, at 1:20 PM, Jared Mauch wrote:
> 2) is a mapped-v4 address a valid *source* address on the wire even if it's
> not a valid dest?
The world is split on that and why wouldn't it in theory be a valid dest?
It would be easier if this had made it past draft state:
http://tools.ietf.o
On Fri, Jul 08, 2011 at 10:21:13PM +0200, Florian Weimer wrote:
> * Jared Mauch:
>
> > 2) is a mapped-v4 address a valid *source* address on the wire even if it's
> > not a valid dest?
>
> By the way, has the analogous issue involving v4 addresses from
> RFC 1918 space ever been settled?
define
* Jared Mauch:
> 2) is a mapped-v4 address a valid *source* address on the wire even if it's
> not a valid dest?
By the way, has the analogous issue involving v4 addresses from
RFC 1918 space ever been settled?
Hello All,
I have been working for two days trying to get an ASA to setup
a VPN tunnel to a SSG-550. I have the VPN tunnel Setup and ready to go on the
ASA. I ran a Debug crypto IPSec 200 and crypto ikve1 200. I do the command
ping PRIVATE and I get in the console
Sending
This is an automated weekly mailing describing the state of the Internet
Routing Table as seen from APNIC's router in Japan.
The posting is sent to APOPS, NANOG, AfNOG, AusNOG, SANOG, PacNOG, LacNOG,
CaribNOG and the RIPE Routing Working Group.
Daily listings are sent to bgp-st...@lists.apnic.net
On 07/08/2011 01:23 PM, Seth Mattinen wrote:
On 7/8/11 9:04 AM, Michael K. Smith - Adhost wrote:
Hello Everyone
We are going to be moving the NANOG mailing list over to our new service
provider beginning this week. There are several changes that will occur over
time that will, hopefully, red
On 7/8/11 9:04 AM, Michael K. Smith - Adhost wrote:
> Hello Everyone
>
> We are going to be moving the NANOG mailing list over to our new service
> provider beginning this week. There are several changes that will occur over
> time that will, hopefully, reduce the service impact to users. One
Hello Everyone
We are going to be moving the NANOG mailing list over to our new service
provider beginning this week. There are several changes that will occur over
time that will, hopefully, reduce the service impact to users. One key note -
the new system doesn't use Mailman, so your filter
11 matches
Mail list logo