Scratch that, I still get the error messages. For some reason they didn't
show up for an hour or two. They usually show up immediately.
-gordon
On Sat, 6 Jan 2001, Gordon Tetlow wrote:
> I used to get this exact same message, although my natd setup worked just
> fine. It was just filling up the
I used to get this exact same message, although my natd setup worked just
fine. It was just filling up the logs. I then added -log_denied to the
arguements for natd and it stopped spewing log messages. Here's what I
run:
/sbin/natd -unregistered_only -use_sockets -punch_fw 5050:10 -log_denied -n
It didn't seem to help for me. I still get lots of permission denied, but
then again, I'm also using a much stricter set of rules.
I seriously hope that the fact we are using 3com etherlink iii cards
doesn't have anything to do with it.
Just to note. As far as I can tell, it's still doing nat ju
rguments I pass to natd:
>
> /sbin/natd -dynamic -unregistered_only -use_sockets -punch_fw 3850:10 -n vx0
>
> On Thu, 30 Nov 2000, Frederik Meerwaldt wrote:
>
> > Date: Thu, 30 Nov 2000 20:25:15 +0100 (CET)
> > From: Frederik Meerwaldt <[EMAIL PROTECTED]>
> > T
/natd -dynamic -unregistered_only -use_sockets -punch_fw 3850:10 -n vx0
On Thu, 30 Nov 2000, Frederik Meerwaldt wrote:
> Date: Thu, 30 Nov 2000 20:25:15 +0100 (CET)
> From: Frederik Meerwaldt <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: natd bug
>
> Hi there!
>
Hi!
> Is your link up at that time? The usual setup for a sppp device using dynamic
> ip's is an invalid ip (0.0.0.0) that is changed once an ip was assigned. So, if
> you are not dialled in, the invalid ip will be put in by natd, and that usually
> causes this error message.
I want the link to
On Thu, Nov 30, 2000 at 08:25:15PM +0100, Frederik Meerwaldt wrote:
> I compiled my kernel with IPDIVERT IPFIREWALL and
> IPFIREWALL_DEFAULT_TO_ACCEPT and I set up only one rule:
> ipfw add divert natd all from any to any via isp0
> Then I started natd (at boot time):
> natd -unregistered_only -dy
Hi!
> # ipfw add divert natd all from any to any via isp0
I have exactly this line in my config (see my original posting)
Best Regards,
Freddy
--
Geek Code 3.1: GCS s+: a--- C+++ UBOU+++ P-- E--- W++ N w--- V++ PGP- t? 5? tv
===
t;[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 30, 2000 8:25 PM
Subject: natd bug
> Hi there!
>
> I was just looking why my natd doesnt work, when I discovered the
> following bug (?):
>
> I compiled my kernel with IPDIVERT IPFIREWALL and
> IPFIREWALL
Hi there!
I was just looking why my natd doesnt work, when I discovered the
following bug (?):
I compiled my kernel with IPDIVERT IPFIREWALL and
IPFIREWALL_DEFAULT_TO_ACCEPT and I set up only one rule:
ipfw add divert natd all from any to any via isp0
Then I started natd (at boot time):
natd -un
On Wed, Sep 27, 2000 at 12:34:36AM -0400, David G. Andersen wrote:
> With natd+ipfw, I was setting up a front-end firewall for
> a client. The firewall has several real IP addresses
> (we'll call them 10.0.0.1 and 10.0.0.2) and two
> MS PPTP servers behind it.
>
>
> 10.0.0.1
>
With natd+ipfw, I was setting up a front-end firewall for
a client. The firewall has several real IP addresses
(we'll call them 10.0.0.1 and 10.0.0.2) and two
MS PPTP servers behind it.
10.0.0.1
10.0.0.2
World- | firewall | - PPTP-1 192.168.1.1
Hi all,
I've configured my Server as a router, so when I'm online, I automatically
start natd, to let my other computers use my server as a gateway. But thw
problem is, that NATD dies after about 10 Minutes. The process is still
there, but I can't route anymore. After flushing all rules and start
13 matches
Mail list logo
