we run a little "router" device (~ raspberry pi) that provides an ad-hoc wifi (free / unsecured).
On the same device, there is a webservice with login page. All unauthenticated calls are reditected to that login page.
Somehow, all devices now believe that this is a wifi-login page.
(Androud, Windows and MAC) are asking the user to log into the Wifi (similarly as you do for free wifi in malls etc.).
The ad-hoc wifi is not online, so all the connectivity checks do not work:
Apple iOS and macOS: captive.apple.com
Microsoft Windows: www.msftncsi.com/ncsi.txt
Google Android and Chrome: google.com/generate_204
The domains of that probe are not served by our service. yet, we see Devices try to access our local HTTP service and do these checks.
Related
We have developed a mobile app using Meteor+Ionic2. We use our internal NodeJS server which is not in internet zone. We got the app deployed to our enterprise app store which enables AirWatch VPN tunneling to get the access to server in intranet zone.
Everything works great when tested with iOS device level using "F5 Access" VPN when deployed using Xcode or enterprise app store with NO VPN tunneling . But when download the app from our enterprise app store which does per-app VPN using AirWatch VPN Tunneling, iOS app gets stuck at the splash screen. It is not seems to call any client side or server side code of Meteor+Ionic2.
When redeploying it using development distribution, It seems to be stays at about:blank and not going to localhost and getting "Failed to load resource" error in about:blank.
The same AirWatch VPN Tunneling works great in Android. This issue seems to be happening only in iOS. I checked device level logs and also AirWatch VPN tunnel logs which donesn't report any errors.
I'm not sure whether Meteor+Ionic2 supports AirWatch VPN Tunneling for iOS as none of framework codes get called. Is there anyway to debug the enterprise distributed app? Is VPN-Tunneling not supported in iOS app development using Meteor?
Thanks,
Annadurai.
The root cause of the issue seems to be AirWatch config which causes the localhost to be appended with domain name like localhost.mycompany.com. As AirWatch couldn't fix this issue, we dropped plan of using AirWatch VPN tunneling.
I have an app on mobile which runs through VPN connection . I am doing performance testing using jmeter on desktop for which I have done necessary configurations but http proxy server does not record my http requests
Can anyone help on this
JMeter and mobile device need to be on the same network in order for JMeter to be able to capture mobile device traffic. So the easiest option would be connecting desktop to the same VPN and using VPN-originated IP addresses.
You will also need to install JMeter's self-signed certificate, the relevant file is ApacheJMeterTemporaryRootCA.crt, it's being generated in JMeter's "bin" folder when you start HTTP(S) Test Script Recorder. The easiest way to get the certificate installed onto mobile device is sending it to yourself by email, opening the email on the mobile device and following system dialog to install the certificate.
References:
HTTPS recording and certificates
JMeter Proxy Step by Step
There is also an alternative solution for recording native and hybrid mobile applications traffic. Using it you won't have to bother about proxies and certificates. As a little bonus, this 3rd-party JMeter Cloud recorder has "SmartJMX" mode with automatic correlations of any dynamic parameters so you won't have to extract them yourself. See How to Cut Your JMeter Scripting Time by 80% guide for details.
I need to make an application where a mobile web app can connect to a local web service in a LAN. For example, several locations are running this web service on their own local server. When someone with the mobile app comes into the location they can open it up and it will somehow be able to connect to that local webservice through WiFi. The mobile app won't know the IP of that webservice ahead of time. Any thought on how to go about this? This will be a .NET webservice and HTML5 app but I don't think that matters.
As mentioned in the comments you will probably have to make it configurable by the user as the will ultimately need the address of the server.
There is however another approach that you can take. Develop a small multicast/udp service that broadcasts the web service address every 10-30 seconds. In your android application register a broadcast receiver that responds to the network connectivity status and runs in the background.
This service on the Android service will pick up the address from the UDP broadcasts and then configure the application.
I have downloaded the sample application for Push Notification Module.
At home, with my personal WiFi the application works fine and notifications reach the device as expected.
However, at work, with my company's WiFi, the application is correctly installed in the device, the access to the worklight server occurs but notifications don't reach the device when I send them.
I took a look to the 'Inbound Rules' in the 'Windows Firewall with Advanced Security' panel and the inbound rules for eclipse.exe are defined as follows:
Enabled: Yes
Local Address: Any
Remote Address: Any
Protocol: UDP
Local Port: Any
Remote Port: Any
Allowed Users: Any
The strange thing is that some days ago I've done it here at work (worked however unstable, sometimes worked sometimes not) but, I have no idea why, it stopped working at all.
I think that would be something about permissions or ports, I don't know, because as I said, at home works fine.
Any idea?
Talk with your IT department and have them make sure that all required ports are open and accessible to incoming and outgoing requests, as detailed in the Push Notifications training module.
Page #44
http://public.dhe.ibm.com/software/mobile-solutions/worklight/docs/v610/09_04_Push_notifications.pdf
As the title suggests, I have been unable to connect (and pair) the google tv remote app with a Google TV emulator running on Ubuntu. I understand that the emulator runs on its own sub-network and therefore has to use redirections in order to connect with anything outside its network.
I have tried the following:
1) Remote control app running on device,
2) Remote control app running on android emulator on same machine as the google tv emulator (For this I had to use a modified version of the app, since there is no wifi on the emulator and the official app would close without wifi)
In configuration (2) I have somehow managed to establish a connection with the tv emulator by using telnet and redirection commands (see this). However the app fails while trying to establish pairing as it tries to build a socket at a new (random) port which is not redirected (I assume).
I would firstly like to know how to find which ports to route for the google tv remote app to successfully connect with the TV emulator. And then how would the pairing action succeed in connecting the controller with the TV emulator through a new socket (which I couldn't redirect)
Any help will be greatly appreciated.
This feature is not supported. If you are working on a GoogleTV application that requires this feature, please fill out the form at goo.gl/tVw4i.