Jump to content

catz

Active Members
  • Posts

    5
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by catz

  1. What about local cage proxy to store all of the websites and a custom php script to recall all of them? 500gb usb storage device-->proxy installed on the usb--> pluged in to mk4 ?? or website-->local proxy-->custom php script to modify login page-->back to user ?? Just thinking out loud.
  2. Hi,Seb Now some more errors with 2.0.1. Fist I had to reflash the unit so it would work again. After reflashing it the interface would said disabled and then I would go to advanced page and click on refresh ip tables and then restore to factor for the status page to say interface enabled. Ok second, I tried what you said but it just froze on me and I could not ping or ssh into it or refresh the web page. I did get this for the fist time on the config page. Warning: fopen(/etc/config/wireless) [function.fopen]: failed to open stream: No such file or directory in /www/pineapple/config.php on line 73 Could not open file! Here is the ping request that I would get and it looks like its taking awhile to boot up. @ ~ $ ping 172.16.42.1 -c 5 PING 172.16.42.1 (172.16.42.1) 56(84) bytes of data. From 172.16.42.42 icmp_seq=1 Destination Host Unreachable From 172.16.42.42 icmp_seq=2 Destination Host Unreachable From 172.16.42.42 icmp_seq=3 Destination Host Unreachable From 172.16.42.42 icmp_seq=4 Destination Host Unreachable From 172.16.42.42 icmp_seq=5 Destination Host Unreachable --- 172.16.42.1 ping statistics --- 5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 4006ms pipe 3 @ ~ $ ping 172.16.42.1 -c 5 PING 172.16.42.1 (172.16.42.1) 56(84) bytes of data. From 172.16.42.42 icmp_seq=1 Destination Host Unreachable From 172.16.42.42 icmp_seq=2 Destination Host Unreachable From 172.16.42.42 icmp_seq=3 Destination Host Unreachable From 172.16.42.42 icmp_seq=4 Destination Host Unreachable From 172.16.42.42 icmp_seq=5 Destination Host Unreachable --- 172.16.42.1 ping statistics --- 5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 4007ms pipe 3 @~ $ ping 172.16.42.1 -c 5 PING 172.16.42.1 (172.16.42.1) 56(84) bytes of data. From 172.16.42.42 icmp_seq=3 Destination Host Unreachable From 172.16.42.42 icmp_seq=4 Destination Host Unreachable From 172.16.42.42 icmp_seq=5 Destination Host Unreachable --- 172.16.42.1 ping statistics --- 5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4016ms pipe 2 @~ $ ping 172.16.42.1 -c 5 PING 172.16.42.1 (172.16.42.1) 56(84) bytes of data. From 172.16.42.42 icmp_seq=1 Destination Host Unreachable From 172.16.42.42 icmp_seq=4 Destination Host Unreachable --- 172.16.42.1 ping statistics --- 5 packets transmitted, 0 received, +2 errors, 100% packet loss, time 4007ms @ ~ $ ping 172.16.42.1 -c 5 PING 172.16.42.1 (172.16.42.1) 56(84) bytes of data. From 172.16.42.42 icmp_seq=1 Destination Host Unreachable From 172.16.42.42 icmp_seq=2 Destination Host Unreachable From 172.16.42.42 icmp_seq=3 Destination Host Unreachable From 172.16.42.42 icmp_seq=4 Destination Host Unreachable 64 bytes from 172.16.42.1: icmp_req=5 ttl=64 time=1011 ms --- 172.16.42.1 ping statistics --- 5 packets transmitted, 1 received, +4 errors, 80% packet loss, time 4008ms rtt min/avg/max/mdev = 1011.247/1011.247/1011.247/0.000 ms, pipe 3 @ ~ $ ping 172.16.42.1 -c 5 PING 172.16.42.1 (172.16.42.1) 56(84) bytes of data. 64 bytes from 172.16.42.1: icmp_req=1 ttl=64 time=1.55 ms 64 bytes from 172.16.42.1: icmp_req=2 ttl=64 time=0.959 ms 64 bytes from 172.16.42.1: icmp_req=3 ttl=64 time=0.945 ms 64 bytes from 172.16.42.1: icmp_req=5 ttl=64 time=0.985 ms --- 172.16.42.1 ping statistics --- 5 packets transmitted, 4 received, 20% packet loss, time 4008ms rtt min/avg/max/mdev = 0.945/1.111/1.555/0.256 ms @ ~ $ ping 172.16.42.1 -c 5 PING 172.16.42.1 (172.16.42.1) 56(84) bytes of data. --- 172.16.42.1 ping statistics --- 5 packets transmitted, 0 received, 100% packet loss, time 4006ms @ ~ $ ping 172.16.42.1 -c 5 PING 172.16.42.1 (172.16.42.1) 56(84) bytes of data. From 172.16.42.42 icmp_seq=2 Destination Host Unreachable From 172.16.42.42 icmp_seq=3 Destination Host Unreachable From 172.16.42.42 icmp_seq=4 Destination Host Unreachable From 172.16.42.42 icmp_seq=5 Destination Host Unreachable --- 172.16.42.1 ping statistics --- 5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4007ms pipe 2 @ ~ $ ping 172.16.42.1 -c 5 PING 172.16.42.1 (172.16.42.1) 56(84) bytes of data. From 172.16.42.42 icmp_seq=2 Destination Host Unreachable From 172.16.42.42 icmp_seq=3 Destination Host Unreachable From 172.16.42.42 icmp_seq=4 Destination Host Unreachable From 172.16.42.42 icmp_seq=5 Destination Host Unreachable --- 172.16.42.1 ping statistics --- 5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4008ms pipe 2 @ ~ $ ping 172.16.42.1 -c 5 PING 172.16.42.1 (172.16.42.1) 56(84) bytes of data. From 172.16.42.42 icmp_seq=1 Destination Host Unreachable From 172.16.42.42 icmp_seq=2 Destination Host Unreachable From 172.16.42.42 icmp_seq=3 Destination Host Unreachable From 172.16.42.42 icmp_seq=4 Destination Host Unreachable From 172.16.42.42 icmp_seq=5 Destination Host Unreachable --- 172.16.42.1 ping statistics --- 5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 4016ms pipe 3 Also, I here is the ssh connection or how many time it took. ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: No route to host ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: No route to host ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: No route to host ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: No route to host ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: No route to host ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: No route to host ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: No route to host ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused r ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused @ ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused @ ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused @~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused @ ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused @ ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused @ ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused @ ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused @ ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused @ ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused @ ~ $ ssh 172.16.42.1 -l root ssh: connect to host 172.16.42.1 port 22: Connection refused @ ~ $ ssh 172.16.42.1 -l root root@172.16.42.1's password: BusyBox v1.19.3 (2012-01-02 16:35:40 CET) built-in shell (ash) Enter 'help' for a list of built-in commands. root@Pineapple:~# hostapd_cli -p /var/run/hostapd-phy0 karma_disable this is where is froze Now I have to reflash the unit for it to work again.
  3. Hi, To Everyone and thanks for your hard work on the new firmware 2.0.1.Can't wait for 3.0 firmware. The unit is flashed with 2.0.1 and normal configuration. The issue that I am having in the GUI after turning off Karma is that it just hangs their and does not refresh the page so then I unplug the MK3 unit and then plug it back in, long story short. I can't access the MK3 unit after that.So the only way to access the MK3 unit again is to reflash the unit with fon-flash-gui for linux and then the unit works again. I am also pinging the unit at the same time to see if there is a connection, but there is no connection before or after unplug the unit. Also, I can't remember how to upload/download files with the MK3 unit in a Linux OS. I know that using WinSCP for windows will work, but as of right know I don't have a windows box handy. Thanks,
  4. First do you have a backup of everything.Because if not you could lose some stuff. It sounds like it could be your master boot record (MBR) needs to be repaired.But if you need the paper from your windows install you could burn a disc or a usb flash drive of linux boot it up and mount the linux/windows dual boot hard drive to the boot up disc or flash drive and pull off the paper or other stuff before repair your MBR.You will need the windows disc to use the bootrec.exe that is on the windows 7 repair disc.
  5. I made this simple mac changer script for the ALFA USB WiFi AWUS036H. There might be a better way of writing this. (open to any ideas.) #!/bin/sh echo "wired/wireless network" ifconfig wlan0 echo "wireless network" iwconfig wlan0 #bring down the wireless network sudo ifconfig wlan0 down echo wlan0 down #change the mac address #newmac=`echo $RANDOM$RANDOM | md5sum | sed -r 's/(..)/\1:/g; s/^(.{17}).*$/\1/;'` sudo ifconfig wlan0 hw ether de:ed:be:ef:c0:fe #$newmac #echo "New mac adress: $newmac" #Bring up the wireless network sudo ifconfig wlan0 up echo wlan0 up echo "wired/wireless network" ifconfig wlan0 echo "wireless network" iwconfig wlan0 read ifconfig iwconfig But, maybe Darren can mod this and add this to the mk3 with a button in the advanced tab.(click to change MAC) Just an idea. Yours, is a little bit easier to do. Not trying to hijack your thread,but thought this might go under the same thread for changing MAC address's. thanks, catz
×
×
  • Create New...