Connecting to internet using ethernet (client mode)

[markcoker]

So i have a fresh install, default settings. I changed wired to client mode (DHCP).

My understanding this should work but it is unable to access the internet, no ip address is received (eth0).

Router(DHCP Enabled, standard setup other devices work. IP: 192.168.1.1) <-----> WifiPineapple (default settings except now in client mode).

any ideas or hints?

[side issue] Pineapple doesn't detect my access point (wireless) anymore, it used to work fine, no settings have been changed and is in range.

Edited July 4, 2015 by markcoker

[markcoker]

Is client mode working for anyone else? I'm assuming it is but no one has replied in 4 days.

[DataHead]

It does work for me and on the latest firmware. I would suggest before ruling it as something wrong with the pineapple, have you tried it on a different router?

Have you factory reset the pineapple?

Have you tried to verify that all settings on the internet providing are correct, and or on the pineapple?

[markcoker]

other devices are getting dhcp assigned addresses, i haven't tried another router but i currently think its unlikely that it will be the router. cable seems fine, I've tested it.

i have factory reset pineapple, I believe i have all the correct settings, i don't believe there is much required to be set on the pineapple correct? for "normal setup" in client mode.

[markcoker]

[ 197.860000] eth0: link up (100Mbps/Full duplex)

[ 197.860000] br-lan: port 1(eth0) entered forwarding state

[ 197.870000] br-lan: port 1(eth0) entered forwarding state

[ 199.870000] br-lan: port 1(eth0) entered forwarding state

[ 201.860000] eth0: link down

Repeats

config interface 'loopback'

option ifname 'lo'

option proto 'static'

option ipaddr '127.0.0.1'

option netmask '255.0.0.0'

config interface 'lan'

option type 'bridge'

option proto 'static'

option netmask '255.255.255.0'

option dns '8.8.8.8'

option ipaddr '172.16.42.1'

option gateway '172.16.42.42'

config interface 'wiredwan'

option proto 'dhcp'

option ifname 'eth0'

# Failed client mode dhcp setting above (current settings)

# My attempt at static below (its been a while but i believe it should work but it doesnt)

# option proto 'static'

# option netmask '255.255.255.0'

# option dns '8.8.8.8'

# option ipaddr '192.168.1.200'

# option gateway '192.168.1.1'

config interface 'wan'

option proto 'dhcp'

Edited July 7, 2015 by markcoker

[markcoker]

upgraded to 2.3.0, better performance but still same problem.

[markcoker]

anyone have further ideas?

[markcoker]

nothing?

[barry99705]

Doesn't work for me either. I can set a static ip address, but it still doesn't route to the internet. DHCP does nothing.

@DataHead, this is for wired, not wireless client mode. Wireless client mode works as advertised.

Edited August 20, 2015 by barry99705

[DataHead]

I'm not sure why I would have put that here?

Edit:

Never mind,it seems it was in response to his "side issue"

Edited August 20, 2015 by DataHead

[Wabbe]

When trying the wired client mode with dhcp, I can see that my dhcp server issues an ip address. The pineapple does apply the issued address on the eth0 nic, and the correct default gateway is set in the routing table.

Internet access is not working however, nor is the address reachable in any way.

could this be an iptables issue ?

[SnuggleTwin]

I am seeing this exact same issue on my system as well but I used static IP assignment for the Pineapples IP. It can reach the internet but not any device that attaches to it. It is using the Ethernet for connectivity.

[Wabbe]

ok, finaly figured this out. Took me a while since i've never used the Pineapple before (unboxed it yesterday, so wasn't clear how the hardware was configured) ...

Current status : Wired client mode is working as described in the guides.

Description of the problem i had : when using wired client mode with dhcp, the Pineapple received and applied the issued ip address from the dhcp server, routing table was updated correctly, however no inbound or outbound communication was possible over the eth0 nic.

Why it took so long to figure out : i am a complete novice to Pineapple and was not aware of how the nic configurations were done on the box. Since the Pineapple received a correct dhcp address i mistakenly concluded that all was working fine on the network layer. So after a few hours of checking interface configurations and iptables settings i was forced to conclude that the issue had to be on the network layer (didn't like that at all ...).

What was the problem : I was using tagged vlan's on the network switch (this means in fact that the port was configured as a trunk port and not an access port). This is a normal setup in my lab since i play around with lots of virtualised environments that use virtual switches and hence use vlan tagging to seggregate the traffic. So after changing the port to access mode all worked correctly.

Maybe somebody can benefit from the answer provided.

[johnjohnsp1]

I can also confirm that i have the same issue with Mark5 v. 2.4.0 have access to the local device by the IP i set as static but it still doesn't route to the internet. DHCP does nothing. wlan1 is the only way i have to getting to the internet.

[JohnnyConfidence]

This is the same issue I'm having, except we don't have VLANs here. I've got my turtle working properly with DHCP no problem so I know our config should work. Not sure what I'm missing here. Wanted to use it as a drop and deploy box with the ethernet DHCP connection, and then autossh so I could remotely play with wifi in a clients office.

[Scott.W]

This sounds like the reverse problem from what I'm seeing, in that my eth0 works fine in wired client mode through a machine with Internet Connection Sharing. However wlan0 doesn't seem to work when in wireless client mode; it gets an IP within WPA2 sessions on two different models of router, but can't ping the Internet, and wlan0 connected guests can't ping or get to anything on the Internet.

Seems weird that folks on this thread are seeing the exact opposite configs working (and not working) from mine. Maybe there's some kind of conflict between the two client modes...

I will try to factory reset and start with a wireless client mode. If that works for me, I might bet a small amount that my wired client mode may no longer work. Has anyone tried and succeeded in having both modes work in recent releases without having to do a factory reset?

My problem was posted by a team member on a separate thread, but I'm replying here because these issues could be related, and nobody has responded to our original post. Sorry if these turn out to be unrelated issues.

[ARDETROYA]

It does not work for me eather :_(