My DSL died some week or so ago. AT&T had been working in the area (installing new fibre for their fast service called Uverse or some such). I finally got tired of waiting for it to automagically fix and made a service call.
After a while of attempted debug over the phone, it was suggested that I swap to the new service as the “legacy” DSL over copper was kind of going away anyway and the new service was much faster. After another 1/2 hour with a sales person, I was “upgraded” to a Very Fast Uverse package… It was to be installed today.
The install guy came out and “discovered” that the wires didn’t work. I knew that… Then he left and the wires guy showed up. He climbed the pole and reconnected something and my DSL signal was back, but then swapped it over to the new stuff… and I’m waiting for the reschedule of the box guy to come back and plug in my new router.
So Still on the T-Mobile Hotspot.
Getting tired of not using my ‘no wireless dongle’ computers like the Evo, I decided to do something about it. Now, about 5 hours later, I have my Raspberry Pi Model 2 acting as a router to the HotSpot. Then, just for grins, I took my home WiFi router (that had been talking to the old DSL modem) and put it on the Pi (with NAT and routing configured and all).
Yes, WiFi router to wired Pi to WiFi to LTE Wireless…
Well, the only real hangup was that I needed to add a static route to get the return traffic back to the eth0 (wired ethernet port). The rest was more or less ‘cook book’ from a “how to make an Acess Point router from the Pi” page. I did need to swap eth0 for wlan0 in their directions, since I was backwards from the usual desire…
But the bottom line is that I now have the most glorious odd network you could immagin.
My WiFi router connects via wire to the R.PiM2, that then uses a WiFi dongle to talk to the T-Mobile hotspot. So my tablet can connect to the WiFi through the Pi to more WiFi to the T-Moble hotspot via LTE to the world… Such fun ;-)
Oh, and the WiFi router has 4 wired ports in the back in addition to the uplink to the Pi, so my wired boxes can connect through it too… They had been on the old DSL router ports, but it is now powered down…
Tomorrow the landline network box ought to be installed. Maybe.
But for now, I’ve got a full network back and it routes via the hotspot.
If anyone wants the sordid details, I’ll add them…
The post I modeled on was:
I used a different WiFi dongle, so didn’t need those bits, and it came up via Wicd. There was a bit of excitment finding out how to get it to take the password for the HotSpot (one hovers or clicks over a dropdown and it presents the box…)
I also downloaded and installed the hostapd software since someday I am going to make the Pi a “WiFi Access Point” (i.e. WiFi router) but it isn’t needed for this use.
Then there was the issue of the /etc/network/interfaces not being quite right and needing to put a static route in. Why it wanted to send packets out the WiFi when it had an interface up on the wired ethernet with that address range is beyond me, but it did. Oh Well, one IP ROUTE command later and pings made it to and back from the other end of the ethernet wire. Then it worked. Even a reboot and it was all persistent.
This is also decent practice for the eventual end game where I give the Pi 2 WiFi dongles and set it up as a portable isolation boundary router and Access Point. Then, at places like Starbucks, it can sit in a lunch bucket with a battery, descretely giving me a private WiFi with encryption and firewall protection and then sending that traffic on via the host WiFi. Eventually to include an encrypted tunnel to a VPN provider in some other land. So even my “Public” sessions will have encryption and firewalling and NAT isolation. But that is for another day. (Why do it? So that I don’t need to configure the ‘device du jour’ to do the VPN, and know how to quash DNS for advertizing, and… Just one place I always connect to and it sorts out the rest…)