December 09, 2007
raffi
I've been working hard on the Sleep 2.1 manual. My promise to the world has essentially been finish the code, redo the docs on the language, and then write a short primer on integration. Following those actions Sleep 2.1 will be completed.
One of the challenging aspects of writing this documentation is writing good examples. When writing this documentation I realize I'm not just capturing the syntax and basic use cases within the language. I'm also trying to capture the paradigms and ways of thinking in the language. This is important because it is the difference between an academic example and something people can use.
One example is fork. Fork is Sleep's abstraction for asynchronous computing. I say this because I don't want to call them threads. For the most part, Sleep's forks are completely isolated from each other. Of course they can share explicitly specified variables and then we get into locks and all that ugly mucky muck. But in any case I was trying to capture--how do I write an example of a multi-threaded tcp/ip client app? Something that users can cut and paste and begin using right away.
I learned Java in this cut and paste and begin using right away mentality. (Thanks Mr. David Flanagan for your Java Examples in a Nutshell Book--I'm quoting your name and book from memory, that shows what I really think of you).
Fortunately Sleep has had a strong ally in this type of development. I have a few coworkers and the incredibly, ah, vocal jIRCii user community who use Sleep. There feedback, endless support requests, and hunger for a solution have really driven the project. They have helped me identify holes in my functionality, real problems to solve, and of course what to document.
Case in point with fork. This weekend someone was trying to write a connection bouncer in Sleep. I think he actually is close to finishing it. He keeps adding a lot of stuff to it. But in any case he was trying to wrap his brain around fork and how to do computing in an asynchronous manner.
I managed an example that made it into the Sleep manual. If it weren't for him the technique I documented probably would not have been documented. Meaning ever user with a situation similar to his would be stuck trying to figure something out.
So I'm thankful for the users. They are really helping this come together.
The documentation is almost in a distributable state. So Sleep 2.1 should be coming soon. I will probably be ready to call it official in January 2008.
Posted by @ December 09, 2007 07:47 PM
December 06, 2007
aragirn
Help me plan a trip…
I was talking to my mom last night and she inadvertently convinced me that I should take a trip touring the western half of the U.S. this summer. Me, my camera gear, a GPS, my laptop, a sleeping bag and my car. I would probably be leaving from southern Michigan as early as May or as late as June and return sometime in August. Since I’m poor and gas alone will probably eat through my savings, I’ll be camping and relying on truck stops and laundromats to keep from turning into someone who looks like the unibomber.
Anyways, this is the part where you come in. I need help figuring out where to go. I’m gonna take a couple months and move at my leisure but I only have a few locations on my itinerary so far. If you can think of somewhere else I should visit, leave me a comment. If you’re willing to offer a couch, a shower or access to a laundry machine, leave me a comment.
So far, my trip looks like this (in no particular order):
P.S. Please comment at my blog instead of whatever feed you may be reading this on.
Posted by @ December 06, 2007 08:53 PM
December 03, 2007
jon787
Disgusting routing tricks
Never add a Wireless card in client mode to an ethernet bridge. Its just asking for trouble really. Something about the IPv6 packets that come out the wifi interface disagree with my AP's wireless card firmware. The packets don't even show up for tcpdump. To work around this I'm now running a 6-in-4 tunnel from the AP to the wireless bridge.
The catch is that IPv6 from the AP -> wireless bridge works. So I can't run radvd anymore to provide IPv6 autoconf. The network basically shits its pants with a routing loop. Its rather amusing actually, I get funny errors like this:
# ping6 2001:4830:1546:1::10
PING 2001:4830:1546:1::10(2001:4830:1546:1::10) 56 data bytes
From 2001:4830:1546:1::10 icmp_seq=3 Destination unreachable: Address unreachable
Don't think about that too hard or your head will explode.
Posted by @ December 03, 2007 04:33 AM
December 02, 2007
aragirn
Calling all Photographers
I could use some advice on the following image (my first attempt at in-city long exposures involving headlights).
The street lamps are hard to white balance as I assumed them to be sodium vapor, but that really threw off the colors. Also, there’s some light distortion (see the note on the flickr page) and the car headlights appear to be blown.
Thoughts? Suggestions?
Posted by @ December 02, 2007 06:17 AM
December 01, 2007
aragirn
Panasonic DVD Players - H02 error
I put a DVD into my Panasonic DVD-RP56 player this evening and to my surprise, it could not read any disc that I inserted. Instead, it simply displayed: “H02 Error”. A quick Google search indicated this was a common problem (defect perhaps?) to many Panasonic players.
The solution is pretty simple: remove the case, open the tray and then unplug the unit. Inside you’ll see the portion that spins the discs. Give this a few good whirls and start it up again. If it doesn’t spin on its own, spin it around yourself a couple times and it should start up.
Posted by @ December 01, 2007 06:33 AM
November 24, 2007
jon787
Please sit while peeing!
As found in a public restroom in Grand Rapids.
Posted by @ November 24, 2007 05:43 AM
November 23, 2007
jon787
If anyone wants to know why I hate firefox
1.5 hours into the build process:
ar: libgklayout.a: No space left on device
What kind of build system needs (and I quote from their own website):
* 512MB RAM with lots of available swap space. For static and XULRunner builds, 1GB RAM minimum. Additional RAM will significantly decrease build time.
* For debug builds: at least 1.5 GB free disk space (2 GB recommended)
* For optimized builds: at least 300 MB free disk space (500 MB recommended)
WTF??? Can someone please tell me why the system requirements for building a web browser are higher than that for building my operating system!
I had 1 GB, I figured that was good enough for somewhere between a debug build and a real optimized build. I'm using the debian package to build it with a small patch I'm testing.
Posted by @ November 23, 2007 09:15 AM
Firewalls...
Over the years I've developed a rather nice firewall script. It started as a bash script and has migrated to perl. It currently handles both IPv4 and IPv6. I have a nice helper script to run it from a Debian style network manager (ifup/ifdown)
I'm thinking about cleaning it up for release. I recently realized that start and stop are really just special cases of start, so I'm gonna fix that up first.
Posted by @ November 23, 2007 06:05 AM
November 19, 2007
sgowtham
Trip Down The Memory Lanes
Did someone say History repeats? Almost a year after to-date, things shaped up in such a way that I got an opportunity to be 1265 Lombardi Avenue in Green Bay, Wisconsin. Wondering what this address refers to? It’s The Holy Lambeau Field - the home of Green Bay Packers. What brought me here again is of far less significance but the time I got to spend in the premises of this legendary piece of land - often referred to as the Frozen Tundra during NFL commentaries - gave me a pleasant drive through memory lanes…
It was a very pleasant day - given the time of the year - with snow flurries giving near-perfect demonstration of Brownian motion. Few tens of steps around in this Spring-like weather brought me into the Packers Pro Shop: /me got myself couple of #4 jerseys, copies of Deanna’s book - Don’t Bet Against Me and a Patriots (small) helmet - (almost) all for decoration purposes. Banners/Flags of nine (yeah, NINE) NFL Championships along with three Super Bowls and few minutes I spent in Packer Hall of Fame took me way back in time. Wish I had more time to spend, for it’s well worth more than the $8 price tag. Seeing a bunch of Packers (Driver, KGB, Grant, …) in practice uniforms was yet another highlight of this trip. All these and the memories of being one of the 70,000+ fortunate souls that watched the game live on Nov 19, 2006, should I still say I had goosebumps all over? And unlike last time, I didn’t need to take pictures to make more memories.
As much as I love this game, spending a bit of time in learning about the history of the game has helped me enormously to appreciate many of the game/events as they happen. The day after I returned from this trip was the opening day of hunting season. While many brave fellas braved the cold weather hunting deer in the woods, their better halves showed up at the game with signs reading Shh Our Hubbies Think We Are Out Shopping, How Favre Will He Go? and so on and the ever growing Touch Down meter! It’s only fitting (to my trip) that Brett Favre & Co went on a hunting trip of their own, beating the Carolina Panthers to make it a complete package 
PS: The extra copy of Deanna’s book is for circulation - let me know if you are interested in reading it.
Posted by @ November 19, 2007 03:06 AM
November 18, 2007
paul schou
One Voice
I read about a really awesome movement called One Voice today with a website located at onevoicemovement.org. It's a movement acting towards linking up people across the divide between Israelis and Palestinians, mainly youth and younger generations that want to have hope in a more secure and peaceful future, by not focusing on differences, but focusing on working as `one voice'. Linking friends together across the divide makes the division between peoples blurred. This is such a `crazy movement' that it may just work, and it would be awesome if it did!
It's such an amazing movement that it has drummed up international supporters, such as IBM to contribute over $250,000 to this cause. Just imagine posters, bumper stickers, and youth soliciting politicians to not hold their group's personal agendas, but to work for a real compromise... It may be frowned upon by parents, but really... if we intend to rewrite history books and make peace, then an exciting / awesome / radical movement is definitly deserving of our best support. I cannot help but imagine the potential these Palestinian and Israeli `kids' may bring.
In other news, good job to the participants of this years grand challenge. Imagine a vehicle in an urban city, stop signs, traffic, and no driver. Thanks to many new products and ideas of many students, this is now a reality thanks to this advance research program. I look forward to what is next. : )
Posted by @ November 18, 2007 07:40 PM
November 17, 2007
jon787
Verizon blows
But my motorola e815 is now uncrippled successfully :)
Posted by @ November 17, 2007 04:02 AM
November 14, 2007
sgowtham
NFS : Server & Client Set Up With AutoFS
It is not uncommon to find people (or organizations) who have multiple computers at their disposal and more often than not, these people (or organizations) find themselves in following situation:
One of these machines, often pretty powerful, contains data that need to be accessed from one or more of the other machines.
As is the case with most problems, there exists more than one way to solve this issue. This article discusses, in step-by-step fashion, one such possible approach - Network File System (abbreviated as NFS) - as applicable to Red Hat Enterprise Linux distributions. But unlike the previous write-up along similar lines, this one makes use of autofs service on client machines, so that the NFS shares are mounted on demand and are automatically unmounted when they are not being used. Few more suggestions from buddy Chong have also been incorporated to improve the performance.
What is NFS?
According to Wikipedia, it is a network file system protocol originally developed by Sun Microsystems in 1984, allowing a user on a client computer to access files over a network as easily as if the network devices were attached to its local disks. NFS, like many other protocols, builds on the Open Network Computing Remote Procedure Call (ONC RPC) system. The Network File System protocol is specified in RFC 1094, RFC 1813, and RFC 3530.
Disclaimer
There are very many options that can be used while exporting and mounting NFS partitions as well as while custom-configuring the firewall with IPTABLES. Please read through the man pages to see what fits best. Below given instructions are what I used to set up NFS within my internal network and these may very well work for you. However, please note that you are using these instructions at your very own risk and this website, sgowtham.net, is not responsible for any/all damage caused to your property, intellectual or otherwise.
The Server Part
- Let us assume that the IP address of the server is 192.168.1.2
- Login as root
- Decide on two things:
- What file systems should be made available to clients? Let us assume that /usr/local (as read only) and /home (as read/write) partitions need to be exported.
- Which machines/clients (IP range or specific hostnames) should be allowed to access the exported file systems? Let us assume that all machines in the internal network - identified by IP addresses 192.168.1.xxx/255.255.255.0 - should have access to the exported partitions.
- Once the above is determined, this information needs to be put in a file that NFS will look up and do the needful. Add the following to /etc/exports:
# /etc/exports
/usr/local 192.168.1.0/24(ro,async)
/home 192.168.1.0/24(rw,async) - Save and close the file, Run the following command:
exportfs -rva
- Assuming that a full/complete/maximum installation of the linux distribution was done, start the NFS service:
/etc/init.d/nfs start
- If you plan on keeping this service active over reboots, then:
chkconfig - -level 345 nfs on
The Client Part - With AutoFS
- Login as root
- Autofs uses the automount daemon to manage your mount points by only mounting them dynamically when they are accessed. Autofs consults the master map configuration file /etc/auto.master to determine which mount points are defined. It then starts an automount process with the appropriate parameters for each mount point. Each line in the master map defines a mount point and a separate map file that defines the filesystems to be mounted under this mount point. For example, the /etc/auto.misc file might define mount points in the /misc directory; this relationship would be defined in the /etc/auto.master file.
Each entry in auto.master has three fields. The first field is the mount point. The second field is the location of the map file, and the third field is optional (can contain information such as a timeout value).
- To mount the exported partitions under the mount point /misc/, add the following line to auto.master:
/misc /etc/auto.misc –timeout 60
The directory /misc must exist on the local filesystem (it does exist on most Red Hat Linux distributions). There should be no subdirectories in /misc on the local filesystem.
- Add the following line to /etc/auto.misc:
192_168_1_2_usr_local -ro,soft,intr,rsize=8192,wsize=8192 192.168.1.2:/usr/local
192_168_1_2_home -rw,soft,intr,rsize=8192,wsize=8192 192.168.1.2:/home
The first field in /etc/auto.misc is the name of the /misc subdirectory. This directory is created dynamically by automount. It should not actually exist on the client machine. The second field contains mount options. The third field is the location of the NFS export including the hostname and directory.
- Once the above is done, start the AutoFS service:
/etc/init.d/autofs restart
- If you plan on keeping this set up active over reboots, then run:
chkconfig - -level 345 autofs on
- If you modify the /etc/auto.master configuration file while autofs is running, the automount daemon(s) must be notified to reload by typing the following command at a shell prompt:
/sbin/service autofs reload
- To access the mounted NFS partition,
cd /misc/192_168_1_2_home
(or something similar) - 192_168_1_2_home folder as well as its content will automagically show up.
Troubleshooting
In spite of rigorously following the above steps (some of which were adopted from the Red Hat documentation), I could not proceed beyond /etc/init.d/autofs restart
stage - it would just fail and repetitively so. Fortunately, the troubleshooting I did for the previous entry solved this one as well. For completeness sake, here it is: First thing I had to check was to make sure I was using the proper syntax (in commands) and appropriate arguments/options for a given command. Since the error was very easily reproducible, I thought SELinux (Security Enhanced Linux) feature might be obstructing proper functioning of NFS and as such, I disabled it. As root, I edited the /etc/sysconfig/selinux (in server as well as client) and made it look like:
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - SELinux is fully disabled.
SELINUX=disabled
# SELINUXTYPE= type of policy in use. Possible values are:
# targeted - Only targeted network daemons are protected.
# strict - Full SELinux protection.
# SELINUXTYPE=targeted
After rebooting (both server and client) and re-attempting the NFS set up, I still got the same error message - meaning, something else was obstructing the process. A little bit of digging around and Google!ng led me to believe that the default firewall rules in the server were the culprit. The following steps were followed to resolve this issue:
- Login as root on the server (192.168.1.2)
- cd /etc/sysconfig/
- cp iptables iptables.default
- cd
- Based on firewall rules implemented in a beowulf linux cluster, I created a file called custom_firewall.sh, with following contents:
#! /bin/bash
#
# Define a local variable, IPTABLES
export IPTABLES=/sbin/iptables# Flush out all existing rules
$IPTABLES -F INPUT# Set default Policy for Input, Output and Forward chains
# If nothing else matches, these are followed
$IPTABLES -P INPUT ACCEPT
$IPTABLES -P OUTPUT ACCEPT
$IPTABLES -P FORWARD DROP# Allow self-access by loopback interface
$IPTABLES -A INPUT -i lo -p all -j ACCEPT
$IPTABLES -A OUTPUT -o lo -p all -j ACCEPT# Accept established connections
$IPTABLES -A INPUT -i eth0 -p tcp -m state –state ESTABLISHED -j ACCEPT
$IPTABLES -A INPUT -i eth0 -p udp -m state –state ESTABLISHED -j ACCEPT
$IPTABLES -A INPUT -i eth0 -p icmp -m state –state ESTABLISHED -j ACCEPT# Ping requests
$IPTABLES -A INPUT -p icmp -j ACCEPT# FTP requests - not secure enough
$IPTABLES -A INPUT -p tcp –dport 20 -j DROP
$IPTABLES -A INPUT -p tcp –dport 21 -j DROP# TelNet requests - not secure enough
$IPTABLES -A INPUT -p tcp –dport 23 -j DROP# HTTP requests
$IPTABLES -A INPUT -p tcp –dport 80 -j ACCEPT
$IPTABLES -A INPUT -p tcp –dport 443 -j ACCEPT# SSH requests - allows ssh, scp and sftp requests
$IPTABLES -A INPUT -p tcp –dport 22 -s 192.168.1.0/255.255.255.0 -j ACCEPT# If more than 5 packets are dropped in 3 seconds they will be ignored
# Helps to prevent a DOS attack crashing the computer
$IPTABLES -A INPUT -m limit –limit 3/second –limit-burst 5 -i ! lo -j LOG# NFS
$IPTABLES -A INPUT -p tcp –dport nfs -s 192.168.1.0/255.255.255.0 -j ACCEPT
$IPTABLES -A INPUT -p udp –dport nfs -s 192.168.1.0/255.255.255.0 -j ACCEPT
$IPTABLES -A INPUT -p tcp –dport 111 -s 192.168.1.0/255.255.255.0 -j ACCEPT
$IPTABLES -A INPUT -m state –state ESTABLISHED,RELATED -j ACCEPT# Keep track of log in attempts - /var/log/messages
$IPTABLES -A INPUT -j LOG –log-prefix “INPUT_DROP: ”
$IPTABLES -A OUTPUT -j LOG –log-prefix “OUTPUT_DROP: ”
/sbin/service iptables save
After these steps, my attempt to set up NFS (both server and client with AutoFS) worked just fine. I understand my options for NFS as well as the firewall rules are neither comprehensive nor complete. As such, I (as well as others) would very much appreciate any thoughts to improve them.
Posted by @ November 14, 2007 02:30 PM
November 11, 2007
spi
sometimes lyrics speak to me
I’m walking in the desert land
I’m walking without a plan
The sun will rise stars will fall
- Michigan “Valley of Death”
Posted by @ November 11, 2007 03:26 AM
November 09, 2007
sgowtham
NFS : Server & Client Set Up
It is not uncommon to find people (or organizations) who have multiple computers at their disposal and more often than not, these people (or organizations) find themselves in following situation:
One of these machines, often pretty powerful, contains data that need to be accessed from one or more of the other machines.
As is the case with most problems, there exists more than one way to solve this issue. This article discusses, in step-by-step fashion, one such possible approach - Network File System (abbreviated as NFS) - as applicable to Red Hat Enterprise Linux distributions.
What is NFS?
According to Wikipedia, it is a network file system protocol originally developed by Sun Microsystems in 1984, allowing a user on a client computer to access files over a network as easily as if the network devices were attached to its local disks. NFS, like many other protocols, builds on the Open Network Computing Remote Procedure Call (ONC RPC) system. The Network File System protocol is specified in RFC 1094, RFC 1813, and RFC 3530.
Disclaimer
There are very many options that can be used while exporting and mounting NFS partitions as well as while custom-configuring the firewall with IPTABLES. Please read through the man pages to see what fits best. Below given instructions are what I used to set up NFS within my internal network and these may very well work for you. However, please note that you are using these instructions at your very own risk and this website, sgowtham.net, is not responsible for any/all damage caused to your property, intellectual or otherwise.
The Server Part
- Let us assume that the IP address of the server is 192.168.1.2
- Login as root
- Decide on two things:
- What file systems should be made available to clients? Let us assume that /usr/local (as read only) and /home (as read/write) partitions need to be exported.
- Which machines/clients (IP range or specific hostnames) should be allowed to access the exported file systems? Let us assume that all machines in the internal network - identified by IP addresses 192.168.1.xxx/255.255.255.0 - should have access to the exported partitions.
- Once the above is determined, this information needs to be put in a file that NFS will look up and do the needful. Add the following to /etc/exports:
# /etc/exports
/usr/local 192.168.1.0/24(ro,sync)
/home 192.168.1.0/24(rw,sync) - Save and close the file, Run the following command:
exportfs -rva
- Assuming that a full/complete/maximum installation of the linux distribution was done, start the NFS service:
/etc/init.d/nfs start
- If you plan on keeping this service active over reboots, then:
chkconfig - -level 345 nfs on
The Client Part
- Login as root
- Decide on the following:
- Where will the exported file systems/partitions (from the Server) be mounted? Let us assume that /usr/local will be mounted at /mnt/192_168_1_2/usr_local (as read only) and /home will be mounted at /mnt/192_168_1_2/home (as read/write).
- To that effect, create those mount points:
mkdir -p /mnt/192_168_1_2/usr_local
mkdir -p /mnt/192_168_1_2/home
- Once the above is done, mount the exported file systems:
mount -t nfs 192.168.1.2:/usr/local /mnt/192_168_1_2/usr_local
mount -t nfs 192.168.1.2:/home /mnt/192_168_1_2/home - If you plan on keeping this set up active over reboots, then add the following lines to /etc/fstab:
192.168.1.2:/usr/local /mnt/192_168_1_2/usr_local nfs ro,sync,timeo=14,root_squash 0 0
192.168.1.2:/home /mnt/192_168_1_2/home nfs rw,sync,timeo=14,root_squash 0 0 - Save and close the file.
Troubleshooting
One of the most common problems that bugged me for a while was the following: When
mount -t nfs 192.168.1.2:/usr/local /mnt/192_168_1_2/usr_local
is executed on the client, it results in the following error:
mount: mount to NFS server ‘192.168.1.2′ failed: System Error: No route to host.
First thing I had to check was to make sure I was using the proper syntax (in commands) and appropriate arguments/options for a given command. Since the error was very easily reproducible, I thought SELinux (Security Enhanced Linux) feature might be obstructing proper functioning of NFS and as such, I disabled it. As root, I edited the /etc/sysconfig/selinux (in server as well as client) and made it look like:
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - SELinux is fully disabled.
SELINUX=disabled
# SELINUXTYPE= type of policy in use. Possible values are:
# targeted - Only targeted network daemons are protected.
# strict - Full SELinux protection.
# SELINUXTYPE=targeted
After rebooting (both server and client) and re-attempting the NFS set up, I still got the same error message - meaning, something else was obstructing the process. A little bit of digging around and Google!ng led me to believe that the default firewall rules in the server were the culprit. The following steps were followed to resolve this issue:
- Login as root on the server (192.168.1.2)
- cd /etc/sysconfig/
- cp iptables iptables.default
- cd
- Based on firewall rules implemented in a beowulf linux cluster, I created a file called custom_firewall.sh, with following contents:
#! /bin/bash
#
# Define a local variable, IPTABLES
export IPTABLES=/sbin/iptables# Flush out all existing rules
$IPTABLES -F INPUT# Set default Policy for Input, Output and Forward chains
# If nothing else matches, these are followed
$IPTABLES -P INPUT ACCEPT
$IPTABLES -P OUTPUT ACCEPT
$IPTABLES -P FORWARD DROP# Allow self-access by loopback interface
$IPTABLES -A INPUT -i lo -p all -j ACCEPT
$IPTABLES -A OUTPUT -o lo -p all -j ACCEPT# Accept established connections
$IPTABLES -A INPUT -i eth0 -p tcp -m state –state ESTABLISHED -j ACCEPT
$IPTABLES -A INPUT -i eth0 -p udp -m state –state ESTABLISHED -j ACCEPT
$IPTABLES -A INPUT -i eth0 -p icmp -m state –state ESTABLISHED -j ACCEPT# Ping requests
$IPTABLES -A INPUT -p icmp -j ACCEPT# FTP requests - not secure enough
$IPTABLES -A INPUT -p tcp –dport 20 -j DROP
$IPTABLES -A INPUT -p tcp –dport 21 -j DROP# TelNet requests - not secure enough
$IPTABLES -A INPUT -p tcp –dport 23 -j DROP# HTTP requests
$IPTABLES -A INPUT -p tcp –dport 80 -j ACCEPT
$IPTABLES -A INPUT -p tcp –dport 443 -j ACCEPT# SSH requests - allows ssh, scp and sftp requests
$IPTABLES -A INPUT -p tcp –dport 22 -s 192.168.1.0/255.255.255.0 -j ACCEPT# If more than 5 packets are dropped in 3 seconds they will be ignored
# Helps to prevent a DOS attack crashing the computer
$IPTABLES -A INPUT -m limit –limit 3/second –limit-burst 5 -i ! lo -j LOG# NFS
$IPTABLES -A INPUT -p tcp –dport nfs -s 192.168.1.0/255.255.255.0 -j ACCEPT
$IPTABLES -A INPUT -p udp –dport nfs -s 192.168.1.0/255.255.255.0 -j ACCEPT
$IPTABLES -A INPUT -p tcp –dport 111 -s 192.168.1.0/255.255.255.0 -j ACCEPT
$IPTABLES -A INPUT -m state –state ESTABLISHED,RELATED -j ACCEPT# Keep track of log in attempts - /var/log/messages
$IPTABLES -A INPUT -j LOG –log-prefix “INPUT_DROP: ”
$IPTABLES -A OUTPUT -j LOG –log-prefix “OUTPUT_DROP: ”
/sbin/service iptables save
After these steps, my attempt to set up NFS (both server and client) worked just fine. I understand my options for NFS as well as the firewall rules are neither comprehensive nor complete. As such, I (as well as others) would very much appreciate any thoughts to improve them.
Posted by @ November 09, 2007 10:08 PM
October 30, 2007
mary
Is christmas coming up again?
I’m already getting asked for my Christmas list… So here goes… These items go for other holidays like…my birthday, thanksgiving, hanukkah, new years, veterans day, etc.
-
Bogen-Manfrotto 725B Digi Tripod with Integrated Ball Head - This is the *least* expensive tripod that will meet my needs. Talk to me or someone that knows about photography before selecting another one. - Nikon 105mm f/2.8G ED-IF AF-S VR Micro-Nikkor Lens
- Extra Battery for my Nikon D80.
- Extra bowl for my KitchenAid mixer. I have the 5-quart bowl lift type mixer.
iPod TouchNeo1973 after version 2 (GTA02) gets releasedR