Discussion Locked

A challenge to the Linux Users of the World

0 helpful
242 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This is page 3 of the discussion. Read the opening post

242 replies

by dumphrey

should only be for the decent cards. there are tons of crappy network cards out there I would not want to support on a server. They do need to communicate more then a workstation (arguably), but they also need to be as stable as possible, more so then a workstation (once again this is arguable).

As for rushing the Beta, I would not be surprised. the Vista Beta was junk, but RC1 was nearly usable. By the time WHS products are released, in conjunction with hardware control, it should be a usable system.

by dumphrey

at the finished product from a user point of view, then the lack of linux frienlyness is not important, as the final installed, config product is what the end user would receive, with a few boot up scripts to input some info and set up vpn etc. Comparing the entire install procedure is only fair if you installed windows server 2003, and then added in the products needed to create functionality, and removed the unwanted parts.

I do realize that a full set up of Debbie is a chore, but if some smart programmer came along and made it into a single disk install (ala KnoppMyth) or a specialized live cd (ala Dynabolic) then the install bother would be over.

by doug

I think you might be missing the point of
linux. There is no one way of doing things
like there is in the Microsoft world.

Many years ago when I set up a mail server,
there was only one way to go. Exchange.

With Linux there's a dazzling array of mail
software that can be used. Right now I'm
using KMail+Dovecote+postfix, which is not
a combination I would have thought to end
up with.

Linux gets a bad rap as far as
userfriendleness. I'm finding Linux much
more user friendly than Windows. I
particularly like the way I can adjust font
sizes everywhere.

Configuration can be a pain. Right now I'm
configuring postfix using Webmin, vi, and
monitoring a log file with "tail". Is this
harder than using the purely GUI Exchange?

Well, when I hosed postfix I just copied
the text configuration files back.
Sometimes when you hose Exchange you have
to reinstall. And I've just about
eliminated all my spam, something I never
managed to do with exchange.

by retro77

I read about 90% of the posts. Some got too deep into subjects I dont care too much about [databases].

Good work. I look forward to a finished "cookbook". I too am not upgrading to Vista and I tell everyone around me to not upgrade yet as well.

I am looking to be 100% Linux by the end of the year. Is Debbie the girl for the job? I dont know, we'll see. Might be Suse or the African cousin: Ubuntu.

My hardware: Shuttle mini PC with an AMD 64 3000+, ATI Radeon 9600 All In Wonder. it currently my gaming PC [GuildWars] and my TV/DVD player/recorder.

by apotheon

Thank goodness for people who inform me outside of TR when something that would interest me here at TR occurs. Since TR changed its email alert format, I haven't been able to use them to keep up with discussions at all.

Anyway . . . sorry to hear things didn't just magically fall into place, but as you've made clear, you at least didn't expect that from the Linux side of the story. It's good to have realistic expectations.

Like you, I intend to produce a free/libre/open source software home server setup. I'll probably cobble together a set of scripts to automate the setup process with FreeBSD, though, rather than producing a cookbook for Debian.

I'm sending you an email (via TR "peer mail", aka "private message") about the disposition of that cookbook, by the way. Look for it in your inbox, I guess.

by retro77

can you post it to the general public? I am looking for such a solution and would love a jump start. I hate re-inventing the wheel.

by apotheon

Are you talking about my private communication with Xwindowsjunkie, or my progress with FreeBSD? If the former, he's welcome to post what I said to him if he likes, but I figured I'd start it out privately as the more appropriate way to start with the suggestion I had for collaboration. If the latter -- well, I haven't really started doing much for the FreeBSD variant, so there isn't really anything to post yet. I do intend to post some mention of it here if/when I get around to getting something useful done, however.

by retro77

I just like to see what combinations have worked for others to replace Windows in the home/SOHO/small business sector.

by apotheon

I'm using both FreeBSD and Debian GNU/Linux in my SOHO network environment for servers and workstations. Because I know exactly what I need and (generally) exactly what I'm doing, I can just set up a server to handle my needs with relative ease. What I do isn't exactly suited to a UHS (Unix Home Server) setup, however, as I don't use GUI or web-based administration, don't use a system that automates setup for common server tasks, and so on. I make use of my understanding of how to configure these servers from scratch, and tailor each server to its specific job.

For a UHS project, I intend to automate a lot of things, so this would be a significantly different approach. Thus, while I've done a lot with Debian and FreeBSD that has worked quite well for me, I have not done much of anything along the lines of what this discussion has addressed.

by grax

In a Windows Secrets Newsletter published 17/05/2007 the highly respected Woody Leonhard said:
?As a card-carrying member of the 'Association of Windows Victims,' I never believe Microsoft's hype about software that's still sitting in the hopper.

But I've been playing with the beta version of Windows Home Server for quite a while, and even though the final product isn't due out until the end of the year, I'm impressed.?

