Jump to content

ramp115

Members
  • Content Count

    4
  • Joined

  • Last visited

About ramp115

  • Rank
    Newbie
  1. Im getting these errors in my logs during the scan Sat Jun 8 12:43:33 2019 kern.info kernel: [ 169.100000] eth0: link down Sat Jun 8 12:43:33 2019 kern.info kernel: [ 169.100000] br-lan: port 1(eth0) entered disabled state Sat Jun 8 12:43:38 2019 kern.info kernel: [ 174.100000] eth0: link up (100Mbps/Full duplex) Sat Jun 8 12:43:38 2019 kern.info kernel: [ 174.100000] br-lan: port 1(eth0) entered forwarding state Sat Jun 8 12:43:38 2019 kern.info kernel: [ 174.110000] br-lan: port 1(eth0) entered forwarding state Sat Jun 8 12:43:38 2019 daemon.notice netifd: Network device 'eth0' link is up Sat Jun 8 12:43:40 2019 kern.info kernel: [ 176.110000] br-lan: port 1(eth0) entered forwarding state Sat Jun 8 12:47:13 2019 kern.notice kernel: [ 319.200000] EXT4-fs (sda1): error count since last fsck: 1 Sat Jun 8 12:47:13 2019 kern.notice kernel: [ 319.200000] EXT4-fs (sda1): initial error at time 1540339851: __ext4_get_inode_loc:3855: inode 8: block 18 Sat Jun 8 12:47:13 2019 kern.notice kernel: [ 319.210000] EXT4-fs (sda1): last error at time 1540339851: __ext4_get_inode_loc:3855: inode 8: block 18
  2. SSH seems to work fine as well
  3. Hey Fam! I just set up my c2 cloud server on a digitalocean VPS w/ https, domain name and everything with no issues. I also set up my wifi pineapple to reconnect to the c2 web server when it connects to the interwebz. I cannot, however, seem to get the recon module working in the c2 web interface. It just keeps loading and saying there is no recon info yet. I let it run for a good 30-40 minutes before deciding something was wrong. Is this a bug or something on my end? Any help would be greatly appreciated. Much love to Hak5, Ramp115
×
×
  • Create New...