[Fli4l_dev] Disconnect-Einträge im WAN-IP-Protokoll

[Mark Gerber]

Hallo Peter!

> Intressant wäre nun mal da syslog, ob dort entsprechende ip-up und  
> ip-down
> ereignisse verzeichnet sind, und wer oder was die Auslöst.

Mitlerweile ist es so, dass ip-down vor ip-up aufgerufen wird, warum auch  
immer.

Ich habe soeben mal das aktuelle r32443-testing eingespielt. In meinen  
Augen sind die entsprechenden Zeilen im Syslog (mit ein paar zusätzlichen  
Zeilen drumrum) nicht sehr aussagekräftig:

--- Syslog-Auszug - Anfang ---
Aug 26 13:46:47 rout-01 daemon.info collectd[3712]: Initialization  
complete, entering read-loop.
Aug 26 13:46:48 rout-01 cron.info /usr/sbin/cron[3757]: (CRON) INFO  
(pidfile fd = 3)
Aug 26 13:46:48 rout-01 cron.info /usr/sbin/cron[3758]: (CRON) STARTUP  
(fork ok)
Aug 26 13:46:48 rout-01 cron.info /usr/sbin/cron[3758]: (CRON) INFO  
(Running @reboot jobs)
Aug 26 13:46:48 rout-01 cron.info /USR/SBIN/CRON[3762]: (root) CMD (sleep  
120; cd /data; tar -c -f - accounting backups_shutdown log rrdtool3 | gzip  
- > Backup_ROUT-01_data.tar.gz)
Aug 26 13:46:48 rout-01 local2.notice ip-down[754]:    executing ip-down  
scripts ...
Aug 26 13:46:48 rout-01 local2.notice ip-down[754]: /etc/ppp/ip-down:  
/etc/ppp/ip-up-down: line 61: can't open /var/run/online: no such file
Aug 26 13:46:48 rout-01 local2.notice ip-down[754]: executing  
/etc/ppp/ip-down500.chrony
Aug 26 13:46:48 rout-01 local2.notice ip-down[754]: executing  
/etc/ppp/ip-down700.logip
Aug 26 13:46:48 rout-01 local2.notice ip-down[754]: executing  
/etc/ppp/ip-down800.dhcp
Aug 26 13:46:48 rout-01 local2.notice ip-down[754]: executing  
/etc/ppp/ip-down800.dns
Aug 26 13:46:48 rout-01 local2.notice ip-down[754]: executing  
/etc/ppp/ip-down861.accounting
Aug 26 13:46:48 rout-01 local2.notice ip-down[754]: aktualisiere Index
Aug 26 13:46:48 rout-01 local2.notice ip-down[754]: aktualisiere Hostdaten
Aug 26 13:46:48 rout-01 local2.notice ip-down[754]: aktualisiere  
Interfacedaten
Aug 26 13:46:49 rout-01 local2.notice ip-down[754]: schreibe Daten
Aug 26 13:46:49 rout-01 local2.notice ip-down[754]: Fertig
Aug 26 13:46:49 rout-01 local2.notice ip-down[754]: executing  
/etc/ppp/ip-down900.dhcp-fwsetup
Aug 26 13:46:49 rout-01 local2.notice ip-down[754]: executing  
/etc/ppp/ip-down980.fwsetup
Aug 26 13:46:49 rout-01 local2.notice ip-down[754]: cleaning up dynamic  
IPv4 firewall rules ...
Aug 26 13:46:49 rout-01 local2.notice ip-down[754]:    finished ip-down  
scripts ...
Aug 26 13:46:49 rout-01 local2.notice ip-down[754]: terminating ...
Aug 26 13:46:50 rout-01 local2.notice ip-up[1462]:    executing ip-up  
scripts ...
Aug 26 13:46:50 rout-01 local2.notice ip-up[1462]: default route interface  
'eth1' comes up
Aug 26 13:46:50 rout-01 local2.notice ip-up[1462]: executing  
/etc/ppp/ip-up010.dhcp-fwsetup
Aug 26 13:46:50 rout-01 local2.notice ip-up[1462]: executing  
/etc/ppp/ip-up020.fwsetup
Aug 26 13:46:50 rout-01 local2.notice ip-up[1462]: setting up dynamic IPv4  
firewall rules ...
Aug 26 13:46:51 rout-01 local2.notice ip-up[1462]: executing  
/etc/ppp/ip-up050.conntrack
Aug 26 13:46:51 rout-01 local2.notice ip-up[1462]: conntrack v1.4.2  
(conntrack-tools): 101 flow entries have been deleted.
Aug 26 13:46:51 rout-01 local2.notice ip-up[1462]: executing  
/etc/ppp/ip-up200.dhcp
Aug 26 13:46:51 rout-01 local2.notice ip-up[1462]: executing  
/etc/ppp/ip-up200.dns
Aug 26 13:46:51 rout-01 local2.notice ip-up[1462]: using nameserver  
213.209.104.220
Aug 26 13:46:51 rout-01 local2.notice ip-up[1462]: using nameserver  
213.209.104.250
Aug 26 13:46:51 rout-01 local2.notice ip-up[1462]: cp: can't stat  
'/etc/dnsmasq.d/dns_delegation.conf': No such file or directory
Aug 26 13:46:51 rout-01 local0.info dnsmasq[2134]: read /etc/hosts - 3  
addresses
--- Syslog-Auszug - Ende ---

Hilft das weiter?

Gruß
Mark

P.S.: Zur Info: Kernel 3.16 (genau: 3.16.1-nonfree) läuft hier auf meiner  
alten AMD-K6-III-Möhre. :)