I?ll not bore you with all the chaff, but he finishes with:
?Rumour has it that the first WHS machines will include a substantial amount of hard disk space, but sell for only about $500. If that prediction comes true, there's a Windows Home Server in my future. Bet there'll be one in yours, too.?

From the experiences described in this discussion, I think there will not be one in my life. Debbie will do. The question is should one disabuse Woody? Of course, his Kraken may just be a Triffid.

by xwindowsjunkie

It would be interesting to find out if he did a download or did he get a pre-configured system from a OEM?

As a consumer product WHS RC1 is NOT consumer mass-market material. As a slightly stripped down Win 2003 Server, its a home server geek-toy of fairly incredible power for a home market product.

I limited my test to the user interface that any user would have easy access to. I would not expect the typical Joe Sixpack to have a clue as to how to configure the high power functions in Win2K3.

My guess is that Microsoft is offering the Windows Home Server as a "platform" that it expects OEMs to configure with their own interfaces and methods for the consumer market. You'll likely see packages with graduated feature sets all part of the Win2K3 system but "stepped" like Standard, Deluxe and Super Deluxe. Like 3 grades of gasoline, the marketing departments of OEMs will be able to sell it in stripped to fully "pimped out" versions.

As a SOHO/Home server it would be a really nice system if it was fully tricked out like a 2K3 server could be. I didn't bother to discover what functions were actually enabled and which were disabled. To offer a lot of the functionality touted in the advertising, the feature set of the 2K3 system would have to pretty well stacked up. Simply because the system would require most of the networking software of the 2K3 to implement standard Internet protocols and all of the security infrastructure to support them.

by xwindowsjunkie

At this point my 2 to 3 week experiment has gone way over time but things are still progressing although the pace has slowed considerably. Biggest problem is getting time to work on Debbie and her sisters.

I've been doing some configuration tests with NFS and Samba trying to find the best mix of settings and permissions to allow both server systems equal access to the shared folders. I don't want Linux to override Windows and vice versa. So I've been playing with the server and a couple of Debian client boxes I set up and a couple of Windows clients, one running XP Pro and the other Win98SE.

I've also been toying with the idea of running some services like streaming content on a second subnet and perhaps over 802.11G wireless instead of the main wired 100 baseTX network. Especially since my son seems to think that Internet "radio" hiphop is way cooler than real radio.

More to come.

by dumphrey

that you mention Wireless. I have been working on setting up a wireless Ubuntu box for my bedroom for streaming media from my main box. So far, I have had zero luck. I started with a Linksys wmp54Gv4.1. I pluged it in, and ubuntu saw the card, recognized the chipset, and loaded a driver. The driver was completely broken. I could not even connect using wep, and wpa was not even offered by network manager. Next I tried a netgear 311v3. I once again could not get this card to work under ubuntu, even using ndiswrapper. I kept getting errors that the driver install was not complete. An interesting note: Mint Linux (based on Ubuntu) has an ndiswrapper driver for the Netgear 311v3 on the install disk. In about 10 min I had the netgear card up and using wpa2 on a live cd. I guess I will be installing Mint linux on that workstation.

by neon samurai

I've a linksys wrt54gs with 54gs NIC stuffed into my notebook. Ubuntu took some work, Mandriva picked up the card pretty cleanly.

Ubuntu was one or two liveCD release versions ago but I had to use Ndiswrapper and my Windows WIFI driver. I then had to add wpa-supplicant which gives you the WPA support. The last step was fiddling with network startup scripts to get it connecting.

Mandriva 2007.1 is the latest liveCD offering from the Mandriva distrobution. In this case, I had to do a custom install (it always is anyhow so no change there). At the initial network setup, I specified "use windows driver" and pointed it at my windows partition's NIC driver.sys. After that, the included wifi browser could see my network and Mandriva connected with WPA just fine. I believe this is primarily due to Mandriva now including WPA and doing the Ndiswrapper work for you as a "use windows driver" setup.

I haven't had a chance to push the network card and see if I have complete support under Mandriva mind you; it's only connecting me to the home network at the moment (nothing "fun").

by xwindowsjunkie

I couldn't resist!

You ought to be able to run that wrapper and driver under Ubuntu or at least that would be my uneducated guess.

My son's computer is running Win2K SP4 so running it on a Linksys PCI wireless 802.11b/g card is no big deal. My daughter's computer is running Win98SE and I'm beginning to think that will be a bit of a challenge since it hasn't worked right yet. I'd bump her up to Win XP but I'm really getting reluctant to give MS any more money at least at the personal level.

My company's customers pay for Windows as part of their product purchase so I don't have any problems with that.If I could wean her off the games on her computer than I could get her to run Debian or some other Linux variety.

by xwindowsjunkie

Does it use the specific Windows driver for the card made by the manufacturer or just the generic Windows ndis driver?

by neon samurai

It wraps any Windows network driver in a *nix translator so the *nix outside has it's usual driver module calls and the driver inside get's Windows driver calls.

