> wee! and for some extra fun, just append the bad-guy's ASN to your
> route announcements, force bgp loop-detection to kill the traffic on
> their end (presuming they don't default-route as well)
Even more fun if you are not the only one filtering that ASN. :)
Andras
> At Inter.Net, we specifically excluded .0 and .255 from our DSL pools
> so as to not screw up the day of people running outdated Windows
> software any more than it was already screwed up.
According to Microsoft KB 281507
http://support.microsoft.com/default.aspx?scid=kb;en-us;281579
even "XP
> But even in 2000 the policy was and still is:
> /128 for really a single device
> /64 if you know for sure that only one single subnet will
> ever be allocated.
> /48 for every other case (smart bet, should be used per default)
I believe this policy is changing. The new text is: "End
> > > doesn't more address space just give us more routes to handle?
> >
> > No. It only makes more possible prefixes. Migrating to IPv6 while keeping
> > the current (IPv4) routing and current business relations, there would be
> > somewhat less routes:
> >
> > bigger address space -> bigger
> doesn't more address space just give us more routes to handle?
No. It only makes more possible prefixes. Migrating to IPv6 while keeping
the current (IPv4) routing and current business relations, there would be
somewhat less routes:
bigger address space -> bigger chunks -> less need to incre
Fred, Brandon, Spiro,
Thanks for all your answers.
> operating system called NextStep. It sounds like they came up with a variety
> of site-local address pre-RFC1918 and pre-RFC3927 that did something similar
> to RFC 3927 addresses.
That's it. 192.42.172.0/24 is often used in examples, but I
Hi,
Could someone please tell me what 192.42.172.0/24 is or why it should be
handled as a special prefix?
ftp://ftp-eng.cisco.com/cons/isp/security/Ingress-Prefix-Filter-Templates/T-ip-prefix-filter-ingress-strict-check-v18.txt
Thanks,
Andras
> break. It seems like an IPv6-only ISP would need to operate the NAT-PT
> boxes, and dedicate a block of v4 addresses the size of the expected
> concurrent online users to the NAT-PT box. Keep in mind that a v6 ISP
> with 1 million customers won't need a million v4 addresses, for obvious
> reas
> ;. IN NS
> A.ROOT-SERVERS.NET. 360 IN A 198.41.0.4
> B.ROOT-SERVERS.NET. 360 IN A 192.228.79.201
> C.ROOT-SERVERS.NET. 360 IN A 192.33.4.12
> D.ROOT-SERVERS.NET. 360 IN A 128.8.10.90
> E
Philip,
> I have an east coast and west coast data center connected with a DS3. I
> am running into issues with streaming data via TCP and was wondering
> besides hardware acceleration, is there any options at increasing
> throughput and maximizing the bandwidth? How can I overcome the TCP
>
Jeff,
> I am trying to find an IPv6 subnet calculator or even a "cheat sheet" that
> will help show how a /32 allocation is broken down into /40, /48 and /64
I guess that you don't even need a cheat sheet for that. All the prefix
lengths you mention are multiples of four, which means they're on
Hello,
> I've pretty much always assumed that what a switch
> reported as a status regarding the link of a node was the
> actual status of the line to be the case. However, when I
I think that there is no such thing as "the actual status of the line".
Each end of the cable has a status, either
> > Has anyone used /31 mask addresses on their network?
>
> Yes, works fine (on an all Cisco network).
Maybe not interesting for an ISP, but I'm using it on a vlan interface on
a 6500/7600. It works fine with IOS 12.1.8-EX5, but 12.1.11-E1 refused the
configuration because it's not a p2p interf
Hello,
A bit off-topic and maybe stupid question:
I was told yesterday, that a Hungarian telco/ISP is experimenting with
EDFAs. My friend said that the box looks like if they just brought it from
a research lab (however it's a commercial product). How common is it
nowadays to use EDFAs in ISP
14 matches
Mail list logo
