who_is_using_this_ip_address
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| who_is_using_this_ip_address [2014/02/08 22:47] – [2.2- Riswhois Server] samer | who_is_using_this_ip_address [2014/02/09 00:23] – [2.2- Riswhois Server] samer | ||
|---|---|---|---|
| Line 68: | Line 68: | ||
| ==== -- Riswhois Server ==== | ==== -- Riswhois Server ==== | ||
| - | RIPE NCC implements a similar whois service named RISwhois by providing a higher level view over the most recently collected set of routing tables from the Remote Route Collectors (RRCs). Given an IPv4 or IPv6 address, RISwhois will tell which prefixes and origin ASes on which RRCs match that particular IP. | + | RIPE NCC implements a similar whois service named RISwhois by providing a higher level view over the most recently collected set of routing tables from the Remote Route Collectors (RRCs) |
| <WRAP info> | <WRAP info> | ||
| Line 74: | Line 74: | ||
| </ | </ | ||
| - | In the following, a simple example | + | In the following, a simple example shows the output of a Riswhois |
| < | < | ||
| - | $ whois -h riswhois.ripe.net 217.70.180.132 | + | $ whois -h riswhois.ripe.net 203.178.141.194 |
| + | route: | ||
| + | origin: | ||
| + | descr: | ||
| + | lastupd-frst: | ||
| + | lastupd-last: | ||
| + | seen-at: | ||
| + | num-rispeers: | ||
| + | source: | ||
| + | </ | ||
| + | |||
| + | <WRAP round important> | ||
| + | Note RRCs may receive different information for the same IP prefix. | ||
| + | that Riswhois may provide multiple matchings for IP addresses. In such case, RRCs | ||
| + | </ | ||
| + | |||
| + | < | ||
| + | $ whois -h riswhois.ripe.net 217.70.184.1 | ||
| route: | route: | ||
| origin: | origin: | ||
who_is_using_this_ip_address.txt · Last modified: 2014/02/15 23:31 by samer