That's how I understand the functional details anyhow. In general, it wrapps any Windows network driver then uses the driver to talk to the NIC hardware.

It should also be included with most Linux distrobutions though Mandriva made it rather easy to setup in my specific case. I've also used ndiswrapper with older distros and more conveluted setup steps.

by dumphrey

After several days of frustration, I finally did what I should have from the start. I uninstalled ndiswrapper from Ububtu through apt, and downloaded, built, and installed the latest ndiswrapper from their sourceforge page. Next I checked out the ndiswrapper page for cards, and eventally stumbled on a driver for the Netgear wg311v3 (Marvell). Using the xp sys and inf from the marvell driver, and a new ndiswrpper, I had a wireless wpa2 connection in the amount of time it took to create a new connection. I am most pleased. The key was looking at the ndiswrapper version in Mint Linux (which worked). I guess now I will see if I can get the linksys card working.

by dumphrey

running Ndiswrapper in ubuntu, but I had to upgrade to a newer version then the one in the apt-pool by compiling it myself. That was the only problem it seems. So it should also work in debian I would guess. If anyone is using a netgear wg311v3 pci card, let me know....

by xwindowsjunkie

After neglecting my Linux Home Server project for over 2 weeks I've had some time to work on her. Sometime before then, I managed to screwup the smb.conf file and disabled Samba sharing such that Windows XP could not connect successfully to Debbie. Debbie however worked extremely well as a SMB client of whatever Windows server I pointed her at! Attempting to log on from a Windows client onto Debbie however was another issue. I could get the log-on dialog form repeatably but not a complete transaction. Fixing that took a little time. (see below for a sample smb.conf file.)

Connections are now automatic onto Debbie from all Windows OS boxes, mainly by implementing a log-on/drive mapping script run on each user log on. This duplicates the functionality of the "WHS Client Connector" used by Kraken (Release Candidate 1 of Windows Home Server). All of the log-ons on the Microsoft system need to be "replicated" or basically copied onto the Samba server. That means the User name and its password used to log onto on the Windows system needs to be copied into the configuration of the Samba server. I would heartily suggest that these accounts be only USER accounts on the Windows systems. You don't have any business using an Admin account to access movies or media files on an external server system, Linux or Windows! I do not worry about the security issues of the Debian system but Windows systems have demonstrated many times their vulnerability to "man-in-the-middle" attacks.

Overall, I will be depending on a hardware firewall based on a Linux distribution that basically shuts down ALL Netbios (and a lot of other ) interaction with the outside Internet. I will not be putting Debbie directly on the Internet. She'll be working through the firewall like all of the other systems on my home network. The difference will be that she'll have a NIC in the DMZ and another on the local network. Routing between the NIC ports will be heavily controlled.

Here's how to do the auto-log on on the Windows clients. This line below is saved as a Windows (MSDOS) batch file saved as ANSI or UTF-8. Notepad (not as extensive as gedit) works fine.

net use x: \\192.168.99.30\serverclientsshare password /user:username /persistent:yes

This assumes your Samba equipped server is located at 192.168.99.30 with the share named "serverclientsshare". Don't type , just press enter. The password and username are the password and user name of the Windows AND the Samba account. This is one of those areas where I've run into some confusion. If the Linux account username and password do not match the Windows username and password, the logon on the Samba server usually fails. You can't operate in a mode that is essentially "log-on-Samba-as- another-username". This might be a "feature" of one of the myriad post-Service Pack 2 quick-fix patches from Microsoft, I do not know for certain. I have been keeping the WinXP Pro system up to date using Microsoft/Windows Update, especially since it seems as if support for XP is soon to stop. One of the fixes might have broken using user name aliases.

Then the complete path to the batch file location, as a string, is placed in the Run key in the HK_Current_User.

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run]
"LinuxShareLogon"="C:\\Documents and Settings\\username\\batchfilename.bat"

Shown here as the complete text for a sample.REG file. Double left click on it in Explorer and answer yes twice. There you go, you've just installed a Trojan! No not really. The keyname listed on the left (LinuxShareLogon) makes absolutely no difference, it just can't be "" (a null string or a space). Its the path listing on the right side of the equation as the value that is important. You may already have other programs set to run in the Run key, just add this one to the list.

Or you can add it using a shortcut to the batch file in the Start folder in:
C:\Documents and Settings\username\Start Menu\Programs\Startup

Either of these two methods will enable an automatic log-on to the Linux based Samba share. If you want to enable the same drive mapping (x:, substitute any drive letter for x) for ALL users on the Windows computer, substitute All Users for username in the above listed path. I do not suggest it except on Windows systems used only to access the Samba shares. This mapping will override whatever user mappings for that particular drive letter that have been previously set so be careful! The persistent setting may generate an error message on subsequent log ons but will be ignored. This will allow the system to reconnect automatically on the next Windows system boot-up or user log on regardless of the user mistakenly deleting the drive mapping.

