/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! /* ALSO: Don't quote this header. It makes you look lame :-) */
Alex Gein <[EMAIL PROTECTED]> wrote: > > I've tried looking through the logs for error messages, but I'm not > exactly sure which log to look at. The log will be the one to which kernel messages are directed. You can examine /etc/syslog.conf to see where "kern" messages are sent. Since I don't have a Red Hat machine handy, I'm not sure what the default location is. Alternatively, you can simply type "dmesg" to see the last couple screens of kernel messages. Since ip masq is a kernel function, any failures will be shown in the kernel log. > I don't use ipchains either, I use iptables (Kernel 2.4). Well, you didn't say, so it was just a guess. To view the connection table under 2.4/iptables, simply "cat /proc/net/ip_conntrack". > >Problems with autofw will only arise if you use it. > > This is the same logic I followed, but the HOWTO leads me to think it > will be used automatically or something The HOWTO information must be old, because there is no autofw (or portfw) functionality in the 2.4 kernels. Connection-forwarding is handled in a completely different fashion, using the NAT table. -- [EMAIL PROTECTED] (Fuzzy Fox) || "Good judgment comes from experience. sometimes known as David DeSimone || Experience comes from bad judgment." _______________________________________________ Masq maillist - [EMAIL PROTECTED] Admin requests can be handled at http://www.indyramp.com/masq-list/ -- THIS INCLUDES UNSUBSCRIBING! or email to [EMAIL PROTECTED] PLEASE read the HOWTO and search the archives before posting. You can start your search at http://www.indyramp.com/masq/ Please keep general linux/unix/pc/internet questions off the list.
