lan spoof: bug?
Moderators: jelco, bert_the_turtle, Chris, Icepick, Rkiver, Punisher Bass
I know this is an old thread, but I just had the same problem, so googled and this thread popped up. I think I might have found the answer.
First pic is pre-spoof:
Linky
Now the terminal with the subnet (arrow 2) was getting spoofed and then cracked, but nothing. What I discovered was that you should spoof the terminal, then probe the controller (arrow 1) to test if the link to the next hop appears (pic 2). If not then the subnet isn't spoofed. One thing that solved the so-called 'spoof bug' was closing the spoof tool and re-starting it.
So....
1. Start the spoof tool afresh.
2. Spoof the subnet terminal.
3. Probe the Controller to establish link to next hop (restart spoof and repeat until successful.
4. Hope to spoofed terminal and connect and crack.
5. Hop back to lock.
6. Hop to Controller, crack and continue.
First pic is pre-spoof:
Linky
Now the terminal with the subnet (arrow 2) was getting spoofed and then cracked, but nothing. What I discovered was that you should spoof the terminal, then probe the controller (arrow 1) to test if the link to the next hop appears (pic 2). If not then the subnet isn't spoofed. One thing that solved the so-called 'spoof bug' was closing the spoof tool and re-starting it.
So....
1. Start the spoof tool afresh.
2. Spoof the subnet terminal.
3. Probe the Controller to establish link to next hop (restart spoof and repeat until successful.
4. Hope to spoofed terminal and connect and crack.
5. Hop back to lock.
6. Hop to Controller, crack and continue.
Who is online
Users browsing this forum: No registered users and 6 guests