For those of you that know about WINS or Netbios browsing groups, you may wonder why I used an IP address to address or name the computer in the command line above. Windows simply connects twice or three times as fast when it doesn't have to do a lookup in a WINS server or Netbios listing. In the system design model I am using, Debbie is going to eventually be a PDC (or Primary Domain Controller in Windows nomenclature) and will be running DHCP, DNS caching services and WINS, so it needs a fixed IP to remain consistent for all the Windows client applications (most of them!) that don't like moving DHCP targets.

Files and Folders security and access settings are part of the NFS and Samba settings used on the Debian folders setup as shares. All users and at least one group they are a member of must have at least read access to the folders both under the Debian file system settings and under the Samba configuration file settings in smb.conf. The settings likewise must be consistent. The service with the least level of access rules. In other words Samba access set to write doesn't over-ride the Linux access of read-only, or vice versa. This might be a feature of Linux SE, I'm not sure. I do remember it working differently with Samba 1.

There are nuances in the Linux and Samba security models I still haven't completely mastered yet. I do know that essentially all users on the Windows systems accessing the LHS must have valid user accounts on the Debian system before any of the Samba implemented shares will work properly. The computers the users are logged onto, likewise are required to either have a Machine account or a listing in the permitted systems sections of smb.conf. In addition, there is a Debian-Samba system update cycle issue that limits the number of system privileges, shares access and user group permissions that can be changed at any given time. Using SWAT and then looking at the smb.conf file settings is not guaranteed to give you the total picture of what is going to happen the next time on boot-up of the Debian system. I do not blame Samba or Debian but my own understanding of what items take priority over others in the smb.conf file and how SWAT makes things work.

Here below is a sample smb.conf that works reliably on Debbie. There is actually nothing here that is unusual. serverclients is the name of the general public folder and the user group that has access to LHS. All users having access to the LHS must be a member of serverclients the group. I've set the folder up to be shared as a Samba and a NFS share with the same more or less open permissions. Although the user interfaces and the OS are different, the folder is easily accessible by both types of client. Later I plan on tightening up write permissions so that users can write to their own folder and read all others under serverclients. I also would like to set up the user account routines so that as users are added, they get a public folder and a private folder under their username folder automatically.

I've set the announce level and the OS level to 33 to prevent any Master Browser server battles. WINS server is enabled on Debbie. This level and server setting should guarantee that the LHS is always the Master Browser. 33 is also the recommended setting for a Samba server set-up as PDC. This smb.conf is still set for stand-alone server settings with the exception of the OS level setting. Mangling method has been left blank and will eventually be set to whatever level I can manage to include all the Windows clients I have that will need to access the server. As may not be obvious, Microsoft calls it the "encryption" level and it relates to the security model used in LanManager(NTLMv1 & 2) and later methods of security on user passwords. Mangling method is an all too apt jab at MS for their "encryption techniques".

# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2007/08/02 16:56:05

[global]
workgroup = Homenet
server string = Debbie
auth methods = sam
announce version = 33
client signing = No
client use spnego = No
mangling method =
os level = 33
wins server = 192.168.99.30
ldap ssl = no
username = xwindowsjunkie
valid users = xwindowsjunkie, user1, user2, @serverclients
write list = xwindowsjunkie, user1, user2, @serverclients
hosts allow = 192.168.99.0/255.255.255.0
wins support = yes

[xwindowsjunkie]
comment = this is a folder inside /home on debbie for a Linux client but also shared as an SMB client
path = /home/xwindowsjunkie
read only = No
max connections = 25
available = yes
browseable = yes
public = no
writable = yes
[serverclients]
comment = this is a folder inside /home on debbie
path = /home/serverclients
read only = No
browseable = yes
available = yes
public = yes
writable = yes
[user1]
comment = this is a private folder
path = /home/serverclients/user1
read only = No
browseable = yes
available = yes
public = no
writable = yes

In Debian's Shared Folder applet, I've set the Samba share for the folder /home/serverclients as listed above in the smb.conf. The same folder is also set as a NFS share and its acl (Access Control List) state is saved in the file /etc/exports and gets listed as /home/serverclients 192.168.99.0/255.255.255.0(rw). The acl setting is exactly the same as a Windows group serverclients would get in an NTLM type group as folder owners. Remember that Debian Linux requires the Samba clients have valid Linux accounts in a valid Linux usergroup to have access to the Samba share.

If you are a Windows IT guru in a one-man IT department with no budget and you need a reason to learn Linux, Samba is the reason, especially Samba-3. It is by far the most impressive application to promote interoperability between Linux and Windows systems. It has in my opinion done more to make heterogeneous network installations work than any other piece of software ever written, period. It bridges the gap between Windows workgroups and NT domains and Linux in so many easy ways. It has a scalability that allows for graduated incremental steps from workgroup to full Domain. It is worth the price of learning Linux to use Samba to get around the high price tag of Windows Server products and the high-priced hardware needed to run them, especially with Windows Vista.

