1

I have an Android phone that connects to my local area network via WiFi. The LAN consists of a switch and a Debian box that acts as a router, with two interfaces: one external and one internal. For some reason, after updating to Ice Cream Sandwich, my phone can no longer get through to the internet although it can connect to all machines on my LAN.

Any thoughts on what might be causing this routing problem? When I try to access the net from the phone, I see ARP, Requests that seem to go unanswered, eg:

ARP, Request who-has yyz06s05-in-f7.1e100.net tell ...

It seems as if traffic isn't getting routed back to my phone properly. I run my own DNS, one internal and one external.

Thanks for any ideas.

P.S. I downloaded an nslookup utility onto the phone (using cellular network, which does work) and the phone properly gets served DNS from my home network. Also, FYI, other devices connect to the WiFi fine. Finally, the phone MAC address DOES appear in arp -i eth1 output. I am thoroughly confused.

1
  • you did not mention any details of your WIFI AP/router configuration.
    – user23414
    Commented Mar 6, 2013 at 2:39

1 Answer 1

0

Sounds like you are getting DHCP to your internal network vLAN only.

But its definitely a routing issue. Can you set manual route from your phone IP to WAN port?

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .