[Linux-Anyway] More Re: Re: eth1

  • From: Meph Istopheles <meph@xxxxxxxxxxx>
  • To: Linux-Anyway@xxxxxxxxxxxxx
  • Date: Thu, 6 Mar 2003 12:42:01 -0800 (PST)

  Hey,

  Looking round at stuff on ipmasq, I find a lot to do with 
iptables.  So, I run:

# /sbin/ipchains -L
Chain input (policy ACCEPT):
target     prot opt     source                destination           
ports
ACCEPT     udp  ------  news.zipcon.net      anywhere              
domain ->   1025:65535
ACCEPT     udp  ------  w3.zipcon.net        anywhere              
domain ->   1025:65535
ACCEPT     tcp  -y----  anywhere             anywhere              
any ->   swat
ACCEPT     tcp  -y----  anywhere             anywhere              
any ->   ssh
ACCEPT     tcp  -y----  anywhere             anywhere              
any ->   http
ACCEPT     tcp  -y----  anywhere             anywhere              
any ->   ftp
ACCEPT     all  ------  anywhere             anywhere              
n/a
ACCEPT     all  ------  anywhere             anywhere              
n/a
ACCEPT     all  ------  anywhere             anywhere              
n/a
REJECT     tcp  -y----  anywhere             anywhere              
any ->   0:1023
REJECT     tcp  -y----  anywhere             anywhere              
any ->   nfs
REJECT     udp  ------  anywhere             anywhere              
any ->   0:1023
REJECT     udp  ------  anywhere             anywhere              
any ->   nfs
REJECT     tcp  -y----  anywhere             anywhere              
any ->   x11:6009
REJECT     tcp  -y----  anywhere             anywhere              
any ->   xfs
Chain forward (policy ACCEPT):
target     prot opt     source                destination           
ports
MASQ       all  ------  10.0.0.0/24          anywhere              
n/a
Chain output (policy ACCEPT):

  Why's my masq still st to 10.0.0.0/24?  How do I change that?

  Then, with nat:

# /sbin/iptables -t nat -L
/lib/modules/2.4.18-24.7.x/kernel/net/ipv4/netfilter/ip_tables.o: 
init_module: Device or resource busy
Hint: insmod errors can be caused by incorrect module parameters, 
including invalid IO or IRQ parameters.
      You may find more information in syslog or the output from 
dmesg
/lib/modules/2.4.18-24.7.x/kernel/net/ipv4/netfilter/ip_tables.o: 
insmod 
/lib/modules/2.4.18-24.7.x/kernel/net/ipv4/netfilter/ip_tables.o 
failed
/lib/modules/2.4.18-24.7.x/kernel/net/ipv4/netfilter/ip_tables.o: 
insmod ip_tables failed
iptables v1.2.5: can't initialize iptables table `nat': iptables 
who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.

  I know almost nothing about iptables.  Can anyone tell me 
what's up with all this?

  Meph

-- 
  There is an old time toast which is golden for its beauty.
  "When you ascend the hill of prosperity may you not meet a 
  friend."
  -Mark Twain
To unsubcribe send e-mail with the word unsubscribe in the body to:   
Linux-Anyway-Request@xxxxxxxxxxxxx?body=unsubscribe

Other related posts: