[Q] Networking (netmask) issues on a Captivate

8 posts
Thanks Meter: 2
By natecarlson, Junior Member on 5th August 2010, 09:02 PM
Post Reply Email Thread
I've got a shiny new Samsung Captivate (Galaxy S) on AT&T.. working fairly well so far, besides the annoyances with the phone being locked down and the crappy bundled mail client (I've got loooots of email in my imap box, grin.) Phone is still stock; haven't had a chance to root it yet.

In any case, the issue I'm having is that the phone is setting an invalid netmask ( on the wifi interface, instead of the proper one as served by dhcp ( this is preventing the phone from talking to other devices in 10/8.

Here's the DHCP response sent to the phone by my DHCP server:

      Client-Ethernet-Address 00:26:37:xx:xx:xx
      Vendor-rfc1048 Extensions
        Magic Cookie 0x63825363
        DHCP-Message Option 53, length 1: ACK
        Server-ID Option 54, length 4:
        Lease-Time Option 51, length 4: 86400
        Subnet-Mask Option 1, length 4:
        Default-Gateway Option 3, length 4:
        Domain-Name-Server Option 6, length 8:,
        BR Option 28, length 4:
        RN Option 58, length 4: 43200
        RB Option 59, length 4: 75600
        END Option 255, length 0
        PAD Option 0, length 0, occurs 4
As you can see from the above, the phone was assigned with a netmask of I finally set up the android sdk, and fired up a shell with adb.. here's what it thinks its ip is:

$ ifconfig eth0
eth0: ip mask flags [up broadcast running multicast]
even odder, the properties on the phone has the correct netmask; output from 'getprop':

[]: [3350]
[dhcp.eth0.reason]: [BOUND]
[dhcp.eth0.dns1]: []
[dhcp.eth0.dns2]: []
[dhcp.eth0.dns3]: []
[dhcp.eth0.dns4]: []
[dhcp.eth0.ipaddress]: []
[dhcp.eth0.gateway]: []
[dhcp.eth0.mask]: []
[dhcp.eth0.leasetime]: [86400]
[dhcp.eth0.server]: []
I suspect a firmware bug, but don't know for sure - anyone run into this before?

Appreciate any thoughts!
24th August 2010, 06:14 PM |#2  
Senior Member
Thanks Meter: 23
Same issue here. I posted about it here and on the ATT forums and sadly nobody has any suggestions other than reporting the bug to samsung. I did a bit of poking around in the console grepping but didnt find any files. Im just gonna weather the storm and wait for the next firmware to be released. I have a shortcut to wifi settings and I just toggle the "static ip" option as needed.
24th August 2010, 06:16 PM |#3  
OP Junior Member
Thanks Meter: 2
FYI, there's also a post on ATT's forums about this.. I'm not allowed to link to it, but a Google search for "Samsung Captivate WiFi DHCP netmask issue" will get you to it..
7th October 2010, 07:02 PM |#4  
Junior Member
Flag Pinehurst NC
Thanks Meter: 1
Generally I dislike reviving old threads, but this appears unresolved and I've been encountering it on my Samsung Vibrant.

Can anyone confirm whether this happens with Froyo, or other Eclair-based handsets, or is it specific to Android 2.1 on Samsung GalaxyS?

When the Wifi DHCP assigns an IP in the 10.x.x.x block, (which is actually assigned with a /24 netmask) android puts the IP on the interface TWICE, with both /24 and an incorrect /8 subnet mask. ("ifconfig" is essentially a legacy command from linux kernel 2.2 era, when multiple IPs required aliased interfaces - with two IPs on one interface today "ifconfig" will only show the first one. Since kernel 2.4 days "ip" is the preferred tool)

$ busybox ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: usb0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 5e:38:e9:7b:aa:6d brd ff:ff:ff:ff:ff:ff
3: tunl0: <NOARP> mtu 1480 qdisc noop state DOWN
link/ipip brd
4: gre0: <NOARP> mtu 1476 qdisc noop state DOWN
link/gre brd
30: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 5c:da:d4:09:fb:f3 brd ff:ff:ff:ff:ff:ff
inet brd scope global eth0
inet brd scope global eth0
inet6 2001:470:e130:98:5eda:d4ff:fe09:fbf3/64 scope global dynamic
valid_lft 2591705sec preferred_lft 604505sec
inet6 fe80::5eda:d4ff:fe09:fbf3/64 scope link
valid_lft forever preferred_lft forever

This causes me significant problems, as is the wifi subnet, but 50 other 10.x.x.x subnets exist on the local network, and because it erroneously applies a /8 mask on the local interface I'm unable to reach anything on the 10.x.x.x networks outside of 10.200.10.x. (I have to manually go in and remove the first IP with the /8 subnet)

(Aside, as you might notice it correctly autoconfigured an ipv6 address, with 2001:470:e130::1/64 gateway running radvd - now if only apps like web browser understood ipv6...)

Post Reply Subscribe to Thread

android, netmask, network, wifi

Guest Quick Reply (no urls or BBcode)
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes