Getting Started With My Mkiv

[Phyrne]

Hoping someone can help me here...

I'm having some trouble communicating with my Mark IV over ethernet.

Here's the system & setup details:

MacBook Air running x86_64 Arch Linux (3.5.3-2 kernel with CK patchset)

Interface connected to my home router: wlan0

Interface connected to the Pineapple: eth0 (this is a usb to ethernet dongle, going into the PoE port on the Pineapple)

After powering on the Pineapple, leaving it for a minute or two to settle (WPS button stopped flashing n whatnot) I then connect it to my MacBook as described above.

Running ifconfig only shows lo and wlan0, so, I manually bring up eth0 with sudo ifconfig eth0 up.

I then run the wp4.sh script as root, however, ping requests to 172.16.42.1 fail and the WebUI is inaccessible.

I manually assign 172.16.42.42 to my eth0 with sudo ifconfig eth0 172.16.42.42, then rerun the script, but it's the same thing :(

Here's ifconfig's output after all this:

eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.16.42.42  netmask 255.255.255.0  broadcast 172.16.42.255
        ether b8:8d:12:56:b0:0b  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 16436
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 22403  bytes 1496944 (1.4 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 22403  bytes 1496944 (1.4 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.110  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::1240:f3ff:fe89:c2e2  prefixlen 64  scopeid 0x20<link>
        ether 10:40:f3:89:c2:e2  txqueuelen 1000  (Ethernet)
        RX packets 191815  bytes 256945237 (245.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 176769
        TX packets 129362  bytes 14277439 (13.6 MiB)
        TX errors 10  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17  

I really hope someone can help out! Thanks in advance :)

[Mr-Protocol]

Try disabling the network manager.

[Phyrne]

Try disabling the network manager.

Thanks for the swift response.

I'm using netcfg, everything's done manually, so I don't think that'll be interfering.

EDIT: Just took a look at the tail of dmesg, it looks like the USB dongle is working fine (I have confirmed this previously, it acts as a standard ethernet port would)

[ 4073.427765] usb 1-1.3: new high-speed USB device number 9 using ehci_hcd
[ 4073.878903] asix 1-1.3:1.0: eth0: register 'asix' at usb-0000:00:1a.7-1.3, ASIX AX88772 USB 2.0 Ethernet, b8:8d:12:56:b0:0b
[ 4073.879011] usbcore: registered new interface driver asix
[ 4139.789336] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 4327.492209] ip_tables: (C) 2000-2006 Netfilter Core Team

Edited September 12, 2012 by Phyrne

[barry99705]

Can you ping 172.16.42.1?

[Mr-Protocol]

If you are manually changing the addresses and "something" is changing it to a 192. or something else. There is probably a network manager running that is changing it back.

[Phyrne]

Can you ping 172.16.42.1?

As stated in my post, ping requests fail :/

[Phyrne]

If you are manually changing the addresses and "something" is changing it to a 192. or something else. There is probably a network manager running that is changing it back.

Not sure if I understand what you mean. The only 192 address I'm using is the IP on my wlan0 interface from my router's DHCP, which is fine. There is no network manager changing anything. netcfg works on a profile basis, I strictly tell it what to do, the only thing I have it doing is connecting to my router's wifi on a static IP. netcfg doesn't mess with the interfaces unless I ask it to :)

[Darren Kitchen]

I hope this isn't the case but we did accidentally have a unit go out recently that wasn't flashed with Jasager properly -- it was still running the stock openwrt from the factory. Assign an IP of 192.168.2.2 and try pinging 192.168.2.1. If it responds, then it just needs some manual flash loving: telnet to 192.168.2.1, as a root password with "passwd", then scp over the latest upgrade.bin to /tmp "scp upgrade.bin root@192.168.2.1:/tmp/" and perform the upgrade on the pineapple with "sysupgrade -v -n /tmp/upgrade.bin".

I really hope that's not the case but if it is, 1) the above will get you situated and 2) please contact me directly at darren at hak5 dot org.

[Phyrne]

I hope this isn't the case but we did accidentally have a unit go out recently that wasn't flashed with Jasager properly -- it was still running the stock openwrt from the factory. Assign an IP of 192.168.2.2 and try pinging 192.168.2.1. If it responds, then it just needs some manual flash loving: telnet to 192.168.2.1, as a root password with "passwd", then scp over the latest upgrade.bin to /tmp "scp upgrade.bin root@192.168.2.1:/tmp/" and perform the upgrade on the pineapple with "sysupgrade -v -n /tmp/upgrade.bin".

I really hope that's not the case but if it is, 1) the above will get you situated and 2) please contact me directly at darren at hak5 dot org.

Hey Darren, thanks for your response. I don't think that's going to be it, I've had my Pineapple for quite some time now (a fair few months) and I'm just getting round to FINALLY playing with it... well at least trying to! I really can't see what the problem is :(

[barry99705]

What happens if you let your adapter get a dhcp address from the pineapple?

[Phyrne]

What happens if you let your adapter get a dhcp address from the pineapple?

Just tried, same thing I'm afraid, nothing :( All looks to go well, it get's the address 172.16.42.42 from the Pineapple's dhcp, but, I'm unable to ping it or access the WebUI :/

[barry99705]

Just tried, same thing I'm afraid, nothing :( All looks to go well, it get's the address 172.16.42.42 from the Pineapple's dhcp, but, I'm unable to ping it or access the WebUI :/

The odds of getting the 42 address is pretty slim. You sure it's a dhcp address?