One manual that I have scanned at least most of it and read deeply perhaps 25% of is:
The Official Samba-3 HowTo and Reference Guide, ISBN 0-13-188222-8. It is also available for free by access by download. My rating: Excellent! Extremely clear explanations. The authors' goals were to promote understanding, not arcane jargon, an attitude often hard to find in software manuals. If you are conversant in Windows NT 4.0 and Windows 2K products, this manual is what you need to configure practically any Linux server from any distro to take over generic file and print serving functions, network protocol server functions, and operate as either primary or backup domain server for a "large" domain workgroup in a small office environment. Although Samba/Linux is often associated with these older NT network servers, it can keep up certainly with a Small Business Server 2003 situation without the freaking large price tag and still do it on hardware of P2/P3/P4 vintage. If you decide to use Samba, you will want to go buy a copy and keep it within arm's reach while you work on and learn Linux server functions.

At one point a few years back I used a license I had for NT 4.0 Server on a P1 system because I wanted a full server with DNS, DHCP servers etc. for use at home. Partially it was for my own education while I did my certifications but also because at the time the idea of a central server to hold my family's files was attractive for the idea of maintaining current backups. Samba3 running on Linux now can not only replace the Windows server Control Panel "applets" and backup functions but also function as a full primary server for user logons etc. It will completely replace NT 4.0 Server in a NTLM domain. With Kerberos and LDAP Linux applications, it can completely replace a Win2K or Win2K3 server as well with the exception of Active Domains. In a small office environment, Active Domains is massive overkill and isn't worth the effort. What this means in the realm of Kraken (a Win2K3 Small Business Server cropped down to Windows Home Server RC1) is that with Debbie (a Debian 4.0 server running Samba3) I can serve files to Linux, Windows Vista, XP, NT, CE, ME, 9X and even WFW 3.11 clients! Kraken can only serve to XP and Vista clients!

Apache2 is my next target of investigation. Apache so far has demonstrated absolutely no issues. Perhaps because I really haven't done anything with it yet! What I have experienced with Apache2 and Samba so far seems as if both projects are being written in the same style, by the same groups of programmers. Both groups are obviously pros and they have dedicated pros writing the documentation. That makes the software they release a joy to use.

Web pages will be the standard User interface to Debbie, the LHS. I haven't done it yet but swat looks like a model to follow for at least a beginning control system for the LHS server. Yes I know. I'm breaking one of my own rules, I'm going to write programs. I think my disease is terminal now. I just spent the last 3 weeks writing and debugging batch files and VB scripts to automatically install application software from a remote Windows server for work. The hardest part was making them "stupid-operator-proof". HTML and javascripts seem trivial in comparison.

It looks as if I will be able to write VB Script or Javascript loaded static pages that are served up by Apache2 on Debbie and actually executed on the Windows clients. These pages will most likely need to be accessed by IE 6 or 7 and I'll need to fiddle the security settings on the Windows clients to allow them to execute on the clients. Dropping shortcuts onto Windows desktops look to be the easiest way to get the embedded script pages "installed" on the Windows clients. Browser functions to open, save and view files are the activities most likely to be the ones needed at the start. That should work on the Linux ones as well.

I'm still interested in adding news website RSS feeds into some kind of a master news server. A long time ago BG (Before Google), I had a spider package that would scan websites for specific info (damn I should have filed a patent!) by using keywords. I could be doing that to incoming RSS feeds. I might not even have to write any software, somebody has probably already written it!

I've had no time yet to look into why Bacula doesn't work on Debbie. Having already exposed my aversion to SQL Servers of every flavor, I'm going to put it off as long as I can and avoid messing with it until I have to, probably with Bacula. If I soon can't get Bacula to work I'll find a replacement for it.

Since I'm using what probably ought to be called junk to implement my media server, I'm still of the opinion that I'll put the TV tuner board and the DVR functions on a separate computer. I have an old 1.8 GHz P4 Intel board based on a 423 pin CPU with 512 MB of RAM that probably could run as a TV/DVR streaming server. Its hard to justify the cost of new CPU hardware ($500+) to replace a $150 DVD recorder/player. Using a separate system gives me the option to run it first as a Windows system to verify that all of the boards, the CPU, RAM etc all work without dragging out the process. My skill-set as a Windows system guru is still much stronger than my Linux newbie side. Hey Yoda backoff! I'm still trying to find my balance in the Force!

by dumphrey

