Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Michel Benoit" <murpme@gmail.com>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: IP forwarding with MASQUERADE
Date: Wed, 8 Oct 2008 18:18:17 +0200	[thread overview]
Message-ID: <c88e466f0810080918i5d5491eet2cbcb710be0b74aa@mail.gmail.com> (raw)
In-Reply-To: <c88e466f0810080916x3e58de7cod018200f3b8e8c29@mail.gmail.com>

> I'm not an expert, so I answer it as a PM:

Out of curiosity, what does 'PM' stand for in this context?

>> I believe the connections that connection tracking is keeping
>> track of
>> are listed somewhere in /proc, but I don't know where off hand.
>
>> > My root file system is read-only?  Could that cause
>> problems?  Does the
>> > netfilter code generate any files in the root filesystem?
>
> Is your /proc filesystem writeable ?

The /proc filesystem seems to be rw:

# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / ext2 ro 0 0
proc /proc proc rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
tmpfs /tmp tmpfs rw 0 0
sysfs /sys sysfs rw 0 0
usbfs /proc/bus/usb usbfs rw 0 0
/dev/mtdblock6 /mnt/flash yaffs2 rw 0 0


BTW, Ii'm not running udev.  All /dev entries are statically created
as part of the rootfs.
Are there any /dev entries that must be present for masquerading to work?

      parent reply	other threads:[~2008-10-08 16:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-03 12:07 IP forwarding with MASQUERADE Michel Benoit
2008-10-03 14:23 ` Grant Taylor
2008-10-07 15:58   ` Michel Benoit
2008-10-07 18:15     ` Grant Taylor
2008-10-08 16:12       ` Michel Benoit
2008-10-09 16:36         ` Michel Benoit
     [not found]       ` <B1254A48FE0EE04BAC4A09DD26CBF50203DA62A0@s080a1034.group.rwe.com>
     [not found]         ` <c88e466f0810080916x3e58de7cod018200f3b8e8c29@mail.gmail.com>
2008-10-08 16:18           ` Michel Benoit [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c88e466f0810080918i5d5491eet2cbcb710be0b74aa@mail.gmail.com \
    --to=murpme@gmail.com \
    --cc=netfilter@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox