A Cisco SOHO97 allows you to examine the NAT table.

show ip nat translations

I would be very surprised if you filled up the NAT table on a SOHO97. By
default each entry consumes 160 bytes. It should be able to easily hold
100k translations.

You can't control NAT expiry by port number, but you can control it via IP
protocol. For example, you could expire UDP quicker - but once again, you
wont overflow its table.

-----Original Message-----
From: owner-adsl@unixathome.org [mailto:owner-adsl@unixathome.org] On Behalf
Of Richard Malcolm-Smith
Sent: 3 November 2003 3:43 p.m.
To: adsl@lists.unixathome.org
Subject: RE: Subject: RE: DSE XH7916 Router Setup - what could we do better?

I frequently find the nat table on my M1122 to be filled up resulting in
random things stopping working. I suspect it's the large number of
connections that DC++ has that simply timeout on the PC. I saw similar
behaviour at a mates place on there dse router.

Is there a way to see what entries are in the nat table on any consumer
grade routers and to set them to not expire ones on certain ports etc? I
think this may explain why my ssh sessions that are untouched for hours
close when I try to use them again after coming back.

-----Original Message-----
From: owner-adsl@unixathome.org [mailto:owner-adsl@unixathome.org] On Behalf
Of Warren
Sent: Friday, October 31, 2003 10:49 AM
To: Chris Day
Cc: adsl@lists.unixathome.org
Subject: RE: Subject: RE: DSE XH7916 Router Setup - what could we do better?

On Fri, 2003-10-31 at 22:48, Chris Day wrote:
> The message is LOUD AND CLEAR re multiple logins - I hope to have an
> answer for you all on this next week.
>
> Any other suggestions?
>

A few spring to mind:

* Not having to save & reboot the router when changing options (specifically
to ppp options really - I wanted to make the change, then reboot the unit to
go back to the "saved" settings)

* Bigger NAT cache - I was easily able to push the unit over by having too
many simultaneous web requests (this was from one connected machine)

* Pinhole routing to work.

* Firmware upgradable via non-windows O/S's

* If the web interface says port 80 is only open to the internal net, I
shouldn't be able to find an open port 80 on the internet ...

/My 2c worth.

For the record - I was using firmware rel9v3 - so some of the issues above
may have been solved, however I took the easier option of getting an
internal modem in a machine instead.

Cheers,
Wazza.

-- 
This message is part of the NZ ADSL mailing list. 
see http://unixathome.org/adsl/ for archives, FAQ, 
and various documents. 
To unsubscribe: send mail to majordomo@lists.unixathome.org 
with "unsubscribe adsl" in the body of the message 
 
-- 
This message is part of the NZ ADSL mailing list. 
see http://unixathome.org/adsl/ for archives, FAQ, 
and various documents. 
To unsubscribe: send mail to majordomo@lists.unixathome.org 
with "unsubscribe adsl" in the body of the message 
 
-- 
This message is part of the NZ ADSL mailing list. 
see http://unixathome.org/adsl/ for archives, FAQ, 
and various documents. 
To unsubscribe: send mail to majordomo@lists.unixathome.org 
with "unsubscribe adsl" in the body of the message