The February 16 PLUG meeting will focus on three aspects of networking that are often lumped together, routing, network address translation (NAT), and firewalling. What these things are, and how to configure them under GNU/Linux will be discussed. Live CDs and floppies that can enable a computer to take on these roles will be demonstrated.

Date/time: February 16th, 2006, 7:30pm.
Location: room 2M70 (M=Manitoba building) at the University of Winnipeg, 515 Portage Avenue.

Hackers rejoice!

Winnipeg might not have a big hacker conference like the ones in Las Vegas, New York and across Europe, but this summer we have our own little mini conference within a larger festival. (see www.freeculture.ca)

Hackfest has five goals:

1. To demonstrate the quality of Free Software to non-hackers.
2. To explain why freedom and openness in computing will benefit society.
3. To provide help installing a free operating system for anyone who brings a computer to our event.
4. To help our community by writing an application assigned to us by the OpenCity board. (probably a web front end to a DB). We will call this the Free Software Barn Raising. (moo!)
5. To share advanced knowledge with each other.

Location: Kismat Banquet Centre, 280 Fort St.

Dates:
Thursday August 18, 9am to 11pm
Friday August 19, 9am to 3am
Saturday August 20, 9am to 3am

Conveniently, there are two other events at OpenCity that are in the same building. There is a conference in an adjacent room from 9-5 each day, and a spectacular line up of music in the same room as us starting at 7pm on Friday and Saturday.

There is no cost to participate in Hackfest@OpenCity_2005, except during the music performances on Friday and Saturday night. Admission is $4.99, and totally worth it, there is nothing more exciting than hacking with loud, live music in the background. [And, it's cheaper than DEF CON. :) ]

You can also attend all the OpenCity events at no cost by becoming a festival volunteer. Agreeing to make a good contribution to goals 1-4 will be enough to get you volunteer status. Contact OpenCity Volunteer Signup or call 633-3259 to become a OpenCity volunteer.

Join the Hackfest@OpenCity_2005 mailing list .

Hi, I was looking for the online edition of La Liberte, the French paper in Winnipeg, but their domain isn't liked by any of the name servers I can get at. Can someone confirm or deny that www.presse-ouest.ca is down? Thanks / merci, Phil

Greetings from the steamy south. I'm currently a Linux user in St. Paul, Minnesota, but am considering a move to Winnipeg in the next year or 18 mos. I wanted to compare notes on internet connectivity options, figuring PLUGgers ought to be the most specifically clueful folks I could find.

What I've found is that apparently the two biggest choices are either MTS for DSL or Shaw for cable. But, that's far from all I need to know. What I'd like to do is replicate or approximate the setup I have now.

Currently, I have ADSL, with the physical layer through the telco. We have a Linux friendly ISP in town, so I can get 640K down/ 256K up, for US 40.00. Not the cheapest in town, but there are a couple of reasons why that's a price I'm willing to pay:

• 6 static IPs
• No restrictions on running servers
• No restrictions on bandwidth
• No hassle from tech support about Linux
  (telco is another matter.)

Basically, they just sell me the pipe. (The ADSL is about US 40.00/mo. too.)

So, the big question is, if you know of a nice way to set up such a thing, I'd appreciate hearing about providers that aren't too fussy, reasonable DSL (or other) net connections, who to avoid, etc.

Apologies if this is old hat, but I haven't seen a mailing list or archives or same like what the TCLUG around here uses for such discussions. Thanks for your input! Cheers!

I recently setup a lan and firewall for DSL at home. I tried a few different methods and ultimately stuck with floppyfw router package. It supports nonstandard floppy images (1.6m), VPN using pptp, lptn and ipsec (freeswan), and even has a caching DNS server.

Our friend from India has posted another article on linuxjournal read it here: http://www.linuxjournal.com/article.php?sid=5869

In Part I of this story, I gave a brief history and overview of LDAP. In this, Part II, I will go into some more detail about how to set up and use LDAP.

Ever heard of LDAP? The acronym stands for Lightweight Directory Access Protocol, but it\'s anything but lightweight.

An LDAP directory is like an addressbook shared by many users across a network, with special features to control who gets to see whose information. A company with many branches might use an LDAP directory to allow employees to look up their colleagues\' e-mail addresses or telephone numbers.

That concept in itself sounds simple enough, right? After all, how complicated can an addressbook be? Famous last words. After Jason Loughead and I spent all night trying to put PLUG\'s membership base into an LDAP directory, we feel like no one else should have to suffer through LDAP like we did.

That is why I am submitting this story.

CERT Advisory CA-2000-20 Mulitple Denial-of-Service Problems in ISC BIND Original release date: November 13, 2000 Source: CERT/CC A complete revision history is at the end of this file. Systems Affected * Systems running Internet Software Consortium (ISC) BIND version 8.2 through 8.2.2-P6 * Systems running name servers derived from BIND version 8.2 through 8.2.2-P6 Overview The CERT Coordination Center has recently learned of two serious denial-of-service vulnerabilities in the Internet Software Consortium\'s (ISC) BIND software.

Open source projects are now refined enough that they provide us with the most configurable and reliable solutions of a vast array of refined products. Recently I was told to implement a VPN solution for my company and keep costs down. Since my company is one of the 'survivors' of the dot-com world, this definitely means no highly expensive commercial products (those of us left have a budget.) It also means we don't want to cut off our own head with an open-source solution that doesn't live up to our specifications.