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.) In any case, the issue I'm having is that the phone is setting an invalid netmask (255.0.0.0) on the wifi interface, instead of the proper one as served by dhcp (255.255.255.0).. 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: Code (Text): Client-IP 10.20.0.120 Your-IP 10.20.0.120 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: 10.20.0.254 Lease-Time Option 51, length 4: 86400 Subnet-Mask Option 1, length 4: 255.255.255.0 Default-Gateway Option 3, length 4: 10.20.0.254 Domain-Name-Server Option 6, length 8: 10.20.0.254,10.20.0.1 BR Option 28, length 4: 10.20.0.255 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 10.20.0.120 with a netmask of 255.255.255.0. I finally set up the android sdk, and fired up a shell with adb.. here's what it thinks its ip is: Code (Text): $ ifconfig eth0 eth0: ip 10.20.0.120 mask 255.0.0.0 flags [up broadcast running multicast] even odder, the properties on the phone has the correct netmask; output from 'getprop': Code (Text): [dhcp.eth0.pid]:  [dhcp.eth0.reason]: [BOUND] [dhcp.eth0.dns1]: [10.20.0.254] [dhcp.eth0.dns2]: [10.20.0.1] [dhcp.eth0.dns3]:  [dhcp.eth0.dns4]:  [dhcp.eth0.ipaddress]: [10.20.0.120] [dhcp.eth0.gateway]: [10.20.0.254] [dhcp.eth0.mask]: [255.255.255.0] [dhcp.eth0.leasetime]:  [dhcp.eth0.server]: [10.20.0.254] I suspect a firmware bug, but don't know for sure - anyone run into this before? Appreciate any thoughts!