WFT-E2 II incompatable with IPAD2 (IPAD1OK)?

[TheBrew]

Interesting. Same firmwares and iOS version here - and when I configure the ad-hoc I do it manually..

The issue is, that the ad-hoc network jams after anything from a couple of re-focuses (shutter button half-way) to maybe 50. The solution is to disable Wi-Fi on the iPad and turn it on again.. You have never had this problem?

When I'm through my dinner and the (EDIT) The New iPad keynote, I'll write a step-by-step post on how I set my ad-hoc up, so you can tell me if you do something differently.

Thanks for the info so far. :)

[TheBrew]

Hm. Did I just find the reason for this, or have I been lucky for the last half hour..

If this is the solution, cool: have the ad-hoc network be encrypted. (Well, why wouldn't you.. But during my tests earlier, I've left it unprotected - just to keep causes for errors out. ...maybe that was my cause of error)

With WEP encryption on, 10 key pass, it hasn't failed yet.

[TheBrew]

A good night's sleep. Got up and tried again - failed after a couple of seconds. Hm. Could we compare settings?

Here's how I set it up (manually):

WFT settings -> Set up -> LAN settings -> Pick a free Set -> Change
Protect settings: Off
LAN type: Wireless
TCP/IP:
IP address set.: Manual setting
DNS server: Disable
IP address: 192.168.1.1
Subnet mask: 255.255.255.0
Gateway: 0.0.0.0
Security: Disable
FTP server:
Target server: 192.168.1.5 / 26000
Login password: snitch / superuser pass
Target folder: /
Directory structure: Default
Overwrite same file: Enable
Passive mode: Disable
Proxy server: Disable
Wireless LAN:
SSID: canon-adhoc
Advanced settings:
Networktype: Ad hoc 11g
Channel: Auto
Encryption: WEP
Key index: 1
10 hexadecimal char.: 012345679

iPad: Auto-join, Static IP
IP Address: 192.168.1.5
Subnet Mask: 255.255.255.0
Router: 192.168.1.1

[RobT]

Hi There

The only important difference I can see is that I set mine for a fixed channel rather than auto, in fact I used 11.

Everything else the same with one other exception in that I defined my own IP address range as the one used (192.168.3.nnn/24)

Rob

[TheBrew]

Thanks Rob,

Tried changing my channel to be fixed at 11, choked immediately. ...but after toggling the Wi-fi off and on, it hasn't failed..

I'm beginning to see a pattern: This happens whenever it's been a while since I joined the WFT ad-hoc network. Once I do that, it fails within seconds / a few minutes. After a Wi-Fi toggle, it seems to stay stable.
Since you're not having any problems with the exact same setup, I'm thinking it can be revisions of the Wi-Fi chips / the WFT grips. Will be interesting to see how things work with "The new iPad".

[RobT]

Hi

Mine has been reliable so far, just remembering the steps is sometimes inconvenient if moving from an AP area to an AdHoc setup and back.

But worth the effort

All the best

Rob

[Anzuoni]

i have a Canon Mark IV, with a wfte2a, ipad2 and verizon mufi jetpack.
i have connected my ipad and the wft to the wifi generated by the jetpack, i have set up the wft and pointed it to the ip address and port indicated by shuttersnitch, i have also enabled the privacy separation on the jetpack prefs, and still shuttersnitch does not appear to be ready to receive, the connection fails. i am generally able to send to an internal ftp through the jetpack without issues, the problem seem to be within shuttersnitch, help would be much appreciated!

[MadDawgJ]

Privacy separation should be off, it will block access from one device to another on the jetpack.

[TheBrew]

I promise you, ShutterSnitch is ready to receive if you're inside a collection.

The issue is probably that no one comes "knocking on the door".

Try going into the ShutterSnitch settings, scroll all the way to the bottom, and enable the "Traffic Inspector". Then enter a collection and you'll see a window that logs the traffic. Now try taking a photo and see what the log says. (And feel free to copy/paste the result here).