This is an old revision of the document!
The firewall was constructed with the PCXFirewall Toolkit available here: http://pcxfirewall.sourceforge.net/ After determining list of services to be offered, a list of open ports was created. The following list enumerates that list.
Admin instructions on how to access PCXFirewall
https://63.252.5.3/pcxfirewall/
username – admin
Firewall Config – budlight1
Config Options
Validity Check:
Zones:
Special Protocol Modules:
Rate Limit:
Logging:
Dynamic Interfaces:
Index | Host | LimitTo | Active | Comment |
---|---|---|---|---|
10.0.0.0/8 | false | Class A | ||
192.168.0.0/16 | false | Class C | ||
127.0.0.0/8 | true | Local machine | ||
172.16.0.0/12 | false | Class B | ||
224.0.0.0/4 | false | Class D Multicast | ||
240.0.0.0/5 | true | Class E Reserved | ||
0.0.0.0/8 | false | Illegal except for DHCP | ||
169.254.0.0/16 | true | Link Local Networks | ||
192.0.2.0/24 | false | TEST-NET |
Existing services were left as preconfigured.
Added : POP3s
in | out | ip | source | dest | action | service | active |
---|---|---|---|---|---|---|---|
firewallToExternal | |||||||
* | ALL | ALL | ACCEPT | DNS, SSH, IDENT, SMTP, ICMP, TRACEROUTE, SQUID, HTTP, FTP, BOOTP, NTP, RSYNC | true | ||
externalToFirewall | |||||||
* | ALL | ALL | ACCEPT | SSH, SMTP, POP3, IMAP, ICMP-limited, HTTP, HTTPS, BOOTP, IMAPS, POP3S | true | ||
* | ALL | ALL | Reject | IDENT | true | ||
external | ALL | ALL | Drop No Log | SMB | true | ||
external | ALL | ALL | ACCEPT | Webmin | true | ||
externalBroadcast | |||||||
* | ALL | ALL | ACCEPT | BOOTP | true |
get this from PCXFirewall instructions and put here
Please post changes here in the format of: [H4] date|your name [/H4] [CR]description of chages made
Added Path to allow Webmin access. This was added as a seperate path to allow an easier way to turn the path on or off as needed.
The initial installation
Changed Zone "external" to current static IP address
Get installation instructions and have James verify
need to get how to access and use front end.
Initially installed, configured, and documented by James Pattie and Carl Fitch, 2005-02-19.