Hi folks,
At $day_job, I have a team of engineers who are oncall for critical
services in the United Kingdom. For $reasons, the national power grid is
announcing the possibility of rolling power cuts over the coming months.
Right now it's "unlikely", but possible. If cuts do happen, it'll be 3
l functionality, behavior and
so on.
Regards,
Israel G. Lugo
On 10/20/2016 07:59 PM, Ken Chase wrote:
> re more general 'network utilities' and scripts:
>
> http://sizone.org/m/hacks/cidrmath.pl
>
> adds and removes subnets from networks giving list of remaining/aggreg
ation", and "this
autodetects your cables, configures your switches and sends a robot to
connect everything".
Thank you and best regards,
Israel G. Lugo
On 02/24/2017 03:58 AM, Hugo Slabbert wrote:
> None of these necessarily get to your ideal state, but at least get
> you going wrt discovery for semi-dynamic documentation.
Thank you for the suggestions.
I've used Netdisco in the past, older 1.x version. It was nice and
useful. I've gone ahead an
That actually seems nice!
I tried a quick demo of the Pro version and it has a distinct DCIM-like
feel. Still not sure it can place things e.g. on a floor plant but
perhaps there's a way to integrate with some API.
The community version does lack multiple useful features, though. I'll
have to try
On 02/24/2017 03:52 AM, Mel Beckman wrote:
> This tool is not cheap, but I believe it can handle all the physical plant
> inventory and provisioning objectives you listed:
>
> http://synchronoss.com/wp-content/uploads/spatialNET.pdf
>
Judging from the description on the PDF, that does seem to be
GTGIIRO
>
> Despite the content is in Brazilian Portuguese, it may work well to
> use Google Translator to read the overview.
>
> The software developed was funded by the Brazilian NREN. The software
> is maintained by a team of research and development.
>
> Alex
>
&g
P, via AS6453 (Globe) -> AS1299 (Telia) works fine.
Regards,
Israel G. Lugo
.
Regards,
Israel G. Lugo
On 05/02/2013 07:08 PM, Grant Ridder wrote:
> Looks like ge-2-5.br1-knams.wikimedia.org (130.244.6.250) is filtering you
> somehow.
>
> Grant
>
> Sent from my iPhone
>
> On May 2, 2013, at 9:01 AM, "Israel G. Lugo" wrote:
>
>&
Likewise, working here.
$ dig +trace www.facebook.com
; <<>> DiG 9.7.0-P1 <<>> +trace www.facebook.com
;; global options: +cmd
. 240259 IN NS b.root-servers.net.
. 240259 IN NS g.root-servers.net.
. 240259 IN
, so default traceroute may not be indicative.
To better replicate the problem, you can tell traceroute to send TCP
SYNs to the specific port you're trying to reach (443). Run this as root
(it needs raw sockets):
# traceroute -M tcp -p 443 dropbox.com
Regards,
Israel G. Lugo
to start an argument on
whether A is better than B, nor do I believe that to be the site's
purpose. Rather, I would like to divulge and hopefully incite some
productive discussion.
Regards,
Israel G. Lugo
I was actually not aware of this. I've been told that systemd also
includes fsck's functionality (or is planning to?). That just seems
absurd to me.
I didn't really have a strong opinion on either side of this yet. Seeing
the replies from other people here, though, and reading some more about
it,
On 10/21/2014 11:55 PM, Jay Ashworth wrote:
> - Original Message -
>> From: "Capi"
Whoops, used the wrong alias to reply.
>> Not *every single* distribution...
> I had meant to put an asterisk on that.
My remark was meant to be tongue-in-cheek :)
> Ok, but how does it handle providi
On 10/21/2014 11:59 PM, Tom Hill wrote:
> On 21/10/14 23:55, Jay Ashworth wrote:
>> Ok, but how does it handle providing initscripts? I gather any upstreams
>> which used to provide them aren't anymore...
> It's Gentoo: "You should write your own" is the most likely answer.
Actually, not at all;
On 22-10-2014 17:12, Miles Fidelman wrote:
> Seems to me, this has been a very rational discussion, confined to one
> very identifiable thread, containing what at least this reader finds
> very useful (operational impacts of systemd in server-side
> environments, and what alternatives people are lo
On 22-10-2014 17:30, Jeffrey Ollie wrote:
> Hardly. The discussion so far has been weighted very heavily on the
> side of Dana Carvey's "Grumpy Old Man"-style whining. "That's the way
> it was and we liked it!". The people that like systemd (like myself)
> have wisely learned that the people that h
On 10/23/2014 12:05 AM, Jeffrey Ollie wrote:
> systemd is a tool designed to get the system to a state where "real
> work" can be done. NTP servers, DHCP clients, consoles, aren't the
> real work of a system, or at least I hope not, because that would be
> boring to me.
That idea sounds interes
Old days... :)
http://www.snotr.com/video/14338/In_Honor_Of_The_Internet_Turning_45_Today__Here_Is_Its_First_Router
Hello,
Was down in Portugal until just now, and from downforeveryoneorjustme.com.
Just tried and it seems to be working again, though.
On 09/28/2015 09:39 PM, Raymond Dijkxhoorn wrote:
> Hai Marco,
>
> Same in NL so most likely bigger then Italy alone.
>
> Thanks,
> Raymond Dijkxhoorn, Proloc
think IPv6 should've been at least 192 bits long.
Israel G. Lugo
ng to catch a bug from some weird packets thrown
at it.
Thank you for reading. Regards,
Israel G. Lugo
+1 for BIRD.
Basically, what you want is to have several different static (blackhole)
routes, and be able to differenciate them at BGP level, for marking with
communities, etc. Correct?
This is easy with BIRD. Just use separate instances of the "static"
protocol, and filter using "proto" to disti
On 07/02/2015 04:23 AM, Israel G. Lugo wrote:
> protocol static temp_block {
> # DDOS mitigation, etc
> route 203.0.113.17/32 blackhole;
> }
Didn't make it clear in my example, but you can obviously have multiple
routes in a static instance:
protocol static temp_block {
r
ving addresses to spare, if it just means
you've got to start worrying about subnet scarcity? If the goal was
never having to worry about counting anymore, I propose that 128 bits is
far too little. Should've gone a full 256 and be done with it.
Regards,
Israel G. Lugo
P.S.: I'm 100% for IPv6 and $dayjob has been fully dual stacked for 10
years now.
On 07/09/2015 12:59 AM, Mark Andrews wrote:
> In message <559db604.8060...@lugosys.com>, "Israel G. Lugo" writes:
>> Doesn't seem to make sense at all for the ISP side, though. Standard
>> allocation /32. Giving out /48s. Even if we leave out proper subne
On 07/09/2015 02:15 AM, Owen DeLong wrote:
> If you’re trying to build a decent sized ISP in a /32, you’re doing it
> wrong. /32 is not the “standard size” — It’s the MINIMUM size.
I've addressed this and most of what you said in my earlier reply to
Mike Hammet (00:57:29 UTC). I was going to rep
On 07/09/2015 02:38 AM, Mark Andrews wrote:
> A single /48 has enough space/subnets cover the entire infrastructure
> of 99.% of ISPs even using /64's for p2p links rather than taking
> one /64 and subdividing that for all of the p2p links. Treat the ISP
> as a business customer of itself when
On 07/09/2015 02:31 AM, Owen DeLong wrote:
> Here’s the problem… You started at the wrong end and worked in the wrong
> direction in your planning.
>
> [...get larger allocation...]
>
> We are now left with only 1,041,888 /20s remaining. You still haven’t put a
> dent in it.
I am aware of the
I'm sorry Mel, I only now saw your email.
I'll quote from my reply to Owen, for the motivation behind my question:
> Speaking of IPv6's full potential: we're considering 32 subscriptions
> per client. I've read people thinking of things like IPv6-aware soda
> cans. Refrigerators. Wearables. Cars
30 matches
Mail list logo