with your server. I do have several questions..First, why did you not just use local computer policy to apply the samba mount script? Second, why will Debbie have a nic in the DMZ? Are there that many ports you would have to forward? And if you were going to be security conscious, you may want to look into port knocking instead of just forwarding. Also, have you installed Webmin yet? For Debian Etch its a single .deb package download and install. I recently discovered this little gem, look for it asap. It gives a common web interface to manage 98% of your computer, including servers. I installed it on an old box, put the computer in place in our second location, drove accross town to my office, connected to the web interface through a vpn, and set up a squid/clamav/squidguard web filter/proxy for our call center. All from a web interface. I had to apply the proxy through group policy, and Webmin couldn't help there, but no program is perfect =\
As for putting the tuner card in a seperate box, I recomend that heartily. I have a mythtv box running both the front and back ends. Keep in mind this is a 1.2Ghz celeron with 512Mb sdram. Changing channels is slow, and the UI is a little unresponsive. I have the remote working, but it seems laggy, so I just use the keyboard. I actualy get better perforamnce if I use another box as the front end, and stream the video, the buffereing and reading tends to use a lot of cpu and disk time. I could probably improve the performnace a lot wit some tweaking, but I do not watch enough tv to bother, its good enough for me. For just straight tv viewing, no recording, an old ATI TV Wonder pro (pci) plays beautifully through tvtime using the stock kernel driver in every linux distro Ive used in the last year or two. I have no idea what the newer cards are like though =\
Bacula is a major pain. It either "just works" or takes major hammering. I did see a very good man on it not long ago, i will see if I can find it again and put it in a sa link..
Not the one I saw, but seems pretty good anyway
http://www.debianhelp.co.uk/bacula1.htm
web interface for bacula
http://www.debianhelp.co.uk/baculaweb.htm

I am in the process of replacing my 2 ubuntu boxes with Debian 4.0. I also have a spare box I am attempting to learn freeBSD on. My overall goal is to build a machine able to do 99% of all web based activities a windows box can do, so I can spend less time fixing my roommates computer =\

by xwindowsjunkie

Local computer policy requires you do more work than write a logon script. It also assumes that local computer policy is installable on all clients. Win9X clients really don't have a "local policy". Also the local policy of mapping a drive is handled differently in each version of Windows. So if I had to fiddle with policy I might as well map it directly in each logon. The same logon script works on all Windows computers and with all users. Since the server sets the level of access each user has, the logon script just opens the door. The user group privileges on the server set the permissions the users can exercise.

