| Freesco, NND, CDN, EOS http://forum.freesco.pl/ |
|
| Wywala mi NET http://forum.freesco.pl/viewtopic.php?f=35&t=3965 |
Strona 1 z 1 |
| Autor: | Jaca21 [ sobota, 20 marca 2004, 21:41 ] |
| Tytuł: | Wywala mi NET |
Witam Mam DSL-a 512 od tygodnia na Freesco oczywiscie i przez ten tydzień wszystko było OK. Od 3 dni cos nie gra. 4 razy dziennie wywala mi net. Dopiero odłączenie i ponowne podłączenie do prądu modemu daje rezultaty ale potem sytuacja sie powtarza. Czy ktoś miał podobny przypadek. Proszę o pomoc. Pozdrawiam ____________ Jaca |
|
| Autor: | Kiler [ niedziela, 21 marca 2004, 01:05 ] |
| Tytuł: | |
Mialem tak przez 3 miesiace... Tylko ze jak wywalilo mi 4 razy dziennie to sie cieszylem ze tylko 4 razy dziennie... Bo srednio dochodzilo do 10. Byly to wowczas poczatki dzialalnosci DSL'a i wowczas TPSA za wszelka cene probowala mi wmowic ze to moja wina, ze to u mnie cos nie dziala... Dopiero wymiana modemu na nowy zakonczyla problemy... Ale kosztowalo mnie to 3 miesiace walki z TPSA 
|
|
| Autor: | Jaca21 [ niedziela, 21 marca 2004, 10:44 ] |
| Tytuł: | |
Witam Wielkie dzięki za zainteresowanie. Czekam jeszcze na inne opinie. Może coś w konfiguracji serwera dodać lub ująć. Pozdrawiam ____________ Jaca |
|
| Autor: | monter [ niedziela, 21 marca 2004, 11:12 ] |
| Tytuł: | |
Musisz popatrzec w logi bo jest mozliwosc ze koncza Ci sie porty komunikat :no free ports lub maskarada sie zapycha . rada na to jest dopisanie regulek , jedna masz w faq na stronie glownej frresco.pl http://www.freesco.pl/html/modules.php? ... retacja#98 a druga napisal ZCIECH :ipfwadm -I -i deny -P tcp -D 0/0 135 tu masz linka http://forum.freesco.pl/viewtopic.php?t=2947 mi pomoglo ale mozesz miec inny problem np sprzetowy bo tez mialem taka sytuacje . |
|
| Autor: | Kiler [ niedziela, 21 marca 2004, 13:26 ] |
| Tytuł: | |
Wszystko zalezy od tego czy to rzeczywiscie NET Ci wywala czy tez moze serwer zalicza zwieche... Jesli to drugie to wina bedzie lezala po Twojej stronie (czyt. cos z konfigiem FreeSCO). Aby sie upewnic najlepiej przy braku iNET'u zrob cosik w tym stylu: 1. Wypusc pinga do serwera i do bramy (adres zarezerwowany modemu) - jesli przyjda prawidlowe odpowiedzi tzn ze z serwerem i FreeSCO jest wszystko OK... Jesli wypuscisz pinga w swiat i przyjdzie odpowiedz w stylu: "Odpowiedz z 80.55....... (tu adres modemu): Host docelowy jest nieosiagalny" i tak przez 4 razy, a po zrestartowaniu modemu wszystko powroci do normy to bedzie to wadliwy modem... I proponuje zglaszac to technikom TPSA. 2. Wypusc pinga do serwera i jesli bedzie brak odpowiedzi i nie bedzie szlo sie np zdalnie polaczyc z serwerem to bedzie znaczyc ze to jednak serwer zaliczyl zwieche i proponuje "pomieszac" troche w konfigu... Opcja 1. - wina TPSA, opcja 2. - pogrzeb co nie co u siebie... |
|
| Autor: | Jaca21 [ niedziela, 21 marca 2004, 15:27 ] |
| Tytuł: | |
Witam wielkie dzieki za zainteresowanie tematem bo mnie ludzie zjedza niedługo za te braki neta. Mniej wiecej kumam o czym piszesz. Tylko mam pare pytanek. Oczywiscie mam rozumiec ze pingi puszczam z konsoli Freesco czyli z mojego serwerka. "Wypusc pinga do serwera i do bramy" adres modemu to wiem który to a adres serwera to adres zarezerwowany dla abonenta????? bo nie za bardzo kumam o jakim adresie mówisz. prosze o pilna odpowiedz Pozdrawiam ______________ Jaca21 |
|
| Autor: | Kiler [ niedziela, 21 marca 2004, 18:00 ] |
| Tytuł: | |
Jaca21 pisze: Oczywiscie mam rozumiec ze pingi puszczam z konsoli Freesco czyli z mojego serwerka. Pingi "puszczasz" ze swojego domowego komputera... Bo jesli serwer Ci sie zwiesil to ani zdalnie sie do niego nie podlaczysz (np. za posrednictwem telnetu lub ssh) ani "klepanie" w klawiature podlaczona do serwera nic Ci nie da bo nie bedzie sie nic pojawiac ani odpowiadac  Adres zarezerwowany modemu (adres modemu) to adres Twojej bramy, a adres zarezerwowany dla abonenta to IP, ktore jest przydzielane karcie eth0 (tej do ktorej jest podlaczony modem) w serwerze (adres serwera).
Przy braku iNET'u najlepiej "powypuszczaj" pingi do serwera (moze byc do IP wew i zew), bramy (adres modemu), w swiat (np. www.wp.pl) i zobacz co "odpowie" i jak "odpowie". W razie czego odezwij sie na gg albo podaj swoj gg w profilu 
|
|
| Autor: | Jaca21 [ niedziela, 21 marca 2004, 18:33 ] |
| Tytuł: | |
Witam To są ostatnie pwisy w logu od ostatniego restartu serwera. Moze ktoś powie co jest nie tak bo w tym czasie też rozłlaczył mi sie modem Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:26 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 16:20:11 - last message repeated 3 times Mar 21 16:21:12 - last message repeated 4 times Mar 21 16:21:42 - last message repeated 2 times Mar 21 16:21:48 - named[169]: No root nameservers for class IN Mar 21 16:21:58 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 16:22:43 - last message repeated 3 times Mar 21 16:23:44 - last message repeated 4 times Mar 21 16:24:45 - last message repeated 4 times Mar 21 16:26:01 - last message repeated 5 times Mar 21 16:27:17 - last message repeated 5 times Mar 21 16:28:32 - last message repeated 5 times Mar 21 16:29:33 - last message repeated 4 times Mar 21 16:30:34 - last message repeated 4 times Mar 21 16:31:35 - last message repeated 4 times Mar 21 16:32:36 - last message repeated 4 times Mar 21 16:33:51 - last message repeated 5 times Mar 21 16:34:52 - last message repeated 4 times Mar 21 16:35:53 - last message repeated 4 times Mar 21 16:36:54 - last message repeated 4 times Mar 21 16:37:55 - last message repeated 4 times Mar 21 16:39:10 - last message repeated 5 times Mar 21 16:40:11 - last message repeated 4 times Mar 21 16:41:12 - last message repeated 4 times Mar 21 16:42:13 - last message repeated 4 times Mar 21 16:43:14 - last message repeated 4 times Mar 21 16:44:30 - last message repeated 5 times Mar 21 16:45:45 - last message repeated 5 times Mar 21 16:46:46 - last message repeated 4 times Mar 21 16:47:17 - last message repeated 2 times Mar 21 16:47:31 - named[169]: sysquery: findns error (2) on dns.poczta.fm? Mar 21 16:47:32 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 16:48:17 - last message repeated 3 times Mar 21 16:49:18 - last message repeated 4 times Mar 21 16:50:19 - last message repeated 4 times Mar 21 16:50:34 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 16:50:42 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 16:50:42 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 16:50:49 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 16:51:20 - last message repeated 2 times Mar 21 16:52:36 - last message repeated 5 times Mar 21 16:53:52 - last message repeated 5 times Mar 21 16:55:08 - last message repeated 5 times Mar 21 16:56:23 - last message repeated 5 times Mar 21 16:57:24 - last message repeated 4 times Mar 21 16:58:25 - last message repeated 4 times Mar 21 16:59:26 - last message repeated 4 times Mar 21 17:00:27 - last message repeated 4 times Mar 21 17:01:43 - last message repeated 5 times Mar 21 17:02:59 - last message repeated 5 times Mar 21 17:04:15 - last message repeated 5 times Mar 21 17:05:31 - last message repeated 5 times Mar 21 17:06:46 - last message repeated 5 times Mar 21 17:07:47 - last message repeated 4 times Mar 21 17:08:48 - last message repeated 4 times Mar 21 17:09:49 - last message repeated 4 times Mar 21 17:10:50 - last message repeated 4 times Mar 21 17:11:35 - last message repeated 3 times Mar 21 17:11:39 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:11:39 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:11:50 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:11:56 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:11:56 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:12:05 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:12:21 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:12:30 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:12:30 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:12:36 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:12:47 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:12:47 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:12:49 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:12:49 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:12:51 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:12:58 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:12:58 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:13:04 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:13:04 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:13:06 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:13:17 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:13:17 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:13:21 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:13:52 - last message repeated 2 times Mar 21 17:14:37 - last message repeated 3 times Mar 21 17:14:52 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:14:52 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:14:53 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:15:08 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:15:09 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:15:09 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:15:23 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:15:23 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:15:23 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:15:38 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:15:38 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:15:38 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:15:53 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:15:53 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:15:53 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:16:09 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:16:10 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:16:10 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:16:24 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:16:25 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:16:25 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:16:39 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:17:24 - last message repeated 3 times Mar 21 17:18:25 - last message repeated 4 times Mar 21 17:18:56 - last message repeated 2 times Mar 21 17:19:09 - named[169]: NSTATS 1079889549 1079885949 A=206 PTR=1 Mar 21 17:19:09 - named[169]: XSTATS 1079889549 1079885949 RQ=207 RR=63 RIQ=0 RNXD=0 RFwdQ=90 RFwdR=62 RDupQ=101 RDupR=0 RFail=0 RFErr=0 RErr=0 RTCP=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=1 SAns=16 SFwdQ=90 SFwdR=62 SDupQ=28 SFail=28 SFErr=0 SErr=0 RNotNsQ=207 SNaAns=16 SNXD=0 Mar 21 17:19:11 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:19:56 - last message repeated 3 times Mar 21 17:20:57 - last message repeated 4 times Mar 21 17:21:58 - last message repeated 4 times Mar 21 17:22:44 - last message repeated 3 times Mar 21 17:22:47 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:22:47 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:22:59 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:23:06 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:23:06 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:23:14 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:23:15 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:23:15 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:23:29 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:23:34 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:23:34 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:23:44 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:24:15 - last message repeated 2 times Mar 21 17:25:31 - last message repeated 5 times Mar 21 17:26:01 - last message repeated 2 times Mar 21 17:26:02 - named[169]: sysquery: no addrs found for NS (ns2.nix.paypal.com) Mar 21 17:26:02 - named[169]: sysquery: no addrs found for NS (ns2.sc5.paypal.com) Mar 21 17:26:02 - named[169]: sysquery: no addrs found for NS (ns1.nix.paypal.com) Mar 21 17:26:02 - named[169]: sysquery: no addrs found for NS (ns1.sc5.paypal.com) Mar 21 17:26:02 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:26:02 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Mar 21 17:26:16 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ Mar 21 17:26:47 - last message repeated 2 times Mar 21 17:26:48 - named[169]: sysquery: findns error (2) on l.gtld-servers.net? Mar 21 17:26:48 - named[169]: sysquery: findns error (2) on m.gtld-servers.net? Pozdrawiam Jaca |
|
| Autor: | Anonymous [ niedziela, 21 marca 2004, 20:06 ] |
| Tytuł: | |
Cytuj: Mar 21 16:19:11 - kernel: Traffic shaper initialised.
Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Mar 21 16:19:11 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 16:19:11 - kernel: Traffic shaper initialised. Jeśli masz justice od ver 42 do 44 wywal je są (sorry autorze) do kitu. U mnie tez sie wieszało jak je miałem. Instalnij sobie wersję 33. No chyba że nie masz tych wersji nowszych instalniętych  .
|
|
| Autor: | Jaca21 [ niedziela, 21 marca 2004, 20:24 ] |
| Tytuł: | |
Witam własnie mam wersje Justice 44. Myslałem ze to może od tego ale chyba ta wersja juz jest na tyle przetestowana, że powinna działać. Proszę o opinię autora skryptu. Powiedzcie mi tylko jaki adres musze wpisac w pzregladarce abym mógł przeglądać statystyki Justice ale w w wersji 33 Pozdrawiam jaca |
|
| Autor: | Jaca21 [ niedziela, 21 marca 2004, 22:26 ] |
| Tytuł: | |
Po interwencji Kilera pozbylem sie wpisu w logu "Mar 21 16:19:26 - /bin/mgetty: Can't init modem /dev/cua1 with ATZ ". Niestety to nie rozwiazało problemu. problem wolnych portów w maskaradzie chyba też odpada ponieważ nie ma wpisu o tym w logu. Zapodam nastepna dawke wpisów z uwzględnieniem miejsc w których rozłanczał sie net. Mar 21 18:12:26 - syslogd 1.3-3: restart (remote reception). Mar 21 18:12:28 - kernel: Kernel logging (proc) started. Mar 21 18:12:28 - kernel: Memory: sized by int13 088h Mar 21 18:12:28 - kernel: Console: 16 point font, 480 scans Mar 21 18:12:28 - kernel: Console: colour VGA+ 80x30, 1 virtual console (max 63) Mar 21 18:12:28 - kernel: pcibios_init : BIOS32 Service Directory structure at 0x000fad30 Mar 21 18:12:28 - kernel: pcibios_init : BIOS32 Service Directory entry at 0xfb1b0 Mar 21 18:12:28 - kernel: pcibios_init : PCI BIOS revision 2.10 entry at 0xfb1e0 Mar 21 18:12:28 - kernel: Probing PCI hardware. Mar 21 18:12:28 - kernel: Calibrating delay loop.. ok - 399.77 BogoMIPS Mar 21 18:12:28 - kernel: Memory: 30276k/32768k available (696k kernel code, 384k reserved, 724k data) Mar 21 18:12:28 - kernel: Swansea University Computer Society NET3.035 for Linux 2.0 Mar 21 18:12:28 - kernel: NET3: Unix domain sockets 0.13 for Linux NET3.035. Mar 21 18:12:28 - kernel: Swansea University Computer Society TCP/IP for NET3.034 Mar 21 18:12:28 - kernel: IP Protocols: IGMP, ICMP, UDP, TCP Mar 21 18:12:28 - kernel: Linux IP multicast router 0.07. Mar 21 18:12:28 - kernel: Checking 'hlt' instruction... disabled Mar 21 18:12:28 - kernel: Linux version 2.0.38 (root@localhost.localdomain) (gcc version 2.7.2.3) #4 Wed May 17 22:55:01 EDT 2000 Mar 21 18:12:28 - kernel: Starting kswapd v 1.4.2.2 Mar 21 18:12:28 - kernel: Serial driver version 4.13p1 with no serial options enabled Mar 21 18:12:28 - kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A Mar 21 18:12:28 - kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A Mar 21 18:12:28 - kernel: lp1 at 0x0378, (polling) Mar 21 18:12:28 - kernel: Real Time Clock Driver v1.09 Mar 21 18:12:28 - kernel: Ramdisk driver initialized : 16 ramdisks of 4096K size Mar 21 18:12:28 - kernel: loop: registered device at major 7 Mar 21 18:12:28 - kernel: hda: WDC AC1170F, 162MB w/64kB Cache, CHS=1010/6/55 Mar 21 18:12:28 - kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Mar 21 18:12:28 - kernel: Floppy drive(s): fd0 is 1.44M Mar 21 18:12:28 - kernel: FDC 0 is a post-1991 82077 Mar 21 18:12:28 - kernel: Ethernet Bridge 002 for NET3.035 (Linux 2.0) Mar 21 18:12:28 - kernel: PPP: version 2.3.10 (demand dialling) Mar 21 18:12:28 - kernel: TCP compression code copyright 1989 Regents of the University of California Mar 21 18:12:28 - kernel: PPP line discipline registered. Mar 21 18:12:28 - kernel: SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256). Mar 21 18:12:28 - kernel: CSLIP: code copyright 1989 Regents of the University of California. Mar 21 18:12:28 - kernel: Partition check: Mar 21 18:12:28 - kernel: hda: hda1 Mar 21 18:12:28 - kernel: RAMDISK: Compressed image found at block 0 Mar 21 18:12:28 - kernel: EXT2-fs warning: checktime reached, running e2fsck is recommended Mar 21 18:12:28 - kernel: VFS: Mounted root (ext2 filesystem). Mar 21 18:12:28 - kernel: UMSDOS Beta 0.6 (compatibility level 0.4, fast msdos) Mar 21 18:12:31 - syslogd 1.3-3: restart (remote reception). Mar 21 18:12:32 - kernel: Adding Swap: 65532k swap-space (priority -1) Mar 21 18:12:32 - kernel: ip_masq_icq: using TCP port range 60200-61000 Mar 21 18:12:32 - kernel: ip_masq_icq: loaded support on port 4000/UDP Mar 21 18:12:32 - insmod: Cannot open /mnt/router/drv/*.o Mar 21 18:12:32 - insmod: Cannot open /mnt/router/drv/*.o Mar 21 18:12:32 - insmod: Symbol 'io' not found Mar 21 18:12:32 - last message repeated 7 times Mar 21 18:12:32 - kernel: smc-ultra.c: Presently autoprobing (not recommended) for a single card. Mar 21 18:12:32 - kernel: smc-ultra.c: No SMC Ultra card found (i/o = 0x0). Mar 21 18:12:32 - insmod: Initialization of /tmp/net/smc-ultra.o.A0 failed Mar 21 18:12:32 - kernel: smc-ultra.c: Presently autoprobing (not recommended) for a single card. Mar 21 18:12:32 - kernel: smc-ultra.c: No SMC Ultra card found (i/o = 0x0). Mar 21 18:12:32 - insmod: Initialization of /tmp/net/smc-ultra.o.B0 failed Mar 21 18:12:32 - insmod: Symbol 'io' not found Mar 21 18:12:32 - insmod: Symbol 'io' not found Mar 21 18:12:32 - kernel: ne.c: No PCI cards found. Use "io=0xNNN" value(s) for ISA cards. Mar 21 18:12:32 - insmod: Initialization of /tmp/prm/ne.o.A0 failed Mar 21 18:12:32 - kernel: ne.c: No PCI cards found. Use "io=0xNNN" value(s) for ISA cards. Mar 21 18:12:32 - insmod: Initialization of /tmp/prm/ne.o.B0 failed Mar 21 18:12:32 - insmod: Cannot open /mnt/router/drv/*.o Mar 21 18:12:32 - insmod: Cannot open /mnt/router/drv/*.o Mar 21 18:12:32 - insmod: Symbol 'io' not found Mar 21 18:12:32 - last message repeated 7 times Mar 21 18:12:32 - kernel: smc-ultra.c: Presently autoprobing (not recommended) for a single card. Mar 21 18:12:32 - kernel: smc-ultra.c: No SMC Ultra card found (i/o = 0x0). Mar 21 18:12:32 - insmod: Initialization of /tmp/net/smc-ultra.o.A1 failed Mar 21 18:12:32 - kernel: smc-ultra.c: Presently autoprobing (not recommended) for a single card. Mar 21 18:12:32 - kernel: smc-ultra.c: No SMC Ultra card found (i/o = 0x0). Mar 21 18:12:32 - insmod: Initialization of /tmp/net/smc-ultra.o.B1 failed Mar 21 18:12:32 - insmod: Symbol 'io' not found Mar 21 18:12:32 - insmod: Symbol 'io' not found Mar 21 18:12:32 - kernel: ne.c: No PCI cards found. Use "io=0xNNN" value(s) for ISA cards. Mar 21 18:12:32 - insmod: Initialization of /tmp/prm/ne.o.A1 failed Mar 21 18:12:32 - kernel: ne.c: No PCI cards found. Use "io=0xNNN" value(s) for ISA cards. Mar 21 18:12:32 - insmod: Initialization of /tmp/prm/ne.o.B1 failed Mar 21 18:12:32 - insmod: Cannot open /mnt/router/drv/*.o Mar 21 18:12:32 - insmod: Cannot open /mnt/router/drv/*.o Mar 21 18:12:32 - insmod: Symbol 'io' not found Mar 21 18:12:32 - last message repeated 7 times Mar 21 18:12:32 - kernel: smc-ultra.c: Presently autoprobing (not recommended) for a single card. Mar 21 18:12:32 - kernel: smc-ultra.c: No SMC Ultra card found (i/o = 0x0). Mar 21 18:12:32 - insmod: Initialization of /tmp/net/smc-ultra.o.A2 failed Mar 21 18:12:32 - kernel: smc-ultra.c: Presently autoprobing (not recommended) for a single card. Mar 21 18:12:32 - kernel: smc-ultra.c: No SMC Ultra card found (i/o = 0x0). Mar 21 18:12:32 - insmod: Initialization of /tmp/net/smc-ultra.o.B2 failed Mar 21 18:12:32 - insmod: Symbol 'io' not found Mar 21 18:12:32 - insmod: Symbol 'io' not found Mar 21 18:12:32 - kernel: ne.c: No PCI cards found. Use "io=0xNNN" value(s) for ISA cards. Mar 21 18:12:32 - insmod: Initialization of /tmp/prm/ne.o.A2 failed Mar 21 18:12:32 - kernel: ne.c: No PCI cards found. Use "io=0xNNN" value(s) for ISA cards. Mar 21 18:12:32 - insmod: Initialization of /tmp/prm/ne.o.B2 failed Mar 21 18:12:32 - insmod: Cannot open /mnt/router/drv/*.o Mar 21 18:12:32 - insmod: Initialization of /tmp/net/3c509.o.C failed Mar 21 18:12:32 - kernel: 3c59x.c:v0.99H 11/17/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html Mar 21 18:12:32 - insmod: Initialization of /tmp/net/3c59x.o.C failed Mar 21 18:12:32 - kernel: ne2k-pci.c:v0.99L 2/7/98 D. Becker/P. Gortmaker http://cesdis.gsfc.nasa.gov/linux/drivers/ne2k-pci.html Mar 21 18:12:32 - insmod: Initialization of /tmp/net/ne2k-pci.o.C failed Mar 21 18:12:32 - kernel: rtl8139.c:v1.04 9/22/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/rtl8139.html Mar 21 18:12:32 - kernel: eth0: RealTek RTL8139 Fast Ethernet at 0xe800, IRQ 11, 00:00:1c:81:5a:6d. Mar 21 18:12:32 - kernel: eth1: RealTek RTL8139 Fast Ethernet at 0xec00, IRQ 5, 00:e0:4c:00:37:dd. Mar 21 18:12:33 - kernel: smc-ultra.c: Presently autoprobing (not recommended) for a single card. Mar 21 18:12:33 - kernel: smc-ultra.c: No SMC Ultra card found (i/o = 0x0). Mar 21 18:12:33 - insmod: Initialization of /tmp/net/smc-ultra.o.C failed Mar 21 18:12:33 - insmod: Initialization of /tmp/net/tulip.o.C failed Mar 21 18:12:33 - kernel: ne.c: No PCI cards found. Use "io=0xNNN" value(s) for ISA cards. Mar 21 18:12:33 - insmod: Initialization of /tmp/prm/ne.o.C failed Mar 21 18:12:34 - mode: User 'init' issued 'mode ethernet' Mar 21 18:12:34 - named[168]: starting. named 4.9.3-BETA26 Sun Nov 26 20:58:49 CST 1995 ^Iroot@fuzzy:/tmp/bind-4.9.3-BETA26/named Mar 21 18:12:34 - named[168]: cache zone "" loaded (serial 0) Mar 21 18:12:34 - named[168]: primary zone "domain" loaded (serial 1999317) Mar 21 18:12:34 - named[168]: primary zone "10.in-addr.arpa" loaded (serial 1999317) Mar 21 18:12:34 - named[168]: primary zone "16.172.in-addr.arpa" loaded (serial 1999317) Mar 21 18:12:34 - named[168]: primary zone "168.192.in-addr.arpa" loaded (serial 1999317) Mar 21 18:12:34 - named[168]: primary zone "0.0.127.in-addr.arpa" loaded (serial 1999317) Mar 21 18:12:34 - named[169]: Ready to answer queries. Mar 21 18:12:35 localhost thttpd[324]: thttpd/2.05 09nov99 starting on port 82 Mar 21 18:12:35 localhost thttpd[328]: thttpd/2.05 09nov99 starting on port 80 Mar 21 18:12:35 localhost thttpd[324]: started as root without requesting chroot(), warning only Mar 21 18:12:35 localhost thttpd[328]: started as root without requesting chroot(), warning only Mar 21 18:12:36 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 18:12:36 - kernel: Traffic shaper initialised. Mar 21 18:12:36 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 18:12:36 - kernel: Traffic shaper initialised. Mar 21 18:12:36 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 18:12:36 - kernel: Traffic shaper initialised. Mar 21 18:12:36 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 18:12:36 - kernel: Traffic shaper initialised. Mar 21 18:12:36 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 18:12:36 - kernel: Traffic shaper initialised. Mar 21 18:12:36 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 18:12:36 - kernel: Traffic shaper initialised. Mar 21 18:12:36 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 18:12:36 - kernel: Traffic shaper initialised. Mar 21 18:12:36 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 18:12:36 - kernel: Traffic shaper initialised. Mar 21 18:12:36 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 18:12:36 - kernel: Traffic shaper initialised. Mar 21 18:12:36 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 18:12:36 - kernel: Traffic shaper initialised. Mar 21 18:12:36 - kernel: Traffic Shaper 0.05 for Linux 2.0 <alan@redhat.com> Mar 21 18:12:36 - kernel: Traffic shaper initialised. Mar 21 18:12:42 - named[169]: No root nameservers for class IN Mar 21 18:29:26 - login: ROOT LOGIN ON tty1 Mar 21 18:48:57 - kernel: IP fw-in rej eth0 TCP 220.99.145.138:4298 80.53.109.114:80 L=48 S=0x00 I=61647 F=0x0040 T=101 Mar 21 18:49:00 - kernel: IP fw-in rej eth0 TCP 220.99.145.138:4298 80.53.109.114:80 L=48 S=0x00 I=62084 F=0x0040 T=101 Mar 21 18:49:06 - kernel: IP fw-in rej eth0 TCP 220.99.145.138:4298 80.53.109.114:80 L=48 S=0x00 I=62953 F=0x0040 T=101 Mar 21 18:59:02 - named[169]: sysquery: findns error (2) on dns.mega.net.pl? Mar 21 19:02:28 - named[169]: sysquery: findns error (2) on plusmx1.polkomtel.com.pl? Mar 21 19:02:28 - named[169]: sysquery: findns error (2) on plusmx2.polkomtel.com.pl? Mar 21 19:02:40 - named[169]: sysquery: findns error (2) on ns.bellona.pl? Mar 21 19:02:40 - named[169]: sysquery: findns error (2) on nss.bellona.pl? (gdzies tu Wywalało net) Mar 21 19:12:34 - named[169]: NSTATS 1079896354 1079892754 A=209 Mar 21 19:12:34 - named[169]: XSTATS 1079896354 1079892754 RQ=209 RR=79 RIQ=0 RNXD=0 RFwdQ=101 RFwdR=75 RDupQ=80 RDupR=0 RFail=0 RFErr=0 RErr=0 RTCP=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=0 SAns=32 SFwdQ=101 SFwdR=75 SDupQ=19 SFail=18 SFErr=0 SErr=0 RNotNsQ=209 SNaAns=32 SNXD=0 Mar 21 19:20:41 - named[169]: sysquery: findns error (2) on ns2.tld.pl? Mar 21 19:20:41 - named[169]: sysquery: findns error (2) on ns1.tld.pl? (gdzies tu Wywalało net) Mar 21 19:50:41 - kernel: IP fw-in rej eth0 TCP 64.223.154.94:3572 80.53.109.114:80 L=48 S=0x00 I=39318 F=0x0040 T=107 Mar 21 19:50:44 - kernel: IP fw-in rej eth0 TCP 64.223.154.94:3572 80.53.109.114:80 L=48 S=0x00 I=39639 F=0x0040 T=107 Mar 21 20:12:34 - named[169]: NSTATS 1079899954 1079892754 A=517 Mar 21 20:12:34 - named[169]: XSTATS 1079899954 1079892754 RQ=517 RR=129 RIQ=0 RNXD=0 RFwdQ=197 RFwdR=123 RDupQ=254 RDupR=0 RFail=0 RFErr=0 RErr=0 RTCP=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=0 SAns=72 SFwdQ=197 SFwdR=123 SDupQ=66 SFail=64 SFErr=0 SErr=0 RNotNsQ=517 SNaAns=72 SNXD=0 Mar 21 20:21:03 - named[169]: sysquery: findns error (2) on plusmx1.polkomtel.com.pl? Mar 21 20:21:03 - named[169]: sysquery: findns error (2) on plusmx2.polkomtel.com.pl? Mar 21 20:33:11 - named[169]: sysquery: findns error (2) on ns.bellona.pl? Mar 21 20:33:11 - named[169]: sysquery: findns error (2) on nss.bellona.pl? Mar 21 20:38:19 - kernel: IP fw-in rej eth0 TCP 24.237.153.148:4152 80.53.109.114:80 L=48 S=0x00 I=14434 F=0x0040 T=105 Mar 21 20:38:21 - kernel: IP fw-in rej eth0 TCP 24.237.153.148:4152 80.53.109.114:80 L=48 S=0x00 I=14553 F=0x0040 T=105 Mar 21 20:38:27 - kernel: IP fw-in rej eth0 TCP 24.237.153.148:4152 80.53.109.114:80 L=48 S=0x00 I=14691 F=0x0040 T=105 Mar 21 20:50:00 - named[169]: sysquery: findns error (2) on plusmx1.polkomtel.com.pl? Mar 21 20:51:41 - named[169]: sysquery: findns error (2) on dns2.giga.pl? Mar 21 20:51:41 - named[169]: sysquery: findns error (2) on piskle.net? Mar 21 20:51:41 - named[169]: sysquery: findns error (2) on dns.giga.pl? Mar 21 21:07:20 - named[169]: sysquery: findns error (2) on ns.bellona.pl? Mar 21 21:07:20 - named[169]: sysquery: findns error (2) on nss.bellona.pl? Mar 21 21:12:34 - named[169]: NSTATS 1079903554 1079892754 A=830 Mar 21 21:12:34 - named[169]: XSTATS 1079903554 1079892754 RQ=830 RR=189 RIQ=0 RNXD=0 RFwdQ=301 RFwdR=178 RDupQ=434 RDupR=0 RFail=0 RFErr=0 RErr=0 RTCP=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=3 SAns=103 SFwdQ=301 SFwdR=178 SDupQ=119 SFail=115 SFErr=0 SErr=0 RNotNsQ=830 SNaAns=103 SNXD=0 Mar 21 21:16:45 - named[169]: sysquery: findns error (2) on ns2.tld.pl? Mar 21 21:16:45 - named[169]: sysquery: findns error (2) on ns1.tld.pl? Mar 21 21:27:05 - kernel: IP fw-in rej eth0 TCP 4.15.128.33:3077 80.53.109.114:80 L=48 S=0x00 I=12079 F=0x0000 T=107 Mar 21 21:27:08 - kernel: IP fw-in rej eth0 TCP 4.15.128.33:3077 80.53.109.114:80 L=48 S=0x00 I=12182 F=0x0000 T=107 Mar 21 21:27:14 - kernel: IP fw-in rej eth0 TCP 4.15.128.33:3077 80.53.109.114:80 L=48 S=0x00 I=12355 F=0x0000 T=107 W momencie kiedy rozłancza sie modem mozna zapingowac do serwera a takze do modemu. Nie mozna natomisat puscic pinga do wp.pl ani onetu (brak odpowiedzi). ZCekam na pomysły. Pozdrawiam i dzięki za kazdy pomysł. |
|
| Autor: | Kiler [ niedziela, 21 marca 2004, 23:55 ] |
| Tytuł: | |
Po pierwsze  Jaca21 - nie ma sensu dalsze wklejanie logow... One sa jak najbardziej OK, nic nie wskazuje na nieprawidlowe dzialanie serwera, poza tym monter podal juz linka do interpretacji niektorych wpisow... A te pomiedzy
Mar 21 18:12:26 - syslogd 1.3-3: restart (remote reception). a ostatnim Mar 21 18:12:36 - kernel: Traffic shaper initialised. pokazuja wylacznie proces uruchamiania sie FreeSCO - inicjowania pracy serwera... Po drugie Piotrek - cytowane przez Ciebie logi nie swiadcza o zadnych bledach - informuja wylacznie o zainicjowaniu interfejsow sieciowych "od shaper0 do shapern gdzie n jest liczbą komputerów zadeklarowanych w justice.hst (o jeden mniejszą jako że liczymy od zera...)"[cytat ze strony: http://freesco.internetdsl.pl/justice.htm ]. Nic nie swiadczy o nieprawidlowym dzialaniu justice. Poza tym ze slow Jaca21 jasno wynika ze serwer nie "zalicza" zwieszki...
No i po trzecie Jaca21 - jeszcze raz zapodam pomysl'a Jesli przy braku NET'u dostajesz prawidlowe odpowiedzi na pingi i do serwera i do modemu (to oznacza ze serwer dziala OK) i jesli przy pingowaniu "swiata" z poczatku jest "glucho" (Uplynal limit czasu zadania) a po niedlugim odstepie czasu (tylko nie pytaj dokladnie po jak dlugim - na pewno < 5min) zaczyna przychodzic odpowiedz z bramy (Odpowiedz z 80.55.....:Host docelowy jest nieosiagalny) i restart modemu przywraca wszystko do normy to znaczy ze modem jest wadliwy i nalezy go wymienic - w tym jednak celu musisz zadzwonic do TPSA powiadomic ich o takiej sytuacji i czekac na ich odpowiedz...
|
|
| Autor: | Anonymous [ poniedziałek, 22 marca 2004, 11:21 ] |
| Tytuł: | |
Cytuj: Po drugie Piotrek - cytowane przez Ciebie logi nie swiadcza o zadnych bledach - informuja wylacznie o zainicjowaniu interfejsow sieciowych "od shaper0 do shapern gdzie n jest liczbą komputerów zadeklarowanych w justice.hst (o jeden mniejszą jako że liczymy od zera...)"[cytat ze strony: http://freesco.internetdsl.pl/justice.htm ]. Nic nie swiadczy o nieprawidlowym dzialaniu justice. Poza tym ze slow Jaca21 jasno wynika ze serwer nie "zalicza" zwieszki...
Wiem że te komunikaty to nie błędy. Chciałem tylko "wskazać podejrzanego". |
|
| Strona 1 z 1 | Strefa czasowa UTC+2godz. |
| Powered by phpBB® Forum Software © phpBB Group https://www.phpbb.com/ |
|