89vision Posted May 30, 2012 Share Posted May 30, 2012 (edited) Just got a brand new wifipineapple IV this morning, but it doesn't seem to want to cooperate. I'm running Arch, connected to my wifi through wpa_supplicant. Here is the output of wp4.sh. Eth0 is connected directly to the pineapple with the patch cord provided [root@matt-laptop scripts]# ./wp4.sh Input Pineapple Netmask [or ENTER for 255.255.255.0]: Input Pineapple Network [or ENTER for 172.16.42.0/24]: Input Interface between PC and Pineapple [or ENTER for eth0]: Input Interface between PC and Internet [or ENTER for wlan0]: Input Internet Gateway [or ENTER for 192.168.1.1]: Input IP Address of Host PC [or ENTER for 172.16.42.42]: Input IP Address of Pineapple [or ENTER for 172.16.42.1]: Pineapple connected to: eth0 Internet connection from: wlan0 Internet connection gateway: 192.168.1.1 Host Computer IP: 172.16.42.42 Pineapple IP: 172.16.42.1 Network: 172.16.42.0/24 Netmask: 255.255.255.0 IP Forwarding enabled. /proc/sys/net/ipv4/ip_forward set to 1 iptables chains and rules cleared IP Forwarding Enabled Default route removed Pineapple Default Gateway Configured 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 --- 172.16.42.1 ping statistics --- 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2006ms pipe 3 Browse to http://172.16.42.1/pineapple -- Happy Hacking! here is the output of ifconfig after I run this: eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 metric 1 inet 172.16.42.42 netmask 255.255.255.0 broadcast 172.16.42.255 inet6 fe80::222:19ff:fee3:3e76 prefixlen 64 scopeid 0x20<link> ether 00:22:19:e3:3e:76 txqueuelen 1000 (Ethernet) RX packets 397 bytes 161579 (157.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 118 bytes 16694 (16.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 17 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 metric 1 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 0 (Local Loopback) RX packets 3088 bytes 289328 (282.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 3088 bytes 289328 (282.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 metric 1 inet 192.168.1.126 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::222:fbff:fe12:7f9a prefixlen 64 scopeid 0x20<link> ether 00:22:fb:12:7f:9a txqueuelen 1000 (Ethernet) RX packets 15588 bytes 9329157 (8.8 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 12615 bytes 2377146 (2.2 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Am I doing something wrong? Do I have a bad unit? Edited May 30, 2012 by 89vision Quote Link to comment Share on other sites More sharing options...
Mr-Protocol Posted May 30, 2012 Share Posted May 30, 2012 Try to set your IP on eth0 manually (not running the script) and see if you can ping it then. Also make sure the pineapple has had power for a few minutes to make sure it was fully booted. You can also try using a cross-over network cable, if you have one, in place of the straight through cable which comes from the hakshop purchased ones. Also, what lights are on after it has been powered for a few minutes? What ethernet port are you connecting to? The PoE port is the one to be used (one closest to the power plug for AC/DC adapter). Quote Link to comment Share on other sites More sharing options...
89vision Posted May 30, 2012 Author Share Posted May 30, 2012 Try to set your IP on eth0 manually (not running the script) and see if you can ping it then. Also make sure the pineapple has had power for a few minutes to make sure it was fully booted. You can also try using a cross-over network cable, if you have one, in place of the straight through cable which comes from the hakshop purchased ones. Also, what lights are on after it has been powered for a few minutes? What ethernet port are you connecting to? The PoE port is the one to be used (one closest to the power plug for AC/DC adapter). Hmmm... I thought maybe the straight through patch cord might be a problem - I don't have a xover handy, I'll have to grab one from work tommorrow. Manually setting the ip address didn't help. I let it sit for about 10 minutes, and the only lights on are wlan, wan, pwr, and "wps". Quote Link to comment Share on other sites More sharing options...
PineDominator Posted May 30, 2012 Share Posted May 30, 2012 (edited) Hmmm... I thought maybe the straight through patch cord might be a problem - I don't have a xover handy, I'll have to grab one from work tommorrow. Manually setting the ip address didn't help. I let it sit for about 10 minutes, and the only lights on are wlan, wan, pwr, and "wps". what about trying a different cable altogether? here is what I would do first to rule out the setup and wp4.sh script, when you plug into the POE port and set your computers ethernet port to auto dhcp. if all is good you should get an ip like 172.16.42.XXX, then brows to 172.16.42.1/pineapple/ Edited May 30, 2012 by petertfm Quote Link to comment Share on other sites More sharing options...
89vision Posted May 30, 2012 Author Share Posted May 30, 2012 what about trying a different cable altogether? here is what I would do first to rule out the setup and wp4.sh script, when you plug into the POE port and set your computers ethernet port to auto dhcp. if all is good you should get an ip like 172.16.42.XXX, then brows to 172.16.42.1/pineapple/ Well I feel like a dumbass... I plugged it into the POE port and it worked perfectly. I guess I could always switch careers... Thanks for everyone's help Quote Link to comment Share on other sites More sharing options...
Sebkinne Posted May 30, 2012 Share Posted May 30, 2012 Don't worry, happens to a lot of people. We should really auto enable both ports.. Glad you got it working! Seb Quote Link to comment Share on other sites More sharing options...
Mr-Protocol Posted May 30, 2012 Share Posted May 30, 2012 Don't worry, happens to a lot of people. We should really auto enable both ports.. Glad you got it working! Seb What he said :P. It usually is a simple mistake that is overlooked. Enjoy your fruit. I actually had some sliced pineapple today :). Quote Link to comment Share on other sites More sharing options...
Sebkinne Posted May 30, 2012 Share Posted May 30, 2012 What he said :P. It usually is a simple mistake that is overlooked. Enjoy your fruit. I actually had some sliced pineapple today :). Stop making me hungry. It is too early to be hungry! Quote Link to comment Share on other sites More sharing options...
Battery_ Posted August 23, 2012 Share Posted August 23, 2012 (edited) [edit] Posted issue in wrong thread...my bad Edited August 23, 2012 by Battery_ Quote Link to comment Share on other sites More sharing options...
exeption Posted August 23, 2012 Share Posted August 23, 2012 Same issue here as Battery_ No matter what menu item I press, the screen goes blank white with error "unable to connect" Seems like Karma is throwing of wlan0 which again make the pineapple loose its connection.. Most I've got is two prob responses, and that is from my own wireless network.. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.