Conceal

Spoiler Removed

@Blkph0x said:
Yer I’m having issues with it now was fine getting 1st phase up and was holding it find changed something not even sure what and then at 1st I thought it was crashing my kali vm but it was screwing with my tunnel into my server.
Not sure why as I didnt change anything on that interface but if I use the console window and not rdp I can hold the connection if I’m in rdp it will crash and create 1000s of active connecting threads to the target box… so I should just try on my dedicated kali laptop is that what you mean?

thats what i meant , i havent trouble shooted to as why the VM was causing the connectivity issues to the “strong service” but i finally got phase 1 going when using kali straight from the USB stick on my desktop. just throwing in a tip in case it helps everyone else if they use a VM =)

After spending two decades to have the VPN up and running, finally I could hack the box. :wink:

Hack N’ Roll (-:

This machine is my nightmare - after VPN working, I still looking for privesc possibility.

I’ve given up for now. I thought in Windows it would be easier but it’s not.
But it’s true that no ISP filtering should be involved, because we are trying to vpn into a vpn and the ISP should not even notice it.

hint for root?

I think I’m onto something re root…
… got it.

After some deliberation I’ve decided to upvote this one. I really wish I could downvote the documentation for that obnoxious bit after the initial scans. There’s no way I would have ever sussed out all the details without a little help from a couple of people. However analyzing what it took actually resulted in some expanded understanding and an expanded reference library. And it’s such a refreshing change from web.

@mRr3b00t said:
… also if anyone has connectivity and it’s dropping just bring things back UP and you should be ok (I’m guessing the config can be adjusted to stop this!)

My tunnel lasts for a few minutes, then drops. It’s easy enough to bring up again, but it’s really slowing down progress towards root. Anyone with a stable tunnel willing to offer a tip?

got root! learn new stuff! that was very cool

@cbaker said:
My tunnel lasts for a few minutes, then drops. It’s easy enough to bring up again, but it’s really slowing down progress towards root. Anyone with a stable tunnel willing to offer a tip?

I got tired of screwing with the configs, so I didn’t use a “proper” way of stabilizing it. I wrote a script that waits for a connection and then just sends a shell command every five seconds as a sort of keepalive “ping”, then had the server connect back to it. Traffic seems to keep the connection alive.

Just did a bit of Googling and found the dpdaction and dpddelay settings, though, and those also seem to work. Give those a try.

Can confirm that dpd* can help in stabiizing although I still got some drops for certain type of enum tools.
v** setup was a giant mess. use the strong bird and in addition to what you find here in the forum make perfectly sure you’re using the correct i****.**s file. On my kali install I had to copy it to a certain directory. took quite some time to figure out it was using my .conf but not my i.*****s. Thanks to @schex for discussion on it.
priv esc was straight forward - if you’ve seen something similar before (as always) :wink:
Pay close attention what the user is allowed to do.
Feel free to PM for hints

@kekra said:
Hard to reply without spoiling, but if you want to connect to a VPN based on that version of the service in Windows, the only option you have is to combine it with some other protocol … which I called the ‘next phase’ above.

Final update: I’ve now made the connection work on Windows - so that I can really access services on the box!

Happy to provide nudges if somebody wants to try that. Hint: Don’t zoom in too much on the word ‘VPN’.

@opt1kz said:

I got tired of screwing with the configs, so I didn’t use a “proper” way of stabilizing it. I wrote a script that waits for a connection and then just sends a shell command every five seconds as a sort of keepalive “ping”, then had the server connect back to it. Traffic seems to keep the connection alive.

Just did a bit of Googling and found the dpdaction and dpddelay settings, though, and those also seem to work. Give those a try.

Thanks, I did the same thing, and it does a pretty good job. I’ll look at those. I also tried some different settings for rekey and reauth and some others like lifetime but didn’t have much success.

@opt1kz said:

I wrote a script that waits for a connection and then just sends a shell command

nc -z works great as a “tcp ping”

@LegendarySpork said:
@opt1kz said:

I wrote a script that waits for a connection and then just sends a shell command

nc -z works great as a “tcp ping”

Hm. That’s interesting. I never noticed that flag, to be honest. Googling and playing around with it a bit and you could probably use this too, you’re right. Neat.

For me it was easier/quicker to just whip out Python and do it that way (it was all of ten lines), but this netcat feature could be useful in the future, so thanks!

TCP ping 4evR

while :; nc - z 10.10.10.10 21; sleep 10; done

Another good use – I use nc - z flag for scanning whenever transport is limited somehow and nmap isn’t reliable. I used this on another active box recently.

can someone pm me. I’m having some trouble talking to president Eisenhower. I’ve never done it, i’ve already installed more software on my computer than i’m really happy with, and it’s making me feel all sorts of stupid

@LegendarySpork said:
TCP ping 4evR

while :; nc - z 10.10.10.10 21; sleep 10; done

Another good use – I use nc - z flag for scanning whenever transport is limited somehow and nmap isn’t reliable. I used this on another active box recently.

For scanning via nc I always add -w 1 so I don’t have to wait for longer timeouts and -vn to get results and omit dns resolution, eg. scan for the first 100 ports:

nc - zvn - w 1 1.2.3.4 1-100

@spoppi Yes, agreed, that timeout is important for scanning. Also for those following along at home, notice that @spoppi didn’t need to write the iteration over ports because nc does that. (the reason I had an iteration was because I was periodically pinging a single port)

Rooted ! :smiley: