07-27-2010 7:40 AM
So I tried to report this bug to samsung, but all they did was reply with a link to teh bada developers site, so Im not really sure how to submit it. Im posting this here in teh hopes that someone can direct me the proper channels.
Anyway, here's the issue:
When aquiring a wifi network address, the setwork stack seems to use the default class A network mask instead of the DHCP supplied mask. For instance, Im on the 10.10.10.x network at work, and DHCP supplies a mask of 255.255.255.0. When I check net status, the mask has defaulted to 255.0.0.0. This causes problems for me since my DNS is on a different subnet. When I statically address my phone, everything works as it should. Its not an android issue since my buddy has a droid running 2.1 update 1 (same as I am) and his phone works fine.
Thanks for listening - and any info you can offer...
07-27-2010 12:11 PM
I'd try to give samsung tech support a call.
I had an issue with the phone not properly trusting a godaddy certificate in the browser when it was trusted in IE and firefox fine.
AT&T support was clueless and they directed me to call samsung directly.
They were able to escalate my issue to tier 3 support and get it resolved over the phone.
07-29-2010 10:00 AM
08-06-2010 3:34 PM
I have a Samsung Vibrant on T-mobile which is another version of the Samsung Galaxy S platform. It has the same issue you report. In my case it is a class B network, and it ignores the subnet mask.
Have you found a solution?
08-09-2010 5:50 AM
Same issue here - system information reports a /24 mask, but the captivate (on 10.1.2.0/24) cannot communicate with 10.1.1.0/24. Pings error, indicating that ARP requests are not being fulfilled. Definitely a problem with the subnet mask.
08-10-2010 9:17 AM
Glad to hear (well, not really) that Im not the only one experiencing this. Repeated emails and chat conversations fall on deaf ears. I was directed to call level 2 support, however I just dont have the time or inclination to bother at this point.
The only solution is to statically assign the IP address when Im on my employers network. I have a shortcut to the WiFi settings, and I click menu > advanced and toggle the "static IP" check box bepending on my location. I can deal with this until they roll out a fix.
08-11-2010 2:51 PM
I have a working solution...modify the routing table with a more specific route. My Captivate is has connectbot and has been rooted (Superuser Permissions is a application). This lets me modify the routing table with the "iproute" command. With my wireless network being 10.1.2.0/24 (255.255.255.0) and my wired network being 10.1.1.0/24 (255.255.255.0), and DHCP giving my Captivate an IP address of 10.1.2.24 with a mack of 255.255.255.0 and a gateway of 10.1.2.1, running iproute in connectbot to localhost (after running su and granting superuser permissions), the output is:
10.1.2.0/24 dev eth0 src 10.1.2.24
10.0.0.0/8 dev eth0 src 10.1.2.24
default via 10.1.2.1 dev eth0
The second route is the issue - it is the all encompassing classful route for 10.0.0.0/8. This is forcing the Captivate to ARP and not route the traffic through the gateway 10.1.2.1. So you can either ADD a route for the MORE specific class C network (for a single network fix) or DELETE the 10.0.0.0/8 route:
# iproute add 10.1.1.0/24 via 10.1.2.1
# iproute del 10.0.0.0/8
Either fixed the problem, at least until I disabled and re-enabled the Wifi again.
08-12-2010 9:49 AM
Youre right. Something seems to be adding the 10.0.0.0/8 route to the routing table. Ive done a fair bit of searching but I cannot find whats adding it. Anyone know how to add the iproute delete statement to a network script?
08-21-2010 12:48 PM
I've have the same issue...can't connect to WIFI with a non-class subnet (CIDR) mask! It works fine with clasfull subnet.
08-21-2010 2:40 PM
Called Samsung tech support and I have open a ticket with them, ATT said that they don't support wireless issues...on their phones! I will keep postings. I'm gonna to call Samsung in the next week again.
08-21-2010 3:19 PM
One more update. I have configured my home wireless network to 255.255.255.248 subnet and it works great with Samsung Captivate. I have here the Linksys WRT54GS with DD-WRT frimware, at work we have a wireless based on Cisco amd ARUBA radio and it is not working.
- edited 08-23-2010 11:03 AM
Have you guys tried the leaked Beta JH2 or JH3 firmware to see if it fixed your wi-fi subnet mask issue? I have JH3 installed but don't have such wireless network to test. My workplace uses Cisco VPN to secure the wi-fi access.
What is the tool to check the actual subnet mask on the phone?
08-24-2010 5:01 AM
So I downloaded NetworkInfo app and tried it on my home wifi network which has typical 255.255.255.0 subnet mask. NetworkInfo showed my phone's subnet mask is the same 255.255.255.0. So I think the latest JH3 firmware definitely has the fix for wi-fi issue. You just have to wait for next firmware release to get it.
08-24-2010 9:09 AM
I have a Captivate.. any tool I use always shows the netmask as 255.255.255.0, but when I log into the phone via adb it shows the netmask as 255.0.0.0 at the route level.. posted details on xda-developers, but haven't heard anything back there either:
So foxbat, if you are seeing it as /24 via NetworkInfo, it doesn't mean anything.. ;(
Visit these related resourcesView Samsung S10 Info!