IT BS thread

I'm installing parrot security os on my pi. Have any of you guys used it?

https://youtu.be/Z1YCdhfxwa0

 

Hello IT/ Kali linux people,

Still messing with my pi 3. Loaded kali linux on it, and went through the steps to enable the wifi dongle (tp link TL-WN722N). Got it working, sort of. I can scan and connect to it, but when I disconnect it from my router, I loose it and it dies.

After Googling some stuff, I found this article, link below.

http://www.drchaos.com/enable-ssh-on-kali-linux-enable-ssh-on-kali-linux/

Do I need to go through the steps and enable ssh? Is that why it dies when I disconnect from my router?

Thank ypu.

 

What do you mean by dies? Disconnect it from the router?

 

When I installed kali linux on my raspberry pi 3, I have to plug it in to my wifi router in order to ssh into the pi 3/ linux. After I plug it in to my router, I use fing to find the ip of my pi3 on my wlan. As long as it's plugged into my router I can get a wifi signal from the wifi dongle.

As soon as I unplug it from my wifi router, and try to ssh into the pi, just through wifi, the dongle stops broadcasting a signal and I can't ssh into the pi3/linux.

 

What I'm trying to do with all this stuff.

Building a small raspberry pi, pen testing box. I've had better luck getting things to work on raspbian, but I wanna get it to work on kali linux. Right now, about 90% working on raspbian.

I initially started with a tp-link TL-WN722N wifi dongle, got this cause of the tutorial on youtube, but also cause it supports monitor mode. When I initially installed aircrack-ng I tried to do a scan at school (I asked my professor before trying to scan) and when it went to monitor mode, my ssh session got cut off. Didn't have an ethernet cable so I couldn't run aircrack from the ssh session without loosing connection.

So I got another dongle, TL-WN725N, mainly cause the range on the pi's internal wifi sucks. Both dongles work independently. When I boot up my pi both dongles will fire up and obtain an ip address from my router, but after like maybe 10-15 seconds, one of the signals will shutdown, usually it is wlan2.

My guess is that wlan1 has priority so maybe the pi shuts off or cuts the signal to wlan2?

If I establish an ssh session from the ip address that associated with the TL-WN725N, can I still run the following command, airmon-ng start wlan2 9
and get the TL-WN722N into monitor mode and still have a ssh session through the TL-WN725N

I could have just tried running it, but I re-installed raspbian, so at the moment aircrack isn't on there.





I blacked everything out cause I'm not jedi yet like you folks.

 

One thing to note is your wireless and eth0 will have different MAC address. If your pi has an address on eth0 when you disconnect it a second MAC will have a second IP from DHCP. Have you tried doing another search?

 

A search with fing? I will try later tonight.

My second thought is, since I have both wifi dongles set up and working, just assign two different access points to the pi, at school I can put one wifi dongle on A and put the second one on B. That way each gets assigned an individual ip from two different networks. Not sure if it will work, but I'm gonna try and see what happens.

 

You can do that. What would be the purpose though? You will want to make sure only 1 side has a default gateway otherwise you can have weird session based issues as WAN IP can change.

 

To be honest, I don't really need two individual ip's. I just need to make sure I can connect through and establish an ssh session through the TL-WN725N, which I can, and I just want to be able to put the other into monitor mode. Since both dongles work, I think I should be able to do this.

 

Like I said man if you have a wifi connection to your home wireless and a cable plugged into the same wifi-access point/L2 switch/firewall router combo (or whatever it is), youhave 2 IPs on the same network. Two different MAC addresses.

That explains why if you plug in with a cable you can ssh into THAT IP, you're getting eth0's IP. If you then setup wifi, unplug the cabled connection you'll drop. The wifi is at a different IP on the same network as every NIC has it's own MAC address (spoofing not withstanding....).

 

Unless you're on a PS3/PS4

 

Like I said... spoofing not withstanding.

 

Got them both working. I think it is set up how I want it. I haven't tried running aircrack-ng or monitor mode, but I can log into the IP associated with wlan1 which is set to the mini wifi dongle WN-725N and the wlan2 which is dongle WN-722N, the one I can get into monitor mode, has its own ip. I can still run the command: sudo iwlist wlan2 scan | grep ESSID from wlan1 and scan SSID's.

So I am hoping I will be able to get it into monitor mode and still be connected to the mini dongle

 

Those SSID's are boring

Did you honestly hide your private IP's? bruhhh

 

I'm not Jedi yet and some of the shit that you guys can do scare me. So yes, I did black out my IP's.

 

ips inside your network are trivially easy to obtain.

 

If the IP you have is

192.168.0.0/16
172.16.0.0/12
10.0.0.0/8
169.254.0.0/16

You do not have to hide it.

 

Do you foresee any problems with having the wifi dongles set up this way?

 

Nope. If wlan1 is on network 192.168.0.0/16 and wlan2 is on 10.0.0.0/24, if your computer is on 192.168.0.0/16 you can communicate with the device and it will be able to reach both networks.

Again though, like I said, if you have a gateway on both IPs and the route priorities are wrong you may have weird issues. ESPECAILLY if the 10.0.0.0/24 network happens to have some route built that would point to another network with a 192.168.0.0/24... say via a VPN or MPLS.

 

my noobeness.