My ip hasn’t changed in weeks weirdly, so it’s been useful for me, I just whacked in 192.169.0.21:1337 and it’s great for hitting R1 on start up and then running over to my laptop lol.
Yea, most routers remember the mac address of a device and then reserve an IP address for it so that every time that device connects it will always get the same IP address.
RE the kernel/syscalls thing. Over the last few days I have been doing some extensive tests and written some pages that can test every single syscall and get a comparable result from it.
Here is an example:
The test run is 'p.syscall(2,p.stringify('root'))'
image 1: These are the results without the kernel being patched. (page 1 of 3!)
image 2: These are the results with just the kernel being patched. As you can see, syscalls 20,23,24 & 25 now give different results!
image 3: This is to show that syscall 50 shows 'all f's' both before and after the kernel is patched but changes to '0' when Mira has been run.
This shows us we can use syscall 50 to test if Mira is loaded or not.
I've also found some interesting things while testing. In Specters 5.05 exploit if you look in the syscalls.js I have found several mistakes.
There are several syscalls defined in the list which are invalid and do not actually exist and there are syscalls that work (give back a result when tested) that are not included in the list.
(In total: 27 invalid syscalls and 5 missing syscalls)
The basic purpose to my test is to find any detectable changes when various payloads are run.
When I have tidied some things up I'll share the tester and results here so anyone else can play around with it.