>Hey, what have you noticed on this..  what version are you using of
>ipnat?  See my problem is that ipnat totally stops working after about
>18 hours or so...
>
>If its a bug in ipnat, there must be a fix somewhere for it....  That's
>a pretty major issue to a lot of people.  I'll try using the latest
>version of ipnat.  Right now i'm using netbsd-current kernel and ipnat
>from release 1.6.  (The 1.6 kernel won't run on my system because it
>gives memory errors and page faults and stuff)
>
>Greg

No, there are some posts on google about this being a chipset issue on the 
VT8601a, even on windoh$... IPNAT might have it's share of problems, but 
fixing it it won't fix lousy hardware

>
>On Thu, Nov 14, 2002 at 11:04:41AM +0100, Martin Husemann wrote:
>> On Wed, Nov 13, 2002 at 03:04:10PM -0600, netbsd@jayhackers.net wrote:
>> 
>> > the system and do a "ipnat -l" to list active sessions, i see a couple of
>> > normal nat mappings and then i see a few "kmemcpy: bad address at 0xnnnnnn"
>> > errors.
>> 
>> I've seen that too, I guess it is a bug in the ipnat kernel part or the
>> ipnat utility.
>> 
>> It's most likely unrelated to your other problems.
>> 
>> Martin
>