A few weeks ago when we had 2003 Power outaged that affected several states in the midwest, I lost my DSL connection. I needed access to the internet, and my only option was dial-up. I activated the one month free Earthlink that came with my new Powerbook. Within minutes, I was up and running. I have since decided to keep the service since I travel quite a bit on weekends to rock climbing destinations, and would like to have internet while on the road.
The dial-up is a good idea, but I needed more mobility, and I do have Verizon's wireless service. So I decided that it would be nice to use my existing cell phone to connect while in the car (me not driving, of course). I did a couple of searches on the net and I found some valuable information that later led me to a solution, and I only spent $20.95+tax for a USB data cable for my cell phone.
I've only tried this with T-Mobile, but it should work for anyone. It should also work with other Nokia Bluetooth phones, but that hasn't been tested either.
Pair up your Bluetooth devices the usual way. Set up a new Bluetooth modem port in your Network preference pane. For the modem type, set "Nokia Infrared." Disable "wait for dial tone" and error correction/compression. On the PPP tab in PPP Options, turn off PPP echo packets and turn on TCP header compression. Click "OK" through everything, and enter your PPP info as normal. If you're using T-Mobile internet, set your dial up number as *99# and leave username and password both blank.
That's it, you're all set!
For what it's worth, the same setup will work for an IRDA port to use the phone as an IRDA modem. Only trick is that on the 3650 you need to set up the "connection" of IRDA first (turn on IRDA) and then attempt to connect from the Mac after activating the "modem" program on the phone. The first attempt will fail, but then it'll work fine. T-Mobile documents the whole thing in their support pages except for the Modem program, which is essential to make it work.
Saw this floating around, been using it for a month or so now, works a treat. This is really no good for people that use Internet Connect or any Internet Services that use PPPD, but hey, if you're Ethernet connected, it works fine.
Start by creatings a new pppd file:
% cd /usr/sbin/
% mv pppd pppd.orig
% vi pppd
Put in the following text:
my @args = @ARGV;
s/^defaultroute/nodefaultroute/ for @args;
exec "/usr/sbin/pppd.orig", @args;
Save the file and quit, then make the new file executable with chmod +x pppd, and you're done. Now every session that is started with PPPD will not create a default route. This includes dialup, PPTP, and I would think pppoe for ADSL. Once up, it's just a matter of routing the networks you want over the network. I've configured my PPTP server to assign me the routes, it seems to work fine.
I should begin by saying that Mail.app is a very pleasant mail reader to use. Sadly, it's just not powerful or practical when it comes to really interacting with real world network environments. In particular, it has none of the essential pre-connect or tunneling features of the unix mail readers like mutt. About the only thing one can control is the ports of the servers your using; luckily that is enough when you have root access to you own machine. Anyway, I got sick of needing to manually set up ssh port forwarding every time I wanted to send mail from my laptop when I was off campus, so I set up the following little trick to make it automatic.
I use the shareware product Brickhouse to manage my ipfw host firewall rules on my mac. Here is how to permit your Mac to ping outbound, but also block incoming pings.
Create two custom services:
Action Deny, service Custom Service Protocol icmp, source The internet, Destination my computer. Click Advanced Options and in box icmp Types, put 8, specifying icmp requests.
Directly below above rule, create a second rule. Action Allow, Custom Service, protocol icmp, source The Internet, Destination My Computer, and under Advanced Options, put ICMP types 0. This permits the echo responses back to your computer from pings you send outbound.
So some of you might say "Well ipfw is stateful packet inspection, why do I need to do the second rule?" Because ipfw dosn't keep state on icmp.
As everyone knows, AOL's browser is horrible! It is (finally) based on gecko, but they tweak it and make it unstable (not to mention that if AOL goes down, so does your browser). I do still have an AOL account and I wanted to make AOL open an external browser insted of its own. here's what I found:
Using your favorite text editor, open prefs.js in /Users -> userName -> Library -> Preferences -> America Online -> Profiles -> screenName -> randomString.slt, and add this line:
This works for any protocol which the embedded gecko would normally handle. So change the http to https or ftp or whatever you can think of, and it'll make AOL more usable. Warning: This does bad things if you get lots of HTML mail within AOL; I haven't figured that one out yet...
Being new to OS X, I really appreciate the "print to PDF" option for most apps and have taken to capturing web pages (confirmation screens, on-line documents, etc.) in PDF format. However, frequently I find myself wanting the links in the resultant "web capture" to be clickable. My solution is to save the page as "Web page, complete" in its own directory with my browser (Mozilla) and then I use HTMLDOC (GPL) from the command-line to translate the HTML to PDF via:
htmldoc --webpage -f outfile.pdf infile.html
The resultant PDF will be the HTML file deftly translated into PDF with links (internal or external to the document) that are clickable in Acrobat Reader (or any PDF reader that can read links).
In this forum thread, the topic of direct site-to-site FTP (moving files from one FTP server to another without visiting your local machine first) was brought up, with a few solutions covered. One was to use Fetch, which apparently has this feature built in, but seeing as how I don't like Fetch (UI bugs me, mainly), I came up with a way to do it from Transmit (or any FTP client that lets you look at the "computer" level of your machine to see locally mounted volumes). Check it out:
Mount the source FTP server in the Finder with Command-K (or Go -> Go to Server if you prefer menus).
Launch Transmit (or other FTP client, as noted above).
Navigate to the Computer level with the pop-up menu on the left-hand side of the Transmit window, and select the locally mounted FTP server.
Mount your target (destination) FTP server in the right-hand side of the Transmit window.
Do what comes naturally, and drag your stuff over!
I tried that on a whim just now, and it works amazingly well.
If you want to set up your own internet radio using Shoutcast, here are some instructions:
Follow the instructions at shoutcast.com to download, install, and configure your Shoutcast server. You will need to use the Terminal app to do this, and you'll need the Developer Tools installed as well.
Download MacAmp Lite X (aka MALTX). It's abandonware, and the codes for registation and the plugins power pack are at the bottom of the page (it doesn't matter which version you use).
Follow the instructions in Shoutcast's "Read Me" file.
One of the problems with using WebDAV is that you can't open (GET) files that have any kind of server-side rendering, like PHP files. When you open these files, if you can open them over WebDAV at all, you're treated to the rendered page. That sucks!
Here's where mod_rewrite comes in. Apache comes with a very powerful rewriting engine, which allows you to change the content of just about everything on the fly. We can use this power to turn our dynamic pages into something static to suit our editing needs.
Chances are your WebDAV directory configuration in httpd.conf looks something like this: