Just wanted to say thanks to all for responses about the information on
this! Extremely informative and helpful.
Have a great holiday and happy new year!
-Joe
>
thank you this is very useful to know
Mehmet
On Wed, Dec 19, 2018 at 1:46 AM James Bensley wrote:
> Hi Mehmet,
>
> This has been discussed on the Juniper-NSP list several times, here's
> a couple of examples:
>
> https://puck.nether.net/pipermail/juniper-nsp/2018-November/036673.html
> https://
>
>
>
I remember working on a SGI Unix workstation, where you simply could not
specify netmask. It was implicated by the class of address. This meant that
there were only three possible netmasks.
If that was how the first IP implementations started out, we had contiguous
netmasks at the beginning.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You could be sure of two things when there were ambiguities in the routing
tables:
1- Every manufacturer knew how to handle them.
2 - Every manufacturer did it a different way.
I suspect that in most cases where two conflicting route entries existed
On Wed, 19 Dec 2018 21:11:39 +0100, Thomas Bellman said:
> On 2018-12-19 20:47 MET, valdis.kletni...@vt.edu wrote:
> > There was indeed a fairly long stretch of time (until the CIDR RFC came out
> > and
> > specifically said it wasn't at all canon) where we didn't have an RFC that
> > specifically
> On Dec 19, 2018, at 12:11 , Thomas Bellman wrote:
>
> On 2018-12-19 20:47 MET, valdis.kletni...@vt.edu wrote:
>
>> There was indeed a fairly long stretch of time (until the CIDR RFC came out
>> and
>> specifically said it wasn't at all canon) where we didn't have an RFC that
>> specificall
On 2018-12-19 21:28 MET, William Herrin wrote:
> Easy: .97 matches neither one because 64 & 97 !=0 and 32 & 97 != 0.
> That's a 0 that has to match at the end of the 10.20.30.
D'oh! Sorry, I got that wrong. (Trying to battle 10+% packet loss at
home and a just upgraded Thunderbird at the same t
On Wed, Dec 19, 2018 at 12:12 PM Thomas Bellman wrote:
> On 2018-12-19 20:47 MET, valdis.kletni...@vt.edu wrote:
> > There was indeed a fairly long stretch of time (until the CIDR RFC came out
> > and
> > specifically said it wasn't at all canon) where we didn't have an RFC that
> > specifically
On 2018-12-19 20:47 MET, valdis.kletni...@vt.edu wrote:
> There was indeed a fairly long stretch of time (until the CIDR RFC came out
> and
> specifically said it wasn't at all canon) where we didn't have an RFC that
> specifically said that netmask bits had to be contiguous.
How did routers sel
On Tue, 18 Dec 2018 17:12:45 -0500, "David Edelman" said:
> I seem to remember that before the advent of VLSM and CIDR there was no
> requirement for the 1 bits in the netmask to be contiguous with no intervening
> 0 bits and there was always someone who tested it out on a production network
> just
I got to a point a few years ago that anyone who finds my contact info
anywhere on the internet and wants to sell me something is going to spam
me, and there's nothing I can do about it. I just utilize the blocking /
ignore functions of $platform and go about my day.
At one time I did have a devio
Gee... It seems like NTT sales people are not doing a good job as well as Cogent does since I've yet to see anyone getting calls or mails from them. Only Cogent contacts most for the moment, at least in the EU part of the world. And only mails and calls for the moment M. On 19 Dec 2018 21:08, Ross
After setting up my ASN, I received unsolicited emails from NTT and calls
from Cogent. Fortunately I haven't gotten anything (or at least anything
that I noticed) on LinkedIn.
On Wed, Dec 19, 2018, 12:58 PM Brielle Bruns On 12/19/2018 9:58 AM, Rich Kulawiec wrote:
> > On Wed, Dec 19, 2018 at 09:4
Thank you everyone for following up offlist with their feedback and
recommendations. I truly appreciate this. I am creating a FAQ section in
www.networkatlas.org now as it seemed like several areas needed to be
clarified.
What is Network Atlas? it's a very good question and I want to open that
lit
On 12/19/2018 9:58 AM, Rich Kulawiec wrote:
On Wed, Dec 19, 2018 at 09:49:29AM -0700, Brielle Bruns wrote:
Every time I post to NANOG, I get multiple LinkedIn link requests or e-mails
about selling my excess gear. It's getting old real quick.
I recommend:
Connect:linkedin.comERRO
More likely everyone bought IRUs out of the same ILEC’s single cable.
Or they just all go through the same single raceway to enter the building, etc.
-Ben.
- Ben Cannon, AS15206
> On Dec 19, 2018, at 9:41 AM, Rod Beck wrote:
>
> Some of it is due to lazy buyers purchasing two IP ports from di
Some of it is due to lazy buyers purchasing two IP ports from distinct
companies without considring that two ports both located at the site are
vulnerable to shared risers or entrance facilities.
- R.
From: NANOG on behalf of Mike Hammett
Sent: Wednesday, D
The Trans-Atlantic cables, particularly on the UK side, probably lack physical
diversity. The landings at Bude probably share back haul. The cost of each
cable digging its own trench was quite high.
- R.
From: NANOG on behalf of Mehmet Akcin
Sent: Tuesday
On Wed, Dec 19, 2018 at 09:49:29AM -0700, Brielle Bruns wrote:
> Every time I post to NANOG, I get multiple LinkedIn link requests or e-mails
> about selling my excess gear. It's getting old real quick.
I recommend:
Connect:linkedin.comERROR:5.7.1:"550 Mail refused"
From:link
On 12/19/2018 8:53 AM, Kushal wrote:
There are many Tier 1s doing it and they have moved to LinkedIn these
days instead of emails.
Can confirm that one. I've stopped being nice in my responses.
Every time I post to NANOG, I get multiple LinkedIn link requests or
e-mails about selling my exc
>Why do you think the network portion needs to be contiguous?
Just because some equipment at one time let you configure a non-contiguous mask
does not make it correct configuration. Please come up with any valid use case
for a non-contiguous network (note NETWORK, not any other purpose) mask.
Why do you think the network portion needs to be contiguous?
Well, it does now. But that was not always the case.
https://www.quora.com/Why-is-the-subnet-mask-255-255-255-64-invalid/answer/Patrick-W-Gilmore
https://www.quora.com/Why-is-the-subnet-mask-255-255-255-64-invalid
--
TTFN,
patrick
>
Yes, we got data from Jan 1st, 2018 to Oct 10th, 2018. Happy to share as
long as Team Cymru’s is ok with it too!
Ale
Il 2018-12-19 16:35 M. Omer GOLGELI ha scritto:
I think Alessandro Isolario Project may be of help completing the
missing data where you fell short.
M.
---
On 2018-12-19 18:
There are many Tier 1s doing it and they have moved to LinkedIn these days
instead of emails.
--
Kushal R
Chief Executive | Host4Geeks
site: host4geeks.com
email: kusha...@h4g.co
skype: kush.raha
On 19 December 2018 at 8:55:31 PM, Antonios Chariton (daknob@gmail.com
I think Alessandro Isolario Project may be of help completing the
missing data where you fell short.
M.
---
On 2018-12-19 18:07, Alberto Dainotti wrote:
Hi all,
CAIDA has been collecting Team Cymru’s bogon list from 2013-09-18 to
2018-03-23. Unfortunately we just noticed the script hasn’t b
I think Git would be the perfect solution...would definitely appreciate it.
On Tue, Dec 18, 2018 at 12:01 PM Rabbi Rob Thomas wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Dear Tom,
>
> > I wonder if there's value in having the lists that Team Cymru
> > generates auto pushed to
There’s certainly a Tier-1 doing it for RIPE, every time a new AS is registered
for example.. I imagine it’s the same in ARIN too..
> On 19 Dec 2018, at 16:57, John Curran wrote:
>
> On 19 Dec 2018, at 10:41 AM, Izaac wrote:
>>
>> Just a reminder.
>
> Izaac -
>
> Feel free to note that com
On 12/18/18 8:38 PM, Fred Baker wrote:
On Dec 19, 2018, at 3:50 AM, Brian Kantor wrote:
/24 is certainly cleaner than 255.255.255.0.
I seem to remember it was Phil Karn who in the early 80's suggested
that expressing subnet masks as the number of bits from the top end
of the address word was e
Hi all,
CAIDA has been collecting Team Cymru’s bogon list from 2013-09-18 to
2018-03-23. Unfortunately we just noticed the script hasn’t been working since
then but we just fixed it and restarted it.
We’re happy to share the data as long as Team Cymru’s is ok with it.
Cheers,
Alberto
PS
I thin
On 19 Dec 2018, at 10:41 AM, Izaac wrote:
>
> Just a reminder.
Izaac -
Feel free to note that companies involved and forward the message to me…
ARIN does pursue misuse of Whois information for marketing purposes.
Thanks!
/John
John Curran
President and CEO
American Registry for Internet Num
I am wondering how a netmask could be not contiguous when the network portion
of the address must be contiguous. I suppose a bit mask could certainly be
anything you want but a netmask specifically identifies the network portion of
an address.
Steve
> I seem to remember that before the advent
Just a reminder.
Grrr.
--
. ___ ___ . . ___
. \/ |\ |\ \
. _\_ /__ |-\ |-\ \__
If people start spot-checking this stuff more regularly, perhaps the companies
being verified will take delivering the correct product the first time more
seriously.
Some of it boils down to a lack of data quality about what they actually have.
-
Mike Hammett
Intelligent Computing So
On Tuesday, 18 December, 2018 22:43, "Brandon Martin"
said:
> This is a favorite interview type question of mine, but I won't
> disqualify a candidate if they can't come up with the reason. It's more
> of a probe for historical domain knowledge (one of many I'll slip in).
It's an interestin
Hi Mehmet,
This has been discussed on the Juniper-NSP list several times, here's
a couple of examples:
https://puck.nether.net/pipermail/juniper-nsp/2018-November/036673.html
https://puck.nether.net/pipermail/juniper-nsp/2018-April/035397.html
https://puck.nether.net/pipermail/juniper-nsp/2016-Ju
Hello Rob,
IMHO another option is to set up a local BGP daemon (e.g. Quagga,
ICE) peering with your bogon route server project and dump bogon
information regularly in MRT like route collectors are doing. So folks
can select the RIB snapshot they prefer in time and (in case) study the
evolut
36 matches
Mail list logo