At least in this house I only have 5 potential "logees" not counting the two dogs! (If they manage to log on then I'll give them admin privileges and retire!)

Also at present I don't have a Netbios or NT domain setup yet on Debbie. That is my eventual goal but I'd like to keep it a little looser than that for a while till I understand a little better what I'm doing.

Port knocking, good grief, that looks like a difficult manipulation technique for little benefit. Combine that with Tor from the EFF and you've got incredible IP obfuscation but not encryption.

Transmissions between those two IP addresses will in 99.999% of situations will have to be locked to those two IPs. So I don't think you gain much if anything over encrypted connections. Network monitoring will capture all of the traffic based on IP To and From addresses. You can implement the same thing as a knock sequence by passing a coded sequence back and forth that is encrypted with the same one-time pad technique.

You could take the port knocking sequence to its logical conclusion and continue to scramble the port numbers on every IP frame for the entire communication between two computers. A one-time pad would be perfect for that but there are a limited number of port numbers, 2^16.

In radio systems like wireless Ethernet, pseudo-random frequency hopping is used to scramble the transmission and to provide higher bandwidth capacity with less interference between "competing" systems. A digital correlation filter provides the means of synchronizing transmitter and receiver during a training sequence. You'd have to have something like that for the port tracking. You couldn't really allow the IP frames to embed state information because that would be a give-away for a hacker to do his tracking with.

I suppose you could also hop around on IPs as well but it might make a lot of ISPs really angry!

VPN and tunneling look a lot more feasible and easier to deal with than port scrambling.
Layering on PGP or some other encryption technique should make it invisible to the users at each end.

Back to the issue of the DMZ. My system is structured this way:
The incoming DSL line goes through a ADSL modem that does an IP address translation, serves a block of DHCP addresses that then enters a Linux firewall system with 3 NICs. One for the incoming ADSL/Ethernet, one NIC for my systems and the final NIC (the DMZ) for my son's (win2K) and daughters Windows 98 computers. That NIC feeds into the WAN connection into a Wireless router that does NAT, DHCP and port mapping/ forwarding from the WAN side to the LAN side. The Linux router has IPChains that do not permit routing from the DMZ to the NIC handling my networked systems (2 Windows systems, the Linux Home Server(Debbie), 2 more Debian desktop systems used for testing and trying out the LHS and my SUSE 10.2 desktop system. There are is also a Linux printer server HP DeskJet 500 (it still works!), a HP 3100 printer/scanner/fax and an Epson 880. The LHS (Debbie) will have a NIC on the DMZ so that my kids can use the LHS for their file storage.

by hillman.d9

I use FreeNX on Ubuntu as an application server. It's fast over a slow connection, doesn't drive me crazy like Remote Desktop and is pretty secure. I think this is one area where Linux has Windows beat. XWindows was designed for network use from the beginning. We use Terminal Services on Win2k3 at work and I really hate it. The licensing issue is a real pain and it's a bandwidth hog.

by doug

Yep. I'm posting this over a FreeNX
connection thru a DSL line to my home SuSE
10.2 server. It's plenty fast enough to do
work on.

by absolutely

[i]These are the specific features I was able to discern from the advertising on the URL citation listed above. There is also a mechanism that allows 3rd party applications to operate within the server framework, I'm going to assume plug-ins.

Digital Media Shares
media and other files served throughout your home and through a website IP
Remote Access to Your PCs
WHS lets you access your PCs and media from a Web-connected PC
Protect Your Data
automatic backups and full system restore. Smaller restores of individual files and folders (incremental daily backup) of accidentally deleted material.
PC Health Monitoring
Manage a family of PCs with WHS monitoring. Make sure virus definitions are up-to-date and each PC is running the latest updates.
Users rights and access management
Users can be grouped and allowed specific access to shares and PC access
Firewall (assumed)
Microsoft can be so stupid as to not to build in a stout 2 way, state-full watching firewall. I will not be that stupid in any case with the Linux contender I build.
Web-Browser management and access
This is also an implied feature.[/i]

Some of that is comical: "Keep all your family's PCs happy and healthy with home network health monitoring. You can see the exact condition of the computers in your home and make sure everyone's software and virus definitions are up-to-date." which you summarized "PC Health Monitoring
Manage a family of PCs with WHS monitoring."

Hmm, so, is Windows Update going to be decommissioned, then? Will Vista block my virus definition updates from my third party security software vendor? Because in all seriousness, I am not about to trust my computers' "security" to the team of code monkeys that put the easily exploitable vulnerabilities there in the first place. In other words, by merely configuring a simple file server and Internet server or proxy, I have that functionality via the software installed in XP.

The same goes for "digital media shares". I open Windows Media Player, search the shared directory on my Debian machine, and play my mp3s directly in XP. Streaming media, check.

I myself haven't configured Debian into a "web-connected PC" or tried to use bacula for the data in my Windows computer, but you have posted that those functions are working in Debian as advertised for WHS, haven't you? So in a nutshell my question is, when are you going to compile that, write up documentation for the odd .conf file that will need to be customized from one home network to the next, and what are you going to call it?

by xwindowsjunkie

I haven't gotten anything out of Bacula yet. I think something is broken and I haven't a clue as to what it is. So for the present I've completely un-installed it and yanked it out of Debbie completely, or at least I think I have. That's the nut of the issue, I haven't been able to get anything that comes back and tells me its running or not, installed or not. So I'm going to hold off working on Bacula until I get more info on it.

I have mySql installed and that's all well and good but I hope to not to have to mess with it at all.

I'm spending my time right now working on Apache2 settings, configurations etc. I've run into a bit of an issue in that Apache2 is running in a very secure manner and I appreciate that but its a pain in the butt trying to manage something that requires you to type passwords every time you want or need to fiddle a setting!

I'm not going to claim "mission accomplished" prematurely like another famous Texan I know! Debbie is still a work in progress. The smb.conf (Samba configuration file) that I am currently using is very similar to the one I published with most of the ID info changed to hide my system settings. I do know where you are coming from though, so I am documenting what I do or have done in a series of web pages that I'm writing and "hiding" at present until I get some time to go back through and "sanitize" for my protection! ha!

The one thing that I have learned is that using the apt-get mechanism looks to be the best way to install the scripts and file changes when that time comes around. I'm fairly impressed with the Debian mechanism they use for updating the running system image. I can see writing a configuration application that writes the various text files and then updates the entire system in one fell swoop through the file system.

A final comment on Kraken (the WHS box). Besides only allowing 10 users to be connected to the system at any time. You can do that with any workstation product all the way back to Windows 3.1! So there's an artificial limitation that they AGAIN programmed into the system. The systems that the WHS connector work on only include the last 2 versions of Windows XP (SP2 on top of that!) and Winsta (ryhmes with gangsta').

I was not impressed at all that Microsoft made a cold, hard, mean-spirited decision to cut out support for anything Microsoft older than XP or based on FAT or FAT32 file systems. I can understand their reluctance to include Linux clients. That was a purely marketing decision and from the viewpoint of a long-time user of Microsoft products, that was unforgivable. They claim "inter-operabilty" is their goal but they show time after time that money is the motivation not customer support. That earns them the pirate's black flag (Jolly Roger) in my book.

by absolutely

I'm sure I'm not going to mess with Apache for my own home server, but I have been meaning to get my feet wet with bacula. If I find anything interesting I'll post it here.

by doug

Well, last month my windows 2003 server's
power supply blew, so I set up a SuSE 10.2
server. The e-mail was easy, as was teh
remote access, but I'm still having problem
rewritting my websties in Java Studio
Creator.

Still, except for a few glitches, I found
Linux much more user friendly than windows.
Yesterday I ordered a 699 notebook with a
17 inch screen, and I'm going to install
linux on it and make it my work computer.

BTW, I think Bacula is a bit of a dead end.
You might want to check out partition
magic, and systemrescuecd.

