
| Anonymous | Login | Signup for a new account | 2010-07-29 20:29 CEST |
| Main | My View | View Issues | Change Log | Roadmap | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0000566 | [Endian Firewall] Firewall (iptables) | minor | always | 2008-02-15 21:32 | 2008-07-27 22:18 | ||||
| Reporter | jaebird | View Status | public | ||||||
| Assigned To | peter | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Product Version | 2.2-beta2 | ||||||
| Summary | 0000566: Local Network Ping Limit Unacceptable | ||||||||
| Description |
In our use of endian we use ping to verify that the network is available to remote network nodes. They ping the default gateway, which happens to be endian firewall. The default setup limits the ping responses to once per second. This causes remote nodes to timeout when more than one node is "pinging" endian. |
||||||||
| Additional Information |
WARNING: I have not evaluated the DOS security implications of the following workaround. Workaround: In the following file: /usr/local/bin/setxtaccess.py comment out the line below: # iptables += " -m limit --limit 1/second" |
||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
|
|
|||||||||
Notes |
|
|
(0000919) peter (administrator) 2008-02-15 22:02 |
should probably be done with -m hashlimit and maybe with different or ideally configurable limits for local zones/red |
| Mantis [^] Copyright © 2000 - 2008 Mantis Group |