LOL!Princeton is just lazy...!
No.
If you're going to sell a "magical" web-browsing device, you had better be damn sure it works with all standard protocols.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Princeton University Details iPad Wireless Networking Issues
- Thread starter MacRumors
- Start date
- Sort by reaction score
No.
If you're going to sell a "magical" web-browsing device, you had better be damn sure it works with all standard protocols.
You do realize both I and locust76 were joking, right...?
As I said, Macs have had similar network issues before.
Except colleges are real life and I would imagine that college students are a decent chunk of Apple's customer base these days.
I don't think this is a problem that's limited to iPads - I have occasional issues with Macs, iPhones, iPod touches and Airport Expresses fighting over IP addresses at home (and have had for as long as I can remember). I've actually moved to static IP Addresses for a lot of the gear at home to try and get around the problem.
Normally, the first indication is a message on the Mac screen complaining about a duplicate IP address on the network. Interestingly, when it's happened on an iPod touch, it simply looks as if it's dropped off the network (the network status indicator disappears), which is similar to what people have been reporting with iPad connectivity issues.
Normally, the first indication is a message on the Mac screen complaining about a duplicate IP address on the network. Interestingly, when it's happened on an iPod touch, it simply looks as if it's dropped off the network (the network status indicator disappears), which is similar to what people have been reporting with iPad connectivity issues.
If this is the issue that causes that then I guess that is what I'm seeing on my home network, I'll have to look into it.
Keep in mind, you can add an external BlueTooth keyboard. Or get the official iPad keyboard dock (which might not be as portable as Apple's wireless keyboard).
However, if you're a "serious" computer user/writer, I don't think you'd want an iPad as your primary machine. The iPad more or less needs to sync to a "real" computer to keep your files backed up. If you don't have any computer right now, yeah, get the MacBook or netbook (and avoid the Princeton campus).
This is a really bad problem. No excuse for this. It could cause a lot of issues on a corporate or campus wi-fi network where the same users are spending a lot of their time online. Probably wouldn't be a big problem at a place like Starbucks, unless the iPad user is there every single day. This is a stupid gaffe by Apple that defeats the purpose of DHCP. I wonder if Steve will come out and start publicly villainizing DHCP the way he does to Flash.
There always seems to be "work-arounds" when it comes to Apple products nowadays. I remember having to download all these different programs to make Windows 95 and XP useful. In OS X, it "just worked". So, I switched and never looked back. Until now.
With the iPhone and the iPad, it isn't like this anymore. Usually the user has to download some App from the App Store that has some convoluted "work-around" due to Apple's restrictions. I think Apple is going backwards. It doesn't "just work" anymore.
OH WHAT KINDA BS IS THAT???!!!! you all are so full of ****. "apple's qa is horrible".. are you kidding???? apple's qa is second only to maybe nasa. everything needs public vetting, every system has unforseen snafu's.
what a bunch of know-not losers there are on this board.
LOL!! that's right. i'm flaming. can't help it. you guys bring it out of me. such a bunch of hot air deserves a fart.
Our DHCP setup at the college I work for is a lot like yours - it remembers the device that an IP address is assigned to and continues to give that IP to the same device when requested. So while this is definitely Apple's problem to fix, we would be far less likely to run into this problem. I'm sure that Princeton has a good reason for handing out IPs the way they do, but their setup does play a role in this issue.
Sadly I think most people do. They quickly dog whatever company tries to innovate things because they can't see the possibilities a piece of hardware can do until someone shows them the must have item/app on said device. But when a company shows no innovation just raw hardware stats they salivate like rabid animals.
Playstation 3 - it's too expensive, we didn't ask for blu-ray, we already have a PS2, it's hard to program for.
iPhone - why is apple even bothering to compete with cell phone makers such as nokia.
Playstation 2 - has jaggies, too expensive, hard to program for, we didn't ask for dvd player to be included.
The quotes I made up but seem to be largely the same complaints over and over. The internet forums are riddled with them. The only thing that really changes is the "product" someone is complaining about. It really doesn't matter what "product" it is either. The naysayers will always outnumber the ones who actually enjoy their purchase.
People in general just need to mature. If you don't like it don't buy it, don't watch it, don't read it, or don't listen to it. Simple as that. No one is forcing it down your throat. Sorry losing focus and going off on an anti censorship tangent.
Did you type this with a straight face? Sorry, but I have a hard time believing that Apple's QA is superior to the military & car manufacturers, just to name a couple. And you implied that it COULD be superior to NASA's QA. My God.
I'm at the University of Michigan and I talked to our IT about the iPad and they've had ZERO problems with the iPad and the wireless network. Princeton IT has a bug up their you know what.
your god? don't take things so literally. perhaps i exaggerate slightly to make my point. if you want, you can do a list of american companies ranked by subjective assessment of QA efficacy. we can discuss it. but for the record, i would put apple's QA above most of the military and many car manu's as well, yes.
Fix needed today please Apple.
Most likely because of the nature of Princeton's network setup. I work at a different university, and our DHCP environment is set up in such a way that the DHCP servers remember what device an IP address was assigned to, and will reuse the same IP as much as possible.
That is not the point. The DHCP RFCs are very clear on how the lease timers are supposed to work. True you can implement MAC caching for reassignment, but that is does not negate the DHCP release spec.
This is BS Qa=A from Apple and needs to be fixed today and patched tomorrow.
It has been tested quite extensively in the themed bars around the SF area...
Unfortunately the engineer was so sozzled he can't remember how he solved the problem.... or where he left the iPad.
Ok, what we've got here is what's known in programming/testing as an 'edge case'. The reason we're seeing it on a device of this type where we wouldn't see it on a laptop or desktop is that the iPad/iPhone/iPod Touch are commonly turned on and off at a whim. People don't tend to do that with a laptop, and almost never do that with a desktop.
Princeton's setup is more aggressive than normal.
A bug exists in the network driver for the device.
When the DHCP server attempts to ping the device to be certain the IP isn't still in use, the ping goes unanswered because the device is *off* at that particular moment.
Princeton's DHCP server reclaims the IP even though a device (incorrectly) currently thinks it still has it because the device didn't answer the ping.
This issue is probably an instance of an optimization which looked good on the surface, and passed through QA testing because their test environment isn't quite so aggressive with the expiration/reclamation times. (My home network, for example, gives 2 day leases, which would make this scenario extremely unlikely to occur.)
Princeton's setup is more aggressive than normal.
A bug exists in the network driver for the device.
When the DHCP server attempts to ping the device to be certain the IP isn't still in use, the ping goes unanswered because the device is *off* at that particular moment.
Princeton's DHCP server reclaims the IP even though a device (incorrectly) currently thinks it still has it because the device didn't answer the ping.
This issue is probably an instance of an optimization which looked good on the surface, and passed through QA testing because their test environment isn't quite so aggressive with the expiration/reclamation times. (My home network, for example, gives 2 day leases, which would make this scenario extremely unlikely to occur.)
Hey buddy, where in my post did I mention QA? Learn to read...
i was lumping that in on top of my response to you. buddy.
I basically agree with you but you do realize you're going to get slaughtered by the others on this board, right? lol
That is not the point. The DHCP RFCs are very clear on how the lease timers are supposed to work. True you can implement MAC caching for reassignment, but that is does not negate the DHCP release spec.
This is BS Qa=A from Apple and needs to be fixed today and patched tomorrow.
Yep. iPads should be banned from the network until then.
Plus, since only someone with an IQ below 60 would buy an iPad to use on campus, all iPad owners should be banned from places of higher learning.