Jump to content

Search the Community

Showing results for tags 'dhcp'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Talk
    • Everything Else
    • Gaming
    • Questions
    • Business and Enterprise IT
    • Security
    • Hacks & Mods
    • Applications & Coding
    • Trading Post
  • WiFi Pineapple
    • WiFi Pineapple TETRA
    • WiFi Pineapple NANO
    • WiFi Pineapple Mark V
    • WiFi Pineapple Mark IV
    • Pineapple Modules
    • WiFi Pineapple University
    • WiFi Pineapples Mark I, II, III
  • Hak5 Gear
    • Hak5 Cloud C²
    • Bash Bunny
    • Packet Squirrel
    • LAN Turtle
    • USB Rubber Ducky
    • Plunder Bug
  • Hak5 Shows
    • Hak5
    • HakTip
    • Metasploit Minute
    • Threatwire
  • Community
    • Forums and Wiki
    • #Hak5
  • Projects
    • SDR - Software Defined Radio
    • Community Projects
    • Interceptor
    • USB Hacks
    • USB Multipass
    • Pandora Timeshifting

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Enter a five letter word.

Found 6 results

  1. Hello there! Just got a bash bunny that worked fine when I got it. I decided to upgrade it using apt, and got a lot of issues. I fixed the problems I had with apt (fixed issues with procps), and now it seems to have some issues with DHCP when connecting to my computer using FNDIS_ETHERNET. If I connect the bunny and then set a static ip for it, I can ssh in as normal. Then I see that the service isc-dhcp-service has failed. If I try to start that service again, it seems like it works just fine. I get a dhcp lease from the computer and can GET TARGET_IP. So maby this is an issue with the usb0 interface not being ready when the dhcp server starts or something? I am not sure. It is pretty annoying that I have to set a static ip, log in with ssh, restart the service, set dynamic ip again just to get dhcp to work 😛 Have anyone else had any issues like this? I will provide you with more logs and stuff soon
  2. I have problems to connect to the open wifi network of "wifi pineapple nano", I currently have firmware 2.0.2 and I did a factory reset edit: Fixed
  3. Hi guys, Once again, Dave-ee Jones comin' at you with another question! How would one loop forever until an IP address (172.16.64.10-12), via DHCP, has been given to the client? Looking for something like this... while cannot_see_client { sleep 1 } # Continue with rest of code
  4. Hi, I went through the initial setup by connecting my Turtle to my laptop and updating to the latest version (per ).%C2'> Once I reset the password for the SSH connection, I disconnected the Turtle from my laptop and connected it directly to my LAN switch. I can see the device come up and pull a DHCP address, and I can ping it just fine, but ALL ports are closed - no SSH for me. Once I reconnect to my laptop to get the 172.16.84.x address, I'm back in business. I must be missing something - maybe I need to configure one of the modules differently or something? F
  5. I have dropped my turtle onto my employer's network. I can see the WAN has been assigned an IP Address via DHCP. The problem is with the computer that is using the Turtle as an ethernet adapter. It is given it's own IP address and it can access the internet fine but DNS is not working. I can ping the devices on the corporate network, connect to our servers via RDP using IP address but no names are being resolved. Any ideas? I tried setting both eth0 and eth1 to dhcp but then I couldn't SSH to it.
  6. Hello everybody, i have just bought this amazing piece of hardware and i would like to know if problems i am experiencing are "normal" or there's something wrong with it or my set up. The first i plugged in the Lan Turtle to my Mac it didn't assign an IP via DHCP. So i have tried to connect to it using the self assigned 169.254.x.x IP as i saw there were SSH and DNS services enabled. Unfortunately it wasn't possible to log in as the default credentials didn't work forcing me to explore the unblocking procedure for a factory reset. After the reset i was able to connect to it but mostly the 50% of the time i plug in my Lan Turtle if i do not get IP even is SSH is accessible i cannot connect to it..Do you know guys why this is happening?(the non working dhcp but most importantly the wrong credential behaviour) Thanks in advance for any feedback
×
×
  • Create New...