DataPipe Wireless [Open WiFi Access Point]

I recently came upon a curious WiFi access point branded “Datapipe Wireless”
Although the network is “Open” it required Phone number verification for internet access (Very odd for a US WiFi Provider).


The sign-on page was hosted by, a private domain with an IP address resolving to a CDN network.

Welcome to Datapipe Wireless: A mobile phone that can receive text messages (SMS) is required to access this network. Enter your mobile phone number and you will receive a login code for access. Standard SMS charges will apply.
Sign-on screen when you connect to the network

Immediately after entering my phone number, I received a text from 201-580-2502 with “Authorization Code: ######”.

After connecting, I was taken to a “Cisco Meraki” confirmation page, indicating the brand of hardware the WiFi point is using.


The WiGLE map of the access point “Datapipe Wireless” indicates it’s only on a single block of San Jose.

/h/8913147.html in Google Analytics Spam

The page “/h/8913147.html” is part of a Google Analytics Spam campaign published by
It is likely the uniqueness of the url is utilized to avoid being filted by Google.

I’ve also seen the same html page being used for referrer spam from


iPhone: Number not available. Which number would you like to send the message with?

The following message pops up when you are replying to an SMS or MMS conversation on an iPhone from a number that wasn’t the original recipient number of the message.

Number not available. Which number would you like to send the message with?

For example, if you have two active SIM cards in two seperate iPhones and you are sycning them together using “Text Message Forwarding” you will recieve SMS messages for both SIM cards on both phones. This can be very convenient for business phones. You can get all of your messages on both phones! Unfortunately, if you want to reply to the business-related message conversation using your business line, you will have to switch to that line or you can reply with your “Primary” line, but the recipient of the message will likely see it as a reply message from another number.

uudecode flags / help / command example

[email protected]:~$ uudecode --help
uudecode (GNU sharutils) - decode an encoded file
Usage:  uudecode [ - [] | --[{=| }] ]... [...]

   -o, --output-file=str      direct output to file
   -c, --ignore-chmod         ignore fchmod(3P) errors
   -v, --version[=MODE]       output version information and exit
   -h, --help                 display extended usage information and exit
   -!, --more-help            extended usage information passed thru pager
   -R, --save-opts[=FILE]     save the option state to a config file FILE
   -r, --load-opts=FILE       load options from the config file FILE
                                - disabled with '--no-load-opts'
                                - may appear multiple times

Options are specified by doubled hyphens and their name or by a single
hyphen and the flag character.
If no 'file'(s) are provided, then standard input is decoded.

The following option preset mechanisms are supported:
 - reading file $HOME/.sharrc

'uudecode' transforms uuencoded files into their original form.

The encoded file(s) may be specified on the command line, or one may be
read from standard input.  The output file name is specified in the encoded
file, but may be overridden with the '-o' option.  It will have the mode of
the original file, except that setuid and execute bits are not retained.  If
the output file is specified to be '/dev/stdout' or '-', the result will be
written to standard output.  If there are multiple input files and the
second or subsquent file specifies standard output, the decoded data will
be written to the same file as the previous output.  Don't do that.

'uudecode' ignores any leading and trailing lines.  It looks for a line
that starts with "'begin'" and proceeds until the end-of-encoding marker is
found.  The program determines from the header line of the encoded file
which of the two supported encoding schemes was used and whether or not the
output file name has been encoded with base64 encoding.  See 'uuencode(5)'.

Please send bug reports to: