The Waikato Linux Users Group have a meeting in one week from today:
----------------------------------------------------------------------
<?plugin RedirectTo page="MeetingTopics.2006-09-16" ?>
Carrying on the theme of my previous message here is an article about
firewalls on Ubuntu and two choices. By default Ubuntu doesn't install
a firewall because it doesn't listen on inbound ports by default but
if you enable any listening services you will want a firewall:
http://www.linux.com/article.pl?sid=06/06/26/1556259
--
Ian McDonald
Web: http://wand.net.nz/~iam4
Blog: http://imcdnzl.blogspot.com
WAND Network Research Group
Department of Computer Science
University of Waikato
New Zealand
From: "Ian McDonald"
What source code package are you using? i.e. where are you getting
those files you put in that directory Intel-536.
These are the drivers from Intel's download site. The same ones I used on Breezy.
That version number sounds like an Ubuntu kernel. Have you tried with
a kernel from http://kernel.org and then using that?
It is the default Ubuntu Dapper kernel. I gather compiling custom kernels is not for nube's like me.
Maybe next install fest I will get a chance to come down and learn a few things, lots of questions to ask,
From: Craig Box
Tried following https://help.ubuntu.com/community/DialupModemHowto ?
Yes. It works fine for Breezy, nothing there for Dapper yet, can't get the driver to compile (Make).
Well I plan on going ADSL in the not to distant future. But it would be nice to work through this problem, for learning purposes.
Thanks David Bowen
I currently have a Debian Woody machine acting as a head-end IPSEC
server to three sites with Cisco 837 ADSL routers. Woody is no longer
maintained and I would like to upgrade the machine, and get it onto a
2.6 kernel.
The IPSEC driver used by FreeS/WAN on 2.4 is klips. FreeS/WAN is no
longer maintained, and has forked into OpenSwan and StrongSwan. The 2.6
kernel has its own implementation of IPSEC, called NETKEY, and klips
requires a patched kernel, which I would rather not have to maintain, as
there is a good IPSEC implementation in the mainline.
The standard 2.6 kernel IPSEC model, using the ipsec-tools, lets you do
all sorts of things with policies. In the past, I've had an ipsec0
interface, which has been given IP addresses and been able to connect
routes to, and hang firewall rules off. I believe NETKEY doesn't give
that. The remote sites can be considered 'trusted' insomuch as machines
on their LAN are currently routed such they may as well be on the local
LAN, and so it wouldn't matter too much that I couldn't apply specific
firewall rules.
Can anyone advise me on the easiest way to do this? Should I continue
using OpenSwan? Is there a good HOWTO for this, or will I be the guy
that writes it? (Assume I know everything on
http://www.wlug.org.nz/26sec :)
Any suggestions? Michal, are you still around, and is this right in
your area of expertise? :)
Craig
