Hallo.
kann mal wer auf nephron7 draufschauen. ist online, aber vom haus kommt keiner per kabel drauf. neustart bringt nichts. kann man irgendwie sehen, obs am router liegt, oder ob beim switch etwas nicht stimmt???
Hat das so alles seine richtigkeit???
Aug 4 18:37:39 (none) kern.info rrdcollect[3417]: We just started
Aug 4 18:37:39 (none) kern.info rrdcollect[3417]: Update method: rrdlib
Aug 4 18:37:58 (none) kern.notice xrelayd[3542]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:37:59 (none) kern.notice xrelayd[3542]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:38:01 (none) kern.notice xrelayd[3593]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:38:04 (none) kern.notice xrelayd[3721]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:38:04 (none) kern.notice xrelayd[3593]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:38:04 (none) kern.notice xrelayd[3721]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:38:04 (none) kern.notice xrelayd[3722]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:38:05 (none) kern.notice xrelayd[3728]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:38:05 (none) kern.notice xrelayd[3728]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:38:05 (none) kern.notice xrelayd[3722]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:38:05 (none) kern.notice xrelayd[3730]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:38:05 (none) kern.notice xrelayd[3730]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:38:06 (none) kern.notice xrelayd[3745]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:38:06 (none) kern.notice xrelayd[3752]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:38:08 (none) kern.notice xrelayd[3752]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:38:08 (none) kern.notice xrelayd[3745]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:38:12 (none) kern.notice xrelayd[3891]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:38:12 (none) kern.notice xrelayd[3891]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:38:22 (none) kern.notice xrelayd[3923]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:38:27 (none) kern.notice xrelayd[3923]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:38:29 (none) kern.notice xrelayd[4168]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:38:31 (none) kern.notice xrelayd[4168]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:39:11 (none) kern.notice xrelayd[4561]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:39:15 (none) kern.notice xrelayd[4561]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:39:16 (none) kern.notice xrelayd[4771]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:39:18 (none) kern.notice xrelayd[4771]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:39:24 (none) kern.notice xrelayd[4987]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:39:31 (none) kern.notice xrelayd[4987]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:39:31 (none) kern.notice xrelayd[5315]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:39:31 (none) kern.notice xrelayd[5315]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:39:32 (none) kern.notice xrelayd[5322]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:39:32 (none) kern.notice xrelayd[5322]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:39:34 (none) kern.notice xrelayd[5330]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:39:36 (none) kern.notice xrelayd[5330]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:40:32 (none) kern.notice xrelayd[5863]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:40:41 (none) kern.notice xrelayd[5863]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:40:42 (none) kern.notice xrelayd[6280]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:40:42 (none) kern.notice xrelayd[6282]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:40:42 (none) kern.notice xrelayd[6280]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:40:42 (none) kern.notice xrelayd[6282]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:40:43 (none) kern.notice xrelayd[6287]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:40:43 (none) kern.notice xrelayd[6287]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:40:44 (none) kern.notice xrelayd[6292]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:40:46 (none) kern.notice xrelayd[6292]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:41:14 (none) kern.notice xrelayd[6760]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:41:19 (none) kern.notice xrelayd[6760]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:41:20 (none) kern.notice xrelayd[7002]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:41:22 (none) kern.notice xrelayd[7002]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:41:41 (none) kern.notice xrelayd[7302]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:41:43 (none) kern.notice xrelayd[7302]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:41:44 (none) kern.notice xrelayd[7442]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:41:45 (none) kern.notice xrelayd[7442]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:41:45 (none) kern.notice xrelayd[7447]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:41:45 (none) kern.notice xrelayd[7449]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:41:45 (none) kern.notice xrelayd[7447]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:41:46 (none) kern.notice xrelayd[7449]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:41:49 (none) kern.notice xrelayd[7589]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:41:52 (none) kern.notice xrelayd[7589]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:41:57 (none) kern.notice xrelayd[7747]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:41:58 (none) kern.notice xrelayd[7747]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:42:02 (none) kern.notice xrelayd[7943]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:42:04 (none) kern.notice xrelayd[7943]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:42:04 (none) kern.notice xrelayd[8030]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:42:07 (none) kern.notice xrelayd[8030]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:42:11 (none) kern.notice xrelayd[8233]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:42:12 (none) kern.notice xrelayd[8233]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:42:30 (none) kern.notice xrelayd[8411]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:42:32 (none) kern.notice xrelayd[8411]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:42:33 (none) kern.notice xrelayd[8563]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:42:34 (none) kern.notice xrelayd[8563]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:42:35 (none) kern.notice xrelayd[8627]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:42:41 (none) kern.notice xrelayd[8627]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:42:42 (none) kern.notice xrelayd[8957]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:42:44 (none) kern.notice xrelayd[8957]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:46:54 (none) kern.notice xrelayd[10523]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:46:56 (none) kern.notice xrelayd[10523]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:46:57 (none) kern.notice xrelayd[10660]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:46:58 (none) kern.notice xrelayd[10660]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:47:03 (none) kern.notice xrelayd[10865]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:47:05 (none) kern.notice xrelayd[10865]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:47:07 (none) kern.notice xrelayd[10961]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:47:08 (none) kern.notice xrelayd[10961]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:47:30 (none) kern.notice xrelayd[11111]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:47:33 (none) kern.notice xrelayd[11111]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:47:36 (none) kern.err xrelayd[11280]: xrelayd.c:436 SSL handshake failed: fffff080
Aug 4 18:47:36 (none) kern.notice xrelayd[11282]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:47:45 (none) kern.notice xrelayd[11282]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:47:47 (none) kern.notice xrelayd[11733]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:47:47 (none) kern.notice xrelayd[11733]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:48:15 (none) kern.notice xrelayd[12297]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:48:18 (none) kern.notice xrelayd[12297]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:48:21 (none) kern.err xrelayd[12455]: xrelayd.c:436 SSL handshake failed: fffff080
Aug 4 18:48:21 (none) kern.notice xrelayd[12458]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:48:25 (none) kern.notice xrelayd[12458]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:48:26 (none) kern.notice xrelayd[12667]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
Aug 4 18:48:28 (none) kern.notice xrelayd[12667]: xrelayd.c:535 Closed connection between ssl client 104.62.2.49 and plain server localhost:80
Aug 4 18:48:35 (none) kern.notice xrelayd[12886]: xrelayd.c:445 Connected ssl client 104.62.2.49 to plain server localhost:80
nephron7
Re: nephron7
also das log sieht erst mal normal aus. einige male erfolgreich ne ssl-verbindung hergestellt. mich wundern nur die beiden errs, dass das handshake fehlgeschlagen sei, aber dann gleich danach die verbindung doch hergestellt werden konnte, das kann aber auch an nem timeout bei ner funkverbindung liegen oder so. ich probier nachher mal draufzukommen.
みんなはばかだ。
Mein öffentlicher Schlüssel (OpenPGP)
Mein öffentlicher Schlüssel (SSH2, kommerzielles Format)
Verwalter von 7.42, 7.43, 7.44, 9.42, 10.42, 10.43, 15.42 und 28.1.
Anschluss: T-Com Call & Surf Comfort Plus inkl. HotSpot-Flat 16/1 Mbit
Modem, Router, TK-Anlage: Speedport W 700V
FF-Router: Buffalo WHR-HP-G54, FFF-Leipzig 1.6.10-core-1-halle-3, Doppel-Biquad-Antenne
Mein öffentlicher Schlüssel (OpenPGP)
Mein öffentlicher Schlüssel (SSH2, kommerzielles Format)
Verwalter von 7.42, 7.43, 7.44, 9.42, 10.42, 10.43, 15.42 und 28.1.
Anschluss: T-Com Call & Surf Comfort Plus inkl. HotSpot-Flat 16/1 Mbit
Modem, Router, TK-Anlage: Speedport W 700V
FF-Router: Buffalo WHR-HP-G54, FFF-Leipzig 1.6.10-core-1-halle-3, Doppel-Biquad-Antenne
Re: nephron7
per freifunk kommt man auf jeden fall drauf!!! Eben nur nicht per wlanstick oder kabel....
ABer ich kann da so nichts sehen... Naja, kenn mich aber auch net so aus...
ABer ich kann da so nichts sehen... Naja, kenn mich aber auch net so aus...
Re: nephron7
mh achso. du warst vor ort, weil du sagst, kabel geht nich? bei wlansticks kann es natürlich sein, dass er laptop-benutzer abgeschaltet hat. aber kabel sollte auf jeden fall auf mindestens einem port gehen, denn sonst ist entweder etwas kaputt oder das eine äußerst merkwürdige konfiguration.
みんなはばかだ。
Mein öffentlicher Schlüssel (OpenPGP)
Mein öffentlicher Schlüssel (SSH2, kommerzielles Format)
Verwalter von 7.42, 7.43, 7.44, 9.42, 10.42, 10.43, 15.42 und 28.1.
Anschluss: T-Com Call & Surf Comfort Plus inkl. HotSpot-Flat 16/1 Mbit
Modem, Router, TK-Anlage: Speedport W 700V
FF-Router: Buffalo WHR-HP-G54, FFF-Leipzig 1.6.10-core-1-halle-3, Doppel-Biquad-Antenne
Mein öffentlicher Schlüssel (OpenPGP)
Mein öffentlicher Schlüssel (SSH2, kommerzielles Format)
Verwalter von 7.42, 7.43, 7.44, 9.42, 10.42, 10.43, 15.42 und 28.1.
Anschluss: T-Com Call & Surf Comfort Plus inkl. HotSpot-Flat 16/1 Mbit
Modem, Router, TK-Anlage: Speedport W 700V
FF-Router: Buffalo WHR-HP-G54, FFF-Leipzig 1.6.10-core-1-halle-3, Doppel-Biquad-Antenne
Re: nephron7
naja, ne. hab aber mit ein paar leuten aus dem haus gesprochen... und die kommen per kabel nicht drauf...Aber ich schau vielleicht nachher mal rüber... eventuell ist auch nur das kabel rausgezogen... und von zu hause kann man ja sehen, dass da kein dhcp nutzer angezeigt wird...
dachte nur man kann sowas auch irgendwo im logfile sehen, oder über putty...
dachte nur man kann sowas auch irgendwo im logfile sehen, oder über putty...
Re: nephron7
hab mal grad draufgeguckt.
robocfg sagt, dass alle 5 ports (4 lan-ports und 1 wan-port) DOWN sind. d.h. das lämpchen dürfte bei allen ports nicht blinken. somit höchstwahrscheinlich das kabel am router oder bei der gegenstelle raus oder gerissen.
robocfg sagt, dass alle 5 ports (4 lan-ports und 1 wan-port) DOWN sind. d.h. das lämpchen dürfte bei allen ports nicht blinken. somit höchstwahrscheinlich das kabel am router oder bei der gegenstelle raus oder gerissen.
Re: nephron7
danke. lag weiter unten das Problem. Kabel getauscht. jetzt gehts wieder...