Tag Archive for 'Networking'

Ubuntu, FreeNX, and Thin Pipes

My mother-in-law has been fighting the battle of thin pipes for as long as she has been paying for Internet access and every year SNET-SBC-AT&T sends her a letter that gets her hopes up that the DSL fairy set up a repeater to light up her neighborhood. Each and every year she learns that there is no DSL fairy. So I’ve been trying to think of every concievable method to get her broadband for a reasonable price. Comcast wants some $70 a month and the municipal wi-fi in Hartford went dark as soon as it went live all of which leaves her living online at the brutal speed of 50.0 kpbs. Yesterday, though, I might have come up with a slightly workable solution that at least gives her the feeling of faster speeds: a terminal server running on my 6MB pipe.

After looking at various implementations, including LTSP, I settled on the stupid simple setup of FreeNX mainly because it was easy and made use of my OpenSSH server. The Ubuntu wiki had fairly solid instructions and the only challenge I had was adding Seveas’ Packages–most of the mirrors were handing out 404’s. For myself, the benefits are that I do not need to run Putty + TightVNC anymore as the FreeNX runs on top of SSH but the downside is that the FreeNX client needs to be installed on the machine in a Windows environment so I’ll need to look at alternatives including QEMU + Puppy Linux.

In testing I found the performance to be astounding if I am on a broadband connection responding with barely any lag and the same is true for my mother-in-law’s connection except when surfing. Surfing, obviously with all the screen refreshes, is only a minimally faster experience, but possibly with some tweaking we can squeeze a little more performance out of it. The goal is to make little things like online banking and shopping a little less painful with pages timing out because her connection is taking to long to pull data down and with our quick test FreeNX does seem to alleviate this problem a smidgen.

If anything, FreeNX gives me a better tool to hit my server and do work GUI style, like tacking my miserably tagged music collection, with a fast connection it is a blissful way to connect and do a little work.

ddclient, Ubuntu, EasyDNS, and You!

So yes, this is stupid simple and I’ve put it off far to long–world renown for my sloth–but here’s the quick lowdown for ddclient.

  1. Grab and install either from Synaptic or apt-get.
  2. Walk through the little install wizard then do it all over again: dpkg-reconfigure ddclient. You want to make sure it runs as a service and monitors changes in ppp–something that the install wizard doesn’t cover.
  3. Then tweak /etc/ddclient.conf:

    # Configuration file for ddclient generated by debconf
    #
    # /etc/ddclient.conf
    pid=/var/run/ddclient.pid
    protocol=easydns
    use=web
    server=members.easydns.com
    login=yournamehere
    password=’password’
    *.your.domain

  4. Restart the service: sudo /etc/init.d/ddclient reload

One of the things I noticed when fiddling with ddclient was that it doesn’t work so well with wireless cards.  Sounds stupid, but I was testing in on my laptop and never got very far because it wouldn’t update the IP address so my sloth settled in and I never took the initiative to test it on a box with a wired connection.

Considering The SOHO

When not scraping, sanding, painting, and generally following orders from Management, my time is backfilled and my bank account is padded by doing help desk work on the side, usually cleaning up Windows boxes that have been neglected and abused as well as the occasional hardware upgrade for the tech phobic, but the best work are the small offices that I maintain as these are the places where the dollars need to be stretched for the greatest return.

At the moment I have one client with a very small office that when set up was configured like a home network with an emphasis on ease of use over security. The result is two Windows 2000 PCs and one Windows XP laptop joined by a password free Workgroup and connected to a cable modem through an aging Linksys router. The PCs themselves are getting long in the tooth having been purchased some six years ago and to add insult to injury he has been battling virus outbreaks with increasing regularity. I make sure that he stays on top of definitions and patches but the network itself is inherently insecure and added to that both machines are logged into as local admins.

Current Configuration
Plain vanilla SOHO

He has given me a list of things he would like to see implemented when or if he proceeds with upgrading or reconfiguring the existing network including somethings I would file under necessity: automated backup plan, network firewall solution, and centralized and secure file sharing. While 2000 is still a serviceable OS, I’m leaning towards recommending that he purchase two machines to replace those boxes and to go with XP Professional, skipping Vista for now. Surprisingly, I’m not recommending he deploy Ubuntu, SUSE, or Fedora for the simple fact that it might be too much change for him and his employees and XP, when configured properly, is a fairly rock-solid OS.

The first possible configuration maintains the general layout of the network but would allow for remote administrative access as well as centralized file sharing and automated backups by redeploying one box to act as an SSH and file server.

Configuration One
Slightly more complicated…

The purple lines represent an SSH tunnel, the red is vnc, and the blue for file sharing and backups, and you can plainly see what my choice for the server OS. This configuration is most likely the one he will sign off on as the topology closely resembles what he has grown accustomed to but I do have a second configuration in mind to further enhance security.

Configuration Two
Just a little more complicated…

The inclusion of the Smoothwall appliance will go a long way in enhancing security, particularly if I shift tactics and push that they log into their PCs as regular users and reserve the admin account for special cases. The Smoothwall appliance can also be deployed on the remaining 2000 PC to make better use of the hardware with the only cost being replacing the router with a switch.

All things considered, I think that the two options make the best use of his money and could go a long way in enhancing the security of his network as well as functionality. We’ll see what he goes with.

¡Samba es muy lenta!

Because I am so lazy I have only just gotten around to setting up a Samba share on the server so the lone XP machine in the house can partake in the festivities that all the other Linux boxen do. Easy but totally not worth it considering the performance is akin to waiting for puddles to evaporate during a rain storm. Yeah, it is that slow. anyway, here are the simple details:

sudo smbpasswd -a valid-local-user
sudo nano /etc/samba/smbusers

Add the following: system_username = “network username”

Edit /etc/samba/smb.conf and add the following:

Find and comment out: ; security = user

Add the the following below it:
security = user username
map = /etc/samba/smbusers

At the bottom of the file add:
[Your-Share-Here]
comment = Name-It-How-You-Like
path = /path/to/folder/
public = yes
writable = yes
valid users = valid-local-user
create mask = 0700
directory mask = 0700
force user = nobody
force group = nogroup

Reload the service: sudo /etc/init.d/samba restart

Then be amazed at how SLOW it is. I heartily recommend Samba only be used to share little, itty-bitty pieces of data, anything else and you’ll grow old waiting.





Creative Commons Attribution-NonCommercial-ShareAlike 3.0 United States
Creative Commons Attribution-NonCommercial-ShareAlike 3.0 United States