Date: Wed, 23 Apr 1997 11:27:11 -0700 (PDT) From: Chris Coleman <chris@dilbert.bb.cc.wa.us> To: Darren Reed <avalon@coombs.anu.edu.au> Cc: hackers@freebsd.org Subject: Re: IPFILTER Message-ID: <Pine.BSF.3.91.970423111912.236A-100000@dilbert.bb.cc.wa.us> In-Reply-To: <199704231151.EAA11031@dilbert.bb.cc.wa.us>
next in thread | previous in thread | raw e-mail | index | archive | help
These are the rules that i would like to have work: map fxp0 10.17.0.0/16 -> 208.8.136.182/32 portmap tcp/udp 10000:65000 map fxp0 10.16.11.0/24 -> 208.8.136.180/32 portmap tcp/udp 10000:65000 map fxp0 10.16.4.0/24 -> 208.8.136.181/32 portmap tcp/udp 10000:65000 map fxp0 10.12.0.0/16 -> 208.8.136.184/32 portmap tcp/udp 10000:65000 map fxp0 10.16.0.0/16 -> 208.8.136.185/32 portmap tcp/udp 10000:65000 map fxp0 10.0.0.0/8 -> 208.8.136.10/32 portmap tcp/udp 10000:65000 But when ever i do it, the internet stops working for all the virtual address i have set up. I do an ipnat -ls and it shows that is has mapped things according to what i specified. Have i specified something wrong? Can i specify different ip addresses to go out the same etherNIC? I also had a problem with ipnat -FC. when i tried to Flush the active routes, it causes a panic :free: too many frees. and the system reboots. it only happens when i have it running for a while. when i first start it i can Clear and Flush perfectly. But it seems to be associated with the load, or number of active links that have been mapped in. Also, after it had been up about 30+ days, all of a sudden it just froze up. I am not sure if it had anything to do with ipnat, but that was all that was running on the machine, i was wondering if there might be a limit as to how many active routes it can handle before it needs reset. or if there might be a memory leak or something. I am running the LKM version 3.1.4 of ipfilter, but only using the ipnat stuff. Thanks. --Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.970423111912.236A-100000>