William Waites writes:
> Is this a good or a bad thing? I can remember back when there was a
> project in the 'states called Carnivore, and we had some American
> police -- I believe they were FBI -- come up and ask us politely if
> we'd like to put some of their machines on our network. Everybo
William Herrin writes:
> IPv4 jumped from 8 bits to 32 bits. Which when you think about it is
> the same ratio as jumping from 32 bits to 128 bits.
Sorry for the late reply, Bill, but you were snoozing when they taught
logarithms in high school weren't you?
Jumping from 8 bits to 32 bits (1:16
Ray Soucy writes:
> Pricing just popped up for the new EdgeRouter PRO last night and I was
> pretty blown away:
>
> $360
>
> For a device with 2 SFP ports, and 2M PPS. That is music to my ears since
> we do a lot of dark fiber around the state even for smaller locations. I'm
> pretty excited t
Ray Soucy writes:
> Can confirm the current ER Lite is a plastic enclosure.
I got mine almost a year ago, and mine is plastic too.
> But for $ 100 I can definitely look past that.
Likewise.
> I believe the chips they use are from Cavium [1], but I could be mistaken.
The bootloader output ag
I'd like to call everyone's attention to ARIN's policy on IPv6
transition space https://www.arin.net/policy/nrpm.html#six531 which
was created specifically in response to the standardization of 6rd.
The discussion at the time that this policy was under consideration
was that encoding the [m,n] in
jean-francois.tremblay...@videotron.com writes:
> Offering /48s out of a single /16 block, to take a simple example,
> would use a whole /32.
Sounds as if your organization can justify more than the /32
"minimum/default" allocation of IPv6 then (I'd imagine you have more
than a minimum-assignme
Matthew Petach writes:
> Using a 1/10th of a second interval is rather anti-social.
> I know we rate-limit ICMP traffic down, and such a
> short interval would be detected as attack traffic,
> and treated as such.
This should be obvious to everyone here but just in case, there's also
a huge dif
jean-francois.tremblay...@videotron.com writes:
>> IPv4-thinking. In the fullness of time this line of reasoning [...]
>
> Hopefully, the fullness of time won't apply to 6RD (this is what
> was being discussed here, not dual-stack).
I agree but there's a subtlety here - we don't want to get peo
"Ricky Beam" writes:
> On Fri, 29 Nov 2013 08:39:59 -0500, Rob Seastrom wrote:
>> So there really is no excuse on AT&T's part for the /60s on uverse 6rd...
> ...
> Handing out /56's like Pez is just wasting address space -- someone
> *is* payi
Cutler James R writes:
> Does this mean we can all get back to solving real IPv6 deployment and
> operations problems?
I sure hope so. :)
> I certainly hope you all can finally see which is the better business choice
> between:
>
> 1. Using up to around 10% of IPv6 space to make our netwo
Brian Dickson writes:
> Rob Seastrom wrote:
>
>> "Ricky Beam" > gmail.com<http://mailman.nanog.org/mailman/listinfo/nanog>>
>> writes:
>> >
>> * On Fri, 29 Nov 2013 08:39:59 -0500, Rob Seastrom > <http://mailman.nanog.org/mailman/lis
Eric Oosting writes:
> It brings a tear to my eye that it takes:
>
> 0) A long standing and well informed internet technologist;
> 1) specific, and potentially high end, CPE for the res;
> 2) specific and custom firmware, unsupported by CPE manufacturer ... or
> anyone;
> 3) hand installing seve
Justin Wilson writes:
> The biggest problem with Mikrotik is you just can¹t call them up for
> support on buggy code. In a critical network this can be a major problem.
I've contacted them (via email) and the experience seems to be exactly
the same as dealing with first level TAC at the b
from speccing their kit when the task
calls for something that's surprisingly good considering how
inexpensive it is! So maybe from a business perspective they were
entirely correct to blow me off - at least where it comes to "revenue
attributable to Rob Seastrom", the negative impact has been nil.
-r
101 - 114 of 114 matches
Mail list logo
