GithubHelp home page GithubHelp logo

sii / sipcalc Goto Github PK

View Code? Open in Web Editor NEW
313.0 313.0 19.0 264 KB

Sipcalc is an advanced ip calculator supporting both IPv4 and IPv6.

Home Page: http://www.routemeister.net/

License: Other

Shell 51.59% C 48.41%

sipcalc's People

Contributors

sii avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

sipcalc's Issues

Splitting doesn't show split subnets in CIDR

When using sipcalc to split a network, the output does not show any of the resulting subnets in CIDR format. Instead, the section headers confusingly prints out the CIDR provided on the cmdline. For example:

$ sipcalc -s /17 -u 192.168.0.0/16  | grep /
-[ipv4 : 192.168.0.0/16] - 0
-[ipv4 : 192.168.0.0/16] - 0
-[ipv4 : 192.168.0.0/16] - 0

I see two potential ways to fix this:

  1. Add CIDR notation as an output line to print_cidr_info_v4
  2. Change the section header to reflect the subnet being printed. (e.g. with the above cmdline you'd see section headers:
    -[ipv4 : 192.168.0.0/17] - 0
    -[ipv4 : 192.168.0.128/17] - 0
    

I can supply a PR with either or both of these changes if you can share which you'd prefer.

bad interpretation of :: when 7 segment are filled

sipcalc 2001:dead:beaf:dead:beaf:dead:beaf::/128
cause an error
-[ERR : Unable to retrieve interface information]

in my point of view it should at least interpreted as
sipcalc 2001:dead:beaf:dead:beaf:dead:beaf:0/128
which resolve fine.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.