Skip to main content
Topic: connman-gtk is not cycling IP addresses. (Read 217 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

connman-gtk is not cycling IP addresses.

I'm using public wifi, so I need to cycle my IP's and mac's when people get nosy.
cmst will cycle the ip addresses.
connman-gtk is not cycling the ip's.
I want to break any MITM they have set up and stop their eventual fuzzing of the browser.
I'm not sure how I'm going to deal with them hooking the login gui, but for now I re-install.
They are installing their backdoor that will boot at login, probably before they begin fuzzing the browser.
By the time I see the browser fuzzing they have already dropped their files and cleaned the logs, so I'm dealing with a lost cause at that point.

Typically, when someone is poking around in my system, I change my connection.
I'm not a fan of Capture The Flag: Cafe Edition and I can't afford a VPN right now, TOR is too slow for video scrolling.
I do have a Pi I planned to turn into a 4G router but I haven't programmed AT the modem yet.

Can I do this with connman-gtk?
How do I address cycling my IP and randomizing my Mac when trouble is near?


Re: connman-gtk is not cycling IP addresses.

Reply #2
I have macchanger. It causes additional issues and doesn't cycle the IP.

I have disabled autoconnect.
disconnect from network.

Settings: set to DHCP
(In cmst, to cycle the IP's you must set a static IP then change it to DHCP to trigger the IP to cycle. DHCP grabs a new IP.)
The cmst method doesn't work with connman-gtk when I tried it.

macchanger -er wlan0
Code: [Select]
[ERROR] Could not change MAC: interface up or insufficient permissions: Device or resource busy
(Adding the macchanger issue complicated learning how to cycle the IP in DHCP mode.)

To fix the [error], I have to turn off the wifi, then turn wifi back on.
After this step, macchanger works, but IP remains the same.

Re: connman-gtk is not cycling IP addresses.

Reply #3
Last I checked, macchanger won't work if the interface is up. DHCP servers usually assign new IPs to new MACs, if the latter appear within a short interval; you cannot force a DHCP server you don't control to assign you a different IP. You have to resort to static.

 
Artix forum uses a single cookie to remember youOK