|
L i n u x H e l p
: :
: :
: :
: :
|
Internet Connection Sharing using ipchains Quick down and dirty about how to get your home network on the internet through your linux box. This post should help you with any Red Hat based distro, including Mandrake.
I assume that you already have the network card set up in the windows box. Assuming (I like to do that) that your NIC is seen at boot time by the kernel, to get the card in the linux box running, all you need to do is...
[root@localhost]# ifconfig eth0 192.168.0.1 up
If you're not sure whether or not your NIC is seen at boot time, try the command 'dmesg | grep eth'. If it's not seen, you will need to load the proper module for your NIC.
Then create a file called /etc/sysconfig/network-scripts/ifcfg-eth0
with the following lines in it...
# /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static
IPADDR=192.168.0.1
NETMASK=255.255.255.0
NETWORK=192.168.0.0
BROADCAST=192.168.0.255
ONBOOT=yes
Let's assume once again that you are using a stock 2.2.x series kernel (try the command 'uname -a'). To share your connection with the modem, you should use the linux box to forward packets using ipchains as follows...
# /etc/rc.d/rc.firewall
echo 1 > /proc/sys/net/ipv4/conf/all/rp_filter
echo 1 > /proc/sys/net/ipv4/ip_forward
ipchains -P forward DENY
ipchains -A forward -s 192.168.0.1/24 -j MASQ
For more help with ipchains, read the HOWTO at http://www.linuxdoc.org/HOWTO/IPCHAINS-HOWTO.html
If you're using a 2.4.x series kernel, you need to use iptables to do your packet forwarding. Information on how to use iptables can be found at http://netfilter.samba.org/unreliab...OWTO/index.html
Hope this helps ;-)
-Rick
|
|
|
|
|
L i n u x W o r l d N e w s
: :
: :
: :
: :
|
|
|
What in the hell is a KrnlPanic? Well, a KrnlPanic is me! Actually, let's start with "What is a kernel?". The
kernel is the core of your operating system (OS), whether your OS is Linux, Unix or windows. The kernel takes
care of all process management (what program runs and when), memory management (which parts of memory get used for what) and
also, the kernel takes care of interfacing the OS with your computer's hardware (disk drives, sound card, modem, network card, etc).
Now...since the kernel is doing all of these extremely important jobs, it stands to reason
that if it has an error, it will be a Bad Thing(tm).
If you use windows, you know a kernel panic as a "BSOD" or Blue Screen of Death. Or how about "Invalid Page
Fault in KERNEL32.DLL". I'm sure you've probably seen both of those. In Linux, a Kernel Panic is normally plainly stated
so. At boot time is when you will see most linux panics. I have yet to see a linux kernel panic while the system is running.
You may have seen "Kernel Panic: init not found" or "Kernel Panic: VFS unable to mount root fs on 2:00". All of these previously
listed errors are because of something that happened to the kernel that it couldn't handle, whether it was an access to an
invalid memory location or the inability to find the initialization files it requires.
I hope that sufficiently explains things. Oh yeah...KrnlPanic is also my name ;-)
- Rick
|
|
|
|
|
|
S l a s h d o t / F r e s h m e a t
: :
: :
: :
: :
|
Slashdot and Freshmeat Headlines at 1283543474
(Unixtime)
|
|
|
|