by dumphrey

I hadn't thought about windows 98 machines. I guess the oldest windows I use is 2000, and I use that quite a bit really...I still think using local policy on the machine able to support it to run your boot-up script would work better for me, I would latter on forget about the reg entry, but I tend to look at local policy when trouble shooting.

I understand why you use a DMZ now, but it seems to me that you do not use it AS a DMZ, since all hosts on it are behind a wireless router, though, now that I look back, it seems that you consider all the hosts on it "untrusted". Nevermind, I see why its a DMZ.

Sounds like you have it all under control =) Let us know how it all progresses, and how Bacula ends up.

by absolutely

"You might want to check out partition
magic, and systemrescuecd."

Why? What about either/both do you find commendable?

by xwindowsjunkie

Partition Magic when it was NOT owned by Symantec was the absolute best partition manager period. No contest. I NEVER lost data due to a software error, not once. It would tell you exactly what it could and could not do BEFORE it did anything. I bought Partition Magic 8 from Symantec on a download but it was obviously still being programmed by the original programmers since it didn't come completely wrapped up in Norton Utilities sh--. I never found that Norton Utilties could do what it said it could. I made backups everytime I had to with Norton and I was glad I did 50% of the time since Norton would trash the drive 50% of the time.

It would also work with ext2 and ext3 partitions, nice! I never used it with Linux though, just Windows systems.

by absolutely

& Symantec's, which is why I asked the question. I had never heard of the other app recommended, and am genuinely curious why either was suggested in place of bacula. Very odd, IMO.

by doug

Sorry dudes. I meant this:

http://www.partimage.org

In linux there's also tar and rsync. I'm
still experimenting to find the right
software.

Right now I'm trying to figure out how to
image my new AMD 64 Turion notebook before
I shrink the VISTA partiion down to 20 gb
and use the rest of the 160 gb drive for
either SuSE or Ubuntu. Systemrescuecd
doesn't like the processor.

This will be my work computer. I will soon
be windows free!

It's an Acer 9300. 160 gb hd, 17 inch
screen, 64 bit processor, all for 699.
Seems like a steal.

by apotheon

SystemRescueCd is a LiveCD Linux distribution designed specifically for use doing, well, system rescue stuff. It includes a lot of utilities for backing up, restoring, filesystem management, and so on.

by absolutely

backuppc looks like the way to go, so I'll be trying that the next few days.

LDAP is a hassle and all the POP3 MUAs I see depend on that, so my "mail server" is currently a send-only freak. I'm tired of trying to get it working, too, so I'm happy to have something easy to do this weekend, between barbecuing.

by apotheon

What MUAs are you trying out that require LDAP? What are your requirements for an MUA, anyway? I may be able to make a suggestion -- or not.

by absolutely

I shouldn't post so late at night I guess. :)

Certainly relaying mail could be accomplished without LDAP, but my observation on the email packages in synaptic is that the ones that can work with clamav and filter rigorously against spam tend to also have sophisticated authentication -- either ldap, mysql or postgresql. Specifically, I have been looking at courier & perdition. I've installed & started configuring both, but neither has delivered my messages to my other computer's Outlook Inbox. In both cases, I got stuck at the step 'list of users/authentication'.

I'm looking at p3scan as my fallback, and really I think it's pretty ideal: "transparent POP3-proxy with virus- and spam-scanning" is really just right for a home server, even for very large families (or small apartment complexes & dorms, possibly).

Your suggestion is definitely welcome, but I might just decide that learning the LDAP dance is a worthwhile exercise anyway.

by neon samurai

I have to find some better howto docs to read though. Right now my postfix/procmail/courier-imap,-ssl is only delivering mail within the machine. I'm using system user accounts but will have to explore mysql auth after I understand the base mail setup. eGroupware works perfectly overtop of it all and my outlook/thunderbird clients connect over ssl imap without issue but there is no mail going out or in.

Any links to good howto for a courier mail server behind a port forwarding router would be appreciated. The webserver works clean through a dyndns so in theory there should be no issues once I learn how to config the mail server properly.

by apotheon

I haven't really dealt with unixy mail servers sans LDAP, so I guess I don't have much to offer in the way of advice. Learning LDAP should prove useful anyway, however, as it can serve to provide you with a deeper understanding not only of Unix-based networking services, but also of Active Directory (since AD is basically just several Unix-based services glued together).

by absolutely

Courier's set of features and compatibility
with various databases looks nice but it's
a little bit of a nuisance to get started.

by apotheon

My experience with managing Unix/Linux mail servers has all been with Sendmail, Postfix, Exim, and Qmail. My experience with Qmail has been that it kinda sucks (for both functionality and security reasons), and my experience with Exim is that it's a severe pain in the butt to configure (like learning to read and write Chinese). Postfix is particularly easy to configure, in my experience, and very well documented -- it's what I used on Debian (instead of Exim).

This discussion is closed to new replies.