Syngenta space

Hi,

sorry for the noise, but my contact at Syngenta says
they have 147.0.0.0/8 168.0.0.0/8 and 172.0.0.0/8,
which is obviously bogus. They do have a 168.246.0.0/16
however.

Any tool to look the other two up quickly, without having to
iterate through the entire second octet? Thanks!

I just scraped the BGP output from one of my border routers and came up with discrete more specific routes and AS's in all three blocks. Given that Sygenta doesn't appear to have an AS, we can assume they are not amongst them.

Regards,

Mike

sorry for the noise, but my contact at Syngenta says
they have 147.0.0.0/8 168.0.0.0/8 and 172.0.0.0/8,

and pigs fly

indeed, an impressive claim, how much for it all?

sorry for the noise, but my contact at Syngenta says
they have 147.0.0.0/8 168.0.0.0/8 and 172.0.0.0/8,

and pigs fly

indeed, an impressive claim, how much for it all?

i am particularly impressed by the annexation of some of the rfc1918
space.

randy

*checks pockets*

$5 and some lint?

Ill throw in 10.0.0.0 /8 for just the lint, but it better be really good
lint

You can make almost anything fly if you put enough oomph behind it..

/me pops open the kevlar umbrella

(thanks for the warning!)

Only if they're RFC1925 compliant. :slight_smile:

sorry for the noise, but my contact at Syngenta says
they have 147.0.0.0/8 168.0.0.0/8 and 172.0.0.0/8,

Bugger. Now I have to renumber out of my 172.16/12 subnets :frowning:

23173jjaeggli:~ jjaeggli$ ssh rviews@route-views.routeviews.org

route-views> show bgp ipv4 unicast 147.0.0.0/8 longer-prefixes

...

route-views>show bgp ipv4 unicast 168.246.0.0/16 longer-prefixes

route-views>

Well, sometimes they do.

http://wardsci.com/product.asp_Q_pn_E_IG0035229

[Flying Pig: Unforgettable Fun with Physics]

And to think, Google manages to get by with the equivalents of a few /
16 or smaller.

and pigs fly

Well, sometimes they do.

There underlying problem here is flying sheep:

   http://www.youtube.com/watch?v=Vkw2DdoskPY

Note the accurate summarization of the entire issue.

Yes that's it. 172/8 is nesting. Perhaps if 172/8 and 168/8 get together and mate they will produce lots of little /16s and ....

We won't have to implement IPv6 What a MASSIVE time savings. VACATION
HERE I COME!

Sometimes with alternate propulsion:

http://img24.imagevenue.com/img.php?loc=loc188&image=ab44c_incroyable.jpg