Fikk klage fra ISP, mener router sender DHCP forespørsel for ofte:

[nree]

Hei,

 

I dag fikk både jeg og min kollega en e-post fra vår ISP som mener routerene våre sender DHCP forespørsel for ofte.

Begge vi har ClearOS installert på en pc med to (eller tre) nettverkskort.

 

Når jeg sjekket loggen stemmer det ganske godt med det ISP sier, routeren tar en slags mini omstart hvert 3-10 min:

Feb 16 21:22:03 system cc-firewall: Starting firewall...

Feb 16 21:22:03 system cc-firewall: Loading environment

Feb 16 21:22:03 system cc-firewall: WARNING: l7-filter is not running' date=' disabling protocol filtering.

Feb 16 21:22:03 system cc-firewall: Assuming device is a LAN interface: eth2

Feb 16 21:22:03 system cc-firewall: Detected LAN role for interface: eth1

Feb 16 21:22:03 system cc-firewall: Detected LAN role for interface: eth2

Feb 16 21:22:03 system cc-firewall: WARNING: No configured WAN interfaces, continuing anyway...

Feb 16 21:22:03 system cc-firewall: if_get_address: SIOCGIFADDR: Cannot assign requested address

Feb 16 21:22:03 system cc-firewall: Warning: Failed to detect IP address for LAN device: eth2

Feb 16 21:22:03 system cc-firewall: Detected LAN info - eth1 192.168.0.1 on network 192.168.0.0/24

Feb 16 21:22:03 system cc-firewall: Setting kernel parameters

Feb 16 21:22:03 system cc-firewall: Using gateway mode

Feb 16 21:22:03 system cc-firewall: Loading kernel modules

Feb 16 21:22:03 system cc-firewall: Loading kernel modules for NAT

Feb 16 21:22:03 system cc-firewall: Setting default policy to DROP

Feb 16 21:22:03 system cc-firewall: Defining custom chains

Feb 16 21:22:03 system cc-firewall: Running blocked external rules

Feb 16 21:22:03 system cc-firewall: Running custom rules

Feb 16 21:22:03 system cc-firewall: Running common rules

Feb 16 21:22:03 system cc-firewall: Running incoming denied rules

Feb 16 21:22:03 system cc-firewall: Running user-defined incoming rules

Feb 16 21:22:03 system cc-firewall: Allowing incoming tcp port/range 81

Feb 16 21:22:03 system cc-firewall: Allowing incoming tcp port/range 1875

Feb 16 21:22:03 system cc-firewall: Running default incoming allowed rules

Feb 16 21:22:03 system cc-firewall: Running user-defined port forward rules

Feb 16 21:22:03 system cc-firewall: Port forwarding tcp ** to 192.168.0.*** **

Feb 16 21:22:03 system cc-firewall: Port forwarding tcp *******************

Feb 16 21:22:03 system cc-firewall: Port forwarding udp *******************

Feb 16 21:22:03 system cc-firewall: Port forwarding tcp *******************

Feb 16 21:22:03 system cc-firewall: Skipping 1-to-1 NAT rules - no active WAN interfaces

Feb 16 21:22:03 system cc-firewall: Running user-defined proxy rules

Feb 16 21:22:04 system cc-firewall: Enabling standby NAT on WAN/LAN interface eth0/eth1

Feb 16 21:22:04 system cc-firewall: Running user-defined outgoing block rules

Feb 16 21:22:04 system cc-firewall: Running default forwarding rules

Feb 16 21:22:04 system cc-firewall: Execution time: 0.367s

Feb 16 21:22:04 system firewall: ========== start /etc/rc.d/rc.firewall.local ==========

Feb 16 21:22:04 system firewall: # Custom firewall rules.

Feb 16 21:22:04 system firewall: # This file is executed by the firewall on stop/start/restart.

Feb 16 21:22:04 system firewall: ========== start /etc/rc.d/rc.firewall.local ==========[/quote'](Sensur på port forward)

 

Jeg lurer på hva dette kan komme av?

Noen som har tips eller forslag til hva jeg kan forsøke/prøve/sjekke?

[nree]

Oppdatering:

syswatch sier dette:

 

Wed Feb 16 21:34:55 2011 info: eth0 - ping check on server #1 failed - 84.234.***.1

Wed Feb 16 21:35:00 2011 info: eth0 - ping check on server #2 failed - 69.90.141.72

Wed Feb 16 21:35:00 2011 warn: eth0 - connection warning

Wed Feb 16 21:35:12 2011 info: eth0 - ping check on server #1 failed - 84.234.***.1

Wed Feb 16 21:35:17 2011 info: eth0 - ping check on server #2 failed - 69.90.141.72

Wed Feb 16 21:35:17 2011 warn: eth0 - connection warning

Wed Feb 16 21:35:29 2011 info: eth0 - ping check on server #1 failed - 84.234.***.1

Wed Feb 16 21:35:34 2011 info: eth0 - ping check on server #2 failed - 69.90.141.72

Wed Feb 16 21:35:34 2011 warn: eth0 - connection warning

Wed Feb 16 21:35:46 2011 info: eth0 - ping check on server #1 failed - 84.234.***.1

Wed Feb 16 21:35:51 2011 info: eth0 - ping check on server #2 failed - 69.90.141.72

Wed Feb 16 21:35:51 2011 warn: eth0 - connection warning

Wed Feb 16 21:36:03 2011 info: eth0 - ping check on server #1 failed - 84.234.***.1

Wed Feb 16 21:36:08 2011 info: eth0 - ping check on server #2 failed - 69.90.141.72

Wed Feb 16 21:36:08 2011 warn: eth0 - connection is down

Wed Feb 16 21:36:10 2011 info: eth0 - restarting DHCP connection

Wed Feb 16 21:36:13 2011 info: system - changing active WAN list - none (was eth0)

Wed Feb 16 21:36:13 2011 info: system - current WANs in use - none

Wed Feb 16 21:36:13 2011 info: system - restarting firewall

Wed Feb 16 21:36:14 2011 info: system - updating intrusion prevention whitelist

Wed Feb 16 21:36:14 2011 info: system - adding ping server 69.90.141.72

Wed Feb 16 21:36:14 2011 info: system - adding ping server 84.234.***.1

Wed Feb 16 21:36:14 2011 info: system - adding DNS server 81.167.36.3

Wed Feb 16 21:36:14 2011 info: system - adding DNS server 81.167.36.11

Wed Feb 16 21:36:14 2011 info: system - resetting intrusion detection

 

Så det ser altså ut som routeren resetter brannmuren pga. nærmeste router til ISP ikke svarer på ping, og det samme gjør ikke en IP som ClearOS har lagt inn?

Så var det hvordan jeg endret/legger til ip-addresser for ping test her.

Endret 16. februar 2011 av Goggen90