|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
|
|
Many messages from pf to the console in blue background and white font.Hi,
I started getting these messages on the console for twol of my firewalls. What is actually wrong? on firewall1 --------- Nov 9 10:51:17 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.4.7 state: TCP in wire: 172.16.4.7:2530 192.168.1.222:80 stack: - [lo=3729906553 high=3729906554 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=3729906552 Nov 9 10:51:18 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.8.20 state: TCP in wire: 172.16.8.20:4151 192.168.1.222:80 stack: - [lo=2255608505 high=2255608506 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=2255608504 Nov 9 10:51:19 risen /bsd: pf_map_addr: selected address 115.109.4.234 Nov 9 10:51:20 risen last message repeated 6 times Nov 9 10:51:23 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.4.7 state: TCP in wire: 172.16.4.7:2530 192.168.1.222:80 stack: - [lo=3729906553 high=3729906554 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=3729906552 Nov 9 10:51:23 risen /bsd: pf_map_addr: selected address 115.109.4.234 Nov 9 10:51:24 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.8.20 state: TCP in wire: 172.16.8.20:4151 192.168.1.222:80 stack: - [lo=2255608505 high=2255608506 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=2255608504 Nov 9 10:51:27 risen /bsd: pf_map_addr: selected address 115.109.4.234 Nov 9 10:51:47 risen last message repeated 13 times Nov 9 10:51:47 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.8.18 state: TCP in wire: 172.16.8.18:3187 192.168.1.222:80 stack: - [lo=426896319 high=426896321 win=10607 modulator=0] [lo=0 high=1 win=1 modulator=0] 2:0 seq=426896319 Nov 9 10:51:52 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.4.7 state: TCP in wire: 172.16.4.7:2535 192.168.1.222:80 stack: - [lo=2818466821 high=2818466823 win=65535 modulator=0] [lo=0 high=1 win=1 modulator=0] 2:0 seq=2818466821 Nov 9 10:51:53 risen /bsd: pf_map_addr: selected address 115.109.4.234 Nov 9 10:51:53 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.8.18 state: TCP in wire: 172.16.8.18:3187 192.168.1.222:80 stack: - [lo=426896320 high=426896321 win=10607 modulator=0] [lo=0 high=10607 win=1 modulator=0] 2:0 seq=426896319 Nov 9 10:51:55 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.4.7 state: TCP in wire: 172.16.4.7:2535 192.168.1.222:80 stack: - [lo=2818466822 high=2818466823 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=2818466821 Nov 9 10:51:57 risen /bsd: pf_map_addr: selected address 115.109.4.234 Nov 9 10:51:57 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.8.20 state: TCP in wire: 172.16.8.20:4161 192.168.1.222:80 stack: - [lo=4165940943 high=4165940945 win=65535 modulator=0] [lo=0 high=1 win=1 modulator=0] 2:0 seq=4165940943 Nov 9 10:52:00 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.8.20 state: TCP in wire: 172.16.8.20:4161 192.168.1.222:80 stack: - [lo=4165940944 high=4165940945 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=4165940943 Nov 9 10:52:01 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.4.7 state: TCP in wire: 172.16.4.7:2535 192.168.1.222:80 stack: - [lo=2818466822 high=2818466823 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=2818466821 Nov 9 10:52:02 risen /bsd: pf_map_addr: selected address 115.109.4.234 Nov 9 10:52:06 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.8.20 state: TCP in wire: 172.16.8.20:4161 192.168.1.222:80 stack: - [lo=4165940944 high=4165940945 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=4165940943 Nov 9 10:52:11 risen /bsd: pf_map_addr: selected address 115.109.4.234 Nov 9 10:52:23 risen last message repeated 7 times Nov 9 10:52:23 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.8.18 state: TCP in wire: 172.16.8.18:3189 192.168.1.222:80 stack: - [lo=1624697237 high=1624697239 win=10607 modulator=0] [lo=0 high=1 win=1 modulator=0] 2:0 seq=1624697237 Nov 9 10:52:28 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.4.7 state: TCP in wire: 172.16.4.7:2537 192.168.1.222:80 stack: - [lo=2087468405 high=2087468407 win=65535 modulator=0] [lo=0 high=1 win=1 modulator=0] 2:0 seq=2087468405 Nov 9 10:52:29 risen /bsd: pf_map_addr: selected address 115.109.4.234 Nov 9 10:52:29 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.8.18 state: TCP in wire: 172.16.8.18:3189 192.168.1.222:80 stack: - [lo=1624697238 high=1624697239 win=10607 modulator=0] [lo=0 high=10607 win=1 modulator=0] 2:0 seq=1624697237 Nov 9 10:52:31 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.4.7 state: TCP in wire: 172.16.4.7:2537 192.168.1.222:80 stack: - [lo=2087468406 high=2087468407 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=2087468405 Nov 9 10:52:37 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.4.7 state: TCP in wire: 172.16.4.7:2537 192.168.1.222:80 stack: - [lo=2087468406 high=2087468407 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=2087468405 Nov 9 10:52:39 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.8.20 state: TCP in wire: 172.16.8.20:4169 192.168.1.222:80 stack: - [lo=3502269195 high=3502269197 win=65535 modulator=0] [lo=0 high=1 win=1 modulator=0] 2:0 seq=3502269195 Nov 9 10:52:42 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.8.20 state: TCP in wire: 172.16.8.20:4169 192.168.1.222:80 stack: - [lo=3502269196 high=3502269197 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=3502269195 Nov 9 10:52:48 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.8.20 state: TCP in wire: 172.16.8.20:4169 192.168.1.222:80 stack: - [lo=3502269196 high=3502269197 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=3502269195 Nov 9 10:53:01 risen /bsd: pf_map_addr: selected address 115.109.4.234 Nov 9 10:53:01 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.8.18 state: TCP in wire: 172.16.8.18:3207 192.168.1.222:80 stack: - [lo=3246448877 high=3246448879 win=10607 modulator=0] [lo=0 high=1 win=1 modulator=0] 2:0 seq=3246448877 Nov 9 10:53:02 risen /bsd: pf_map_addr: selected address 115.109.4.234 Nov 9 10:53:05 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.4.7 state: TCP in wire: 172.16.4.7:2539 192.168.1.222:80 stack: - [lo=492125580 high=492125582 win=65535 modulator=0] [lo=0 high=1 win=1 modulator=0] 2:0 seq=492125580 Nov 9 10:53:07 risen /bsd: pf_map_addr: selected address 115.109.4.234 Nov 9 10:53:07 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.8.18 state: TCP in wire: 172.16.8.18:3207 192.168.1.222:80 stack: - [lo=3246448878 high=3246448879 win=10607 modulator=0] [lo=0 high=10607 win=1 modulator=0] 2:0 seq=3246448877 Nov 9 10:53:08 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.4.7 state: TCP in wire: 172.16.4.7:2539 192.168.1.222:80 stack: - [lo=492125581 high=492125582 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=492125580 Nov 9 10:53:09 risen /bsd: pf_map_addr: selected address 115.109.4.234 Nov 9 10:53:14 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.4.7 state: TCP in wire: 172.16.4.7:2539 192.168.1.222:80 stack: - [lo=492125581 high=492125582 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=492125580 Nov 9 10:53:16 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.8.20 state: TCP in wire: 172.16.8.20:4172 192.168.1.222:80 stack: - [lo=74002749 high=74002751 win=65535 modulator=0] [lo=0 high=1 win=1 modulator=0] 2:0 seq=74002749 Nov 9 10:53:18 risen /bsd: pf_map_addr: selected address 115.109.4.234 Nov 9 10:53:19 risen last message repeated 5 times Nov 9 10:53:19 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.8.20 state: TCP in wire: 172.16.8.20:4172 192.168.1.222:80 stack: - [lo=74002750 high=74002751 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=74002749 Nov 9 10:53:25 risen /bsd: pf: OK ICMP 3:1 172.17.1.0 -> 172.16.8.20 state: TCP in wire: 172.16.8.20:4172 192.168.1.222:80 stack: - [lo=74002750 high=74002751 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=74002749 Nov 9 10:53:32 risen /bsd: pf_map_addr: selected address 115.109.4.234 # --------------------------------------------------------------- on firewall2 ---------------------------- Nov 9 13:53:23 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:23 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:23 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.8.25 state: TCP in wire: 172.16.8.25:2633 192.168.1.222:80 stack: - [lo=1728201122 high=1728201123 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=1728201121 Nov 9 13:53:23 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:25 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:25 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.4.6 state: TCP in wire: 172.16.4.6:1660 192.168.1.222:80 stack: - [lo=3910778615 high=3910778616 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=3910778614 Nov 9 13:53:26 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:28 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:28 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.4.20 state: TCP in wire: 172.16.4.20:2343 192.168.1.222:80 stack: - [lo=2609925938 high=2609925939 win=13068 modulator=0] [lo=0 high=13068 win=1 modulator=0] 2:0 seq=2609925937 Nov 9 13:53:28 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:29 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:29 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.8.18 state: TCP in wire: 172.16.8.18:3232 192.168.1.222:80 stack: - [lo=1450008918 high=1450008920 win=10607 modulator=0] [lo=0 high=1 win=1 modulator=0] 2:0 seq=1450008918 Nov 9 13:53:29 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:29 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.8.25 state: TCP in wire: 172.16.8.25:2633 192.168.1.222:80 stack: - [lo=1728201122 high=1728201123 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=1728201121 Nov 9 13:53:30 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:31 fw2 last message repeated 2 times Nov 9 13:53:32 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.5.5 state: TCP in wire: 172.16.5.5:1964 192.168.1.222:80 stack: - [lo=4134140406 high=4134140408 win=65535 modulator=0] [lo=0 high=1 win=1 modulator=0] 2:0 seq=4134140406 Nov 9 13:53:34 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:35 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.5.5 state: TCP in wire: 172.16.5.5:1964 192.168.1.222:80 stack: - [lo=4134140407 high=4134140408 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=4134140406 Nov 9 13:53:35 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:37 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:39 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.50.44 state: TCP in wire: 172.16.50.44:4608 192.168.1.222:80 stack: - [lo=2896257253 high=2896257255 win=65535 modulator=0] [lo=0 high=1 win=1 modulator=0] 2:0 seq=2896257253 Nov 9 13:53:40 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:41 fw2 last message repeated 2 times Nov 9 13:53:41 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.5.5 state: TCP in wire: 172.16.5.5:1964 192.168.1.222:80 stack: - [lo=4134140407 high=4134140408 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=4134140406 Nov 9 13:53:42 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.50.44 state: TCP in wire: 172.16.50.44:4608 192.168.1.222:80 stack: - [lo=2896257254 high=2896257255 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=2896257253 Nov 9 13:53:43 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:43 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.50.54 state: TCP in wire: 172.16.50.54:1412 192.168.1.222:80 stack: - [lo=3982885460 high=3982885462 win=65535 modulator=0] [lo=0 high=1 win=1 modulator=0] 2:0 seq=3982885460 Nov 9 13:53:43 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:46 fw2 last message repeated 4 times Nov 9 13:53:46 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.50.54 state: TCP in wire: 172.16.50.54:1412 192.168.1.222:80 stack: - [lo=3982885461 high=3982885462 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=3982885460 Nov 9 13:53:47 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:47 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:48 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.50.44 state: TCP in wire: 172.16.50.44:4608 192.168.1.222:80 stack: - [lo=2896257254 high=2896257255 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=2896257253 Nov 9 13:53:51 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:52 fw2 last message repeated 2 times Nov 9 13:53:52 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.50.54 state: TCP in wire: 172.16.50.54:1412 192.168.1.222:80 stack: - [lo=3982885461 high=3982885462 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=3982885460 Nov 9 13:53:52 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.4.6 state: TCP in wire: 172.16.4.6:1668 192.168.1.222:80 stack: - [lo=1434002914 high=1434002916 win=65535 modulator=0] [lo=0 high=1 win=1 modulator=0] 2:0 seq=1434002914 Nov 9 13:53:54 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:55 fw2 last message repeated 2 times Nov 9 13:53:55 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.4.6 state: TCP in wire: 172.16.4.6:1668 192.168.1.222:80 stack: - [lo=1434002915 high=1434002916 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=1434002914 Nov 9 13:53:55 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:56 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:56 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.4.20 state: TCP in wire: 172.16.4.20:2354 192.168.1.222:80 stack: - [lo=1882095811 high=1882095813 win=13068 modulator=0] [lo=0 high=1 win=1 modulator=0] 2:0 seq=1882095811 Nov 9 13:53:56 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:58 fw2 last message repeated 2 times Nov 9 13:53:58 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.8.25 state: TCP in wire: 172.16.8.25:2644 192.168.1.222:80 stack: - [lo=3523721122 high=3523721124 win=65535 modulator=0] [lo=0 high=1 win=1 modulator=0] 2:0 seq=3523721122 Nov 9 13:53:58 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:53:59 fw2 last message repeated 2 times Nov 9 13:53:59 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.4.20 state: TCP in wire: 172.16.4.20:2354 192.168.1.222:80 stack: - [lo=1882095812 high=1882095813 win=13068 modulator=0] [lo=0 high=13068 win=1 modulator=0] 2:0 seq=1882095811 Nov 9 13:54:00 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:54:01 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.4.6 state: TCP in wire: 172.16.4.6:1668 192.168.1.222:80 stack: - [lo=1434002915 high=1434002916 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=1434002914 Nov 9 13:54:01 fw2 /bsd: pf_map_addr: selected address 122.166.40.36 Nov 9 13:54:01 fw2 /bsd: pf: OK ICMP 3:1 172.17.1.1 -> 172.16.8.25 state: TCP in wire: 172.16.8.25:2644 192.168.1.222:80 stack: - [lo=3523721123 high=3523721124 win=65535 modulator=0] [lo=0 high=65535 win=1 modulator=0] 2:0 seq=3523721122 ---------------------------------------------- Thanks --Siju |
|
|
Re: Many messages from pf to the console in blue background and white font.Siju George <sgeorge.ml@...> writes:
> I started getting these messages on the console for twol of my firewalls. > What is actually wrong? This looks very much like you have "set debug loud" or "pfctl -x loud". Unless you're actually debugging a condition where having that level of information available is useful, well, it does generate a lot of messages. - Peter -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. |
|
|
Re: Many messages from pf to the console in blue background and white font.On Mon, Nov 9, 2009 at 11:13 AM, Peter N. M. Hansteen <peter@...>
wrote: > Siju George <sgeorge.ml@...> writes: > >> I started getting these messages on the console for twol of my firewalls. >> What is actually wrong? > > This looks very much like you have "set debug loud" or "pfctl -x > loud". Unless you're actually debugging a condition where having that > level of information available is useful, well, it does generate a lot > of messages. > I have set debug misc in my pf.conf --Siju |
|
|
Re: Many messages from pf to the console in blue background and white font.* Siju George <sgeorge.ml@...> [2009-11-09 09:26]:
> On Mon, Nov 9, 2009 at 11:13 AM, Peter N. M. Hansteen <peter@...> > wrote: > > Siju George <sgeorge.ml@...> writes: > > > >> I started getting these messages on the console for twol of my firewalls. > >> What is actually wrong? > > > > This looks very much like you have "set debug loud" or "pfctl -x > > loud". Unless you're actually debugging a condition where having that > > level of information available is useful, well, it does generate a lot > > of messages. > > > > I have > > set debug misc > > in my pf.conf that's the same as loud you want "urgent" at most. -- Henning Brauer, hb@..., henning@... BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting |
|
|
Re: Many messages from pf to the console in blue background and white font.On 2009-11-09, Henning Brauer <lists-openbsd@...> wrote:
> * Siju George <sgeorge.ml@...> [2009-11-09 09:26]: >> On Mon, Nov 9, 2009 at 11:13 AM, Peter N. M. Hansteen <peter@...> >> wrote: >> > Siju George <sgeorge.ml@...> writes: >> > >> >> I started getting these messages on the console for twol of my firewalls. >> >> What is actually wrong? >> > >> > This looks very much like you have "set debug loud" or "pfctl -x >> > loud". Unless you're actually debugging a condition where having that >> > level of information available is useful, well, it does generate a lot >> > of messages. >> > >> >> I have >> >> set debug misc >> >> in my pf.conf > > that's the same as loud > > you want "urgent" at most. > *especially* if you have a serial console. I'll go as far as saying, if you turn it on for debugging, set an at-job to make sure it gets turned back off. |
| Free embeddable forum powered by Nabble | Forum Help |