Re: natd restart

2002-01-27 Thread Crist J. Clark
On Sun, Jan 27, 2002 at 09:53:56PM +0100, Clemens Hermann wrote: > Am 27.01.2002 um 18:43:11 schrieb Andre Oppermann: > > Hi Andre, > > > Have a look at IPFILTER where IPNAT is part of. It does everything in > > the kernel. > > to come back to my initial question: is there a way to modify ipnat

Re: natd restart

2002-01-27 Thread Matthew Emmerton
> Am 27.01.2002 um 09:59:14 schrieb Matthew Emmerton: > > Hi Matthew, > > > Why not just add an IP alias for the "new" network on each machine? Each > > system will respond to packets directed to either network, but without the > > complexity of a NAT box in the middle. Once you've got everything

Re: natd restart

2002-01-27 Thread Clemens Hermann
Am 27.01.2002 um 09:59:14 schrieb Matthew Emmerton: Hi Matthew, > Why not just add an IP alias for the "new" network on each machine? Each > system will respond to packets directed to either network, but without the > complexity of a NAT box in the middle. Once you've got everything switched,

Re: natd restart

2002-01-27 Thread Clemens Hermann
Am 27.01.2002 um 18:43:11 schrieb Andre Oppermann: Hi Andre, > Have a look at IPFILTER where IPNAT is part of. It does everything in > the kernel. to come back to my initial question: is there a way to modify ipnat rules without breaking existing connections? tia /ch -- "Contrary to popula

Re: natd restart

2002-01-27 Thread veedee
On Sun, Jan 27, 2002 at 09:55:03AM -0500, Matthew Emmerton wrote: > > Am 27.01.2002 um 02:11:30 schrieb Matthew Emmerton: > > > > Hi Matt, > > > > > Here's the patch that I wrote some time ago. > > > > thanks a lot! > > Did you send-pr the patch? It seems quite necessary to be added. > > Not yet.

Re: natd restart

2002-01-27 Thread Matthew Emmerton
> (order of quoted mail slightly altered) > > >I'm looking at making natd into a kernel option ("options IPNAT") and using > >a combination of sysctls and a front-end program to manage how nat operates, > >much like "options IPFIREWALL" and ipfw works today. I've been told that 'options IPFILTER'

Re: natd restart

2002-01-27 Thread Julian Elischer
You can also add rules that allow packets that are going over the INTERNAL interface to skip the NAT divert rules. then you'd only be doing it once. On Sun, 27 Jan 2002, Andre Oppermann wrote: > Matthew Emmerton wrote: > > > > > Am 27.01.2002 um 02:11:30 schrieb Matthew Emmerton: > > > > > > H

Re: natd restart

2002-01-27 Thread Andre Oppermann
Matthew Emmerton wrote: > > > Am 27.01.2002 um 02:11:30 schrieb Matthew Emmerton: > > > > Hi Matt, > > > > > Here's the patch that I wrote some time ago. > > > > thanks a lot! > > Did you send-pr the patch? It seems quite necessary to be added. > > Not yet. One of the things that I don't like a

Re: natd restart

2002-01-27 Thread Rogier R. Mulhuijzen
(order of quoted mail slightly altered) >I'm looking at making natd into a kernel option ("options IPNAT") and using >a combination of sysctls and a front-end program to manage how nat operates, >much like "options IPFIREWALL" and ipfw works today. I've been kicking around the idea of making it

Re: natd restart

2002-01-27 Thread Matthew Emmerton
> Am 27.01.2002 um 00:41:23 schrieb Rogier R. Mulhuijzen: > > Hi Roger, > > > What sort of changes are you talking about here? Maybe there's a different > > way of going about it. > > I want to move an existing network from 91.0.0.0/8 to 172.16.0.0/16. > Furthermore name resolution changes from w

Re: natd restart

2002-01-27 Thread Matthew Emmerton
> Am 27.01.2002 um 02:11:30 schrieb Matthew Emmerton: > > Hi Matt, > > > Here's the patch that I wrote some time ago. > > thanks a lot! > Did you send-pr the patch? It seems quite necessary to be added. Not yet. One of the things that I don't like about this patch is that old rules still stay ar

Re: natd restart

2002-01-27 Thread Clemens Hermann
Am 27.01.2002 um 02:11:30 schrieb Matthew Emmerton: Hi Matt, > Here's the patch that I wrote some time ago. thanks a lot! Did you send-pr the patch? It seems quite necessary to be added. greetz /ch -- "Contrary to popular belief, Unix is user friendly. It just happens to be selective abou

Re: natd restart

2002-01-27 Thread Clemens Hermann
Am 27.01.2002 um 00:41:23 schrieb Rogier R. Mulhuijzen: Hi Roger, > What sort of changes are you talking about here? Maybe there's a different > way of going about it. I want to move an existing network from 91.0.0.0/8 to 172.16.0.0/16. Furthermore name resolution changes from wins to dns and

Re: natd restart

2002-01-26 Thread Matthew Emmerton
> On Sat, 26 Jan 2002, Clemens Hermann wrote: > > > Hi, > > > > Is there a way to get natd to reload the config-file without > > terminating? > > There is a natd patch, running around here somewhere, that allows > you to send a HUP signal to natd and have it reload the config. > > You will hav

Re: natd restart

2002-01-26 Thread Nick Rogness
On Sat, 26 Jan 2002, Clemens Hermann wrote: > Hi, > > Is there a way to get natd to reload the config-file without > terminating? There is a natd patch, running around here somewhere, that allows you to send a HUP signal to natd and have it reload the config. You will h

Re: natd restart

2002-01-26 Thread Rogier R. Mulhuijzen
At 23:46 26-1-2002 +0100, Clemens Hermann wrote: >Hi, > >Is there a way to get natd to reload the config-file without terminating? >The only way I found is to stop natd and then start it again. I am afraid that natd is extremely simple, and does not allow any control after it has been started.

natd restart

2002-01-26 Thread Clemens Hermann
Hi, Is there a way to get natd to reload the config-file without terminating? The only way I found is to stop natd and then start it again. As the natd-config changes frequently here (we are changing the used network and we misuse natd to help us) I expect problems when just shuting down natd in