Red Hat has a rather different tree of configuration files than some
other Linux distributions. The unique stuff is mostly under
/etc/sysconfig/
Documentation files for this ship with recent versions of RH, and are
in the latest User's Guide.
One important file is
I have been masq'ing for about 6 months now and am just curious about
something...
I am masqing a dialup connection, using diald, kernel 2.0.34 on a RH 5 box.
I'm getting the error "MASQ: failed TCP/UDP checksum from [ip]" errors when I
run dmesg. It doesnt seem to be a big problem because I
1. will all the daemons on the linux box run perfectly normally under this
setup? i.e. can outside people telnet to the 386 even if it's
masquerading? (i think i know this one, but i'm just checking)
Only if you let them. I highly recommend that you at least setup
the /etc/hosts.* files to
I am masqing a dialup connection, using diald, kernel 2.0.34 on a RH 5 box.
I'm getting the error "MASQ: failed TCP/UDP checksum from [ip]" errors when I
run dmesg.
heheh.. Is this in the FAQ yet?
The dreaded "MASQ: failed TCP/UDP checksum from [ip]" errors are
from upstream
with kernel 2.0.35, with cacheing named, and sometimes it works well, and
sometimes not. What doesn't work well is a Win 95 box on my network
looking at http://www.linuxhq.com (and many others).
Did this happen with 2.0.34? Personally, this sounds like our
famous MTU bug. Set your Internet
/proc/sys/net/ip_forwarding = 1
Try "echo "1" /proc/sys/net/ipv4/ip_forwarding"
Notice the addition of the ipv4 stuff.
--David
..
| David A. Ranch - Remote Access/Linux/PC hardware [EMAIL PROTECTED] |
!
The first card eth0 is working fine using dhcpcd (I am a mediaone subscriber
via a cable modem) I can ping and do what ever with it. Now how do I set up
the second card, eth1.
Just make sure that the card support is compiled into the kernel,
install the new NIC, and boot up.
Be
ipfwadm -M -s 1800 0 0
However, entering such a command returns:
ipfwadm: setsockopt failed: Invalid argument
You probably aren't using the PATCHED IPFWADM program. Get it
here:
http://www.tor.shaw.wave.ca/~ambrose/ipfwadm.gz
or get just the patch at:
I have token ring and fast ethernet subnets on my network. I have
successfully setup masq'ing on the fast ethernet side and can access from
Win 95 and NT clients, no problem. My problem occurs when I try to
access the masq box from the TR side. Here is my layout.
| masq box |
I've been having lots of problems re-compiling the kernel to include
support for IPMasq. I'm using RedHat 5.0 and I've tried the same thing on
RedHat 5.1. I always get a "error 2", some kind of linking error. How
necessary is it to re-compile when using a RedHat precompiled kernel?
I've heard
I've been trying to get ip-masq set up for the first time on a little
four-machine network, and, to put it bluntly, it's working weirdly.
I'm using Linux-2.0.35 (i.e. this is ipfwadm land, not ipchains land).
I've got this fairly paranoid, mostly-stolen-from-someone-else
firewall config,
On 28 Jul 98, at 19:07, Benjamin K. Andrus wrote:
I have two 3c509 cards in my machine and I can see them both when booting
(eth0, eth1)
eth1. What lines do I add to what files and then what lines do I need to
add to set up the masquerading stuff so that the linux box will forward the
On Wed, 29 Jul 1998, David A. Ranch wrote:
/proc/sys/net/ip_forwarding = 1
Try "echo "1" /proc/sys/net/ipv4/ip_forwarding"
Notice the addition of the ipv4 stuff.
yeap, noticed it was a typo :) But it appaears as if the -W eth0
on my end should have been -W ppp0 ( or simply
The "proper" way to do this is to edit
/etc/sysconfig/network and change
FORWAR_IPV4=false to FORWARD_IPV4=true
--
Bill Eldridge
Radio Free Asia
[EMAIL PROTECTED]
-Original Message-
From: James Michael Keller [EMAIL PROTECTED]
To: David A. Ranch [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
On Tue, 28 Jul 1998, jac--no-spam wrote:
Red Hat has a rather different tree of configuration files than some
other Linux distributions. The unique stuff is mostly under
/etc/sysconfig/
Documentation files for this ship with recent versions of RH, and are
in the latest User's
The "proper" way to do this is to edit
/etc/sysconfig/network and change
FORWAR_IPV4=false to FORWARD_IPV4=true
Agreed... for Redhat.
--David
..
| David A. Ranch - Remote Access/Linux/PC hardware [EMAIL
Hey David,
W95(MTU=1500)-ethernet--(MTU=1006)eth0:Linux:diald(MTU1500)-phone-internet
Just curious, why did you have a MTU of 1006 in the first place?
route -n # list the routing table w/o DNS lookups
Kernel routing table
Destination Gateway Genmask Flags MSS
Nice tutorial. I've saved it, and I'm going to shuffle it off into my
/usr/doc directory. Achau and LDP, are you listening?
Jack Carroll
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
On Tue, 28 Jul 1998, jac--no-spam wrote:
Nice tutorial. I've saved it, and I'm going to shuffle it off into my
/usr/doc directory. Achau and LDP, are you listening?
Thanks!
The text is GPL'd, so that would be fine. Perhaps Stephen would
prefer that his name and email be
19 matches
Mail list logo
