Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>With this code, it does not validate correctly.</p> <p>For example:</p> <pre><code>scala&gt; val ip = java.net.InetAddress.getByName("::ffff:1.2.176.0") ip: java.net.InetAddress = /1.2.176.0 scala&gt; val prefix = new InetPrefix(ip, 20) prefix: InetPrefix = InetPrefix@6febf6f9 scala&gt; prefix.contains(java.net.InetAddress.getByName("::ffff:1.2.176.20")) res11: Boolean = true scala&gt; prefix.contains(java.net.InetAddress.getByName("::ffff:1.2.191.20")) res12: Boolean = false </code></pre> <p>But if you calculate that network: (1.2.176.0/20)</p> <pre><code>$ sipcalc 1.2.176.0/20 -[ipv4 : 1.2.176.0/20] - 0 [CIDR] Host address - 1.2.176.0 Host address (decimal) - 16953344 Host address (hex) - 102B000 Network address - 1.2.176.0 Network mask - 255.255.240.0 Network mask (bits) - 20 Network mask (hex) - FFFFF000 Broadcast address - 1.2.191.255 Cisco wildcard - 0.0.15.255 Addresses in network - 4096 Network range - 1.2.176.0 - 1.2.191.255 Usable range - 1.2.176.1 - 1.2.191.254 - </code></pre> <p>I rewrote both (IPv4 and IPv6) in Scala put it for everyone on GitHub. It now also validates within ranges (so /20 etc will be regarded, which the old one did not do.)</p> <p>You can find the code (i separated it into IPv4 and IPv6) at <a href="https://github.com/wasted/scala-util/blob/master/src/main/scala/io/wasted/util/InetPrefix.scala" rel="nofollow">https://github.com/wasted/scala-util/blob/master/src/main/scala/io/wasted/util/InetPrefix.scala</a></p> <p>I also created a <a href="http://uberblo.gs/2012/12/scala-utils-with-ip-subnet-matching" rel="nofollow">blogpost about this</a>.</p>
    singulars
    1. This table or related slice is empty.
    1. POOptimal IP subnet matching
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USFranz Bettag
    1. USFranz Bettag
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUndeletion
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI never claimed it did validate correctly. I was just showing the OP how to get their (probably broken) code to run faster. If you can fix it, that would make for a good answer--otherwise your "answer" is a bit too much like a comment!
      singulars
      1. PO
      1. USRex Kerr
    2. COI had to write 2 ways of checking it, IPv6 was your way while IPv4 relies on calculating the start/end of the range as Longs and then compare the value. Both are very straight forward. Please feel free to submit suggestions. :)
      singulars
      1. PO
      1. USFranz Bettag
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload