RangeFucker 3.0
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

RangeFucker 3.0

Started by bastya_elvtars, 12 January, 2007, 01:50:32

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

bastya_elvtars

Hi all, I have updated RangeFucker. Here is the changelog for 3.0:
fixed: rightclick not being sent to ops
changed: script is lua 5.1.1-only (so is ptokax)
fixed: CIDR support is now fully compliant with RFC1518
added: dotted (x.x.x.x) netmask support
changed: using bitwise operations powered by luabit
changed: relicensed under the GPL
added: rightclick for netmask and CIDR, not only single IPs


This is a pre-release version, and it may contain bugs. If no objection comes, I will make this the final release in 1 week, so please test it thoroughly, thank you.
Everything could have been anything else and it would have just as much meaning.

bastya_elvtars

Here you can find the manual.
No feedback at all? :(
Everything could have been anything else and it would have just as much meaning.

CHILLCODE?

Well I have a little question about

function getrange(decip,decmask)

now I think what you want to do here is calculate the range from a CIDR-Ranges,
but since you use bitwise anyways why not claculate them through bitwise a little exsample of how
to do so, in less steps

CIDR = 10.4.12.0/22

IP = 10.4.12.0
(00001010.00000100.00001100.00000000)
and subnetmask = 255.255.12.0
(11111111.11111111.11111100.00000000)

now to get the startIP we only have to AND these two
e.g. startIP = AND( IP, subnet), Results in
(00001010.00000100.00001100.00000000) = 10.4.12.0

okey now to calculate the end IP we first do a not on the subnet
notsubnet = NOT(subnet) which results in
(00000000.00000000.00000011.11111111)
then we do a OR( startIP, notsubnet) to get the End IP which results in
(00001010.00000100.00001111.11111111) = 10.4.15.255


and there you have your ranges, in a few little steps, which should boost the functions
performance.







bastya_elvtars

Uhm, well, maybe I have overlooked the part of the linked documents that deals with this. I'll look into the topic a bit deeper, thanks for the hint.
Everything could have been anything else and it would have just as much meaning.

bastya_elvtars

Ah yes, I got the idea finally from here. Thanks for the hint, I've overlooked this.
OK, 3.0 has been released. Grab it from my brand new download page.
Everything could have been anything else and it would have just as much meaning.

SMF spam blocked by CleanTalk