Freesco, NND, CDN, EOS http://forum.freesco.pl/ |
|
PPPoE dziwne zachowanie ;/ http://forum.freesco.pl/viewtopic.php?f=22&t=17565 |
Strona 1 z 1 |
Autor: | wo0t?! [ czwartek, 19 marca 2009, 17:57 ] |
Tytuł: | PPPoE dziwne zachowanie ;/ |
Witam! Internet przez PPPoE po zalogoawniu dostaje swoj własny IP zew (stały) i wszystko ladnie chodzi przez 12-36h po tym czasie połaczenie jest zrywane i czasem samo wstanie a czasem nie. Kiedy zostanie wznowione mam swoj zew IP po przez ping z maszyny lokalnej do niego DNS wszystko niby jest ok. Ale DNS np nie odpowiadaja i www, GG, P2P, Skype itp nie dzialaja. Gdy recznie zrestartuje połacznie brak jakich kolwiek zmian. Dopiero REBOOT serwerka pomaga. I teraz mam pytanie czy to jest wina z mojej strony błednej CFG połaczenia czy może ISP ? Logi z messages Mar 19 16:00:21 Host pppd[3022]: Terminating on signal 15. Mar 19 16:00:21 Host last message repeated 11 times Mar 19 16:00:21 Host pppd[3268]: Terminating on signal 15. Mar 19 16:00:21 Host last message repeated 11 times Mar 19 16:00:21 Host pppd[3022]: Terminating on signal 15. Mar 19 16:00:21 Host last message repeated 11 times Mar 19 16:00:21 Host pppoe[3269]: Session 578 terminated -- received PADT from peer Mar 19 16:00:21 Host pppoe[3269]: Sent PADT Mar 19 16:00:21 Host pppd[3268]: Terminating on signal 15. Mar 19 16:00:21 Host last message repeated 8 times Mar 19 16:00:21 Host pppd[3022]: Terminating on signal 15. Mar 19 16:00:21 Host pppd[3268]: Terminating on signal 15. Mar 19 16:00:21 Host pppd[3022]: Terminating on signal 15. Mar 19 16:00:21 Host pppd[3268]: Terminating on signal 15. Mar 19 16:00:21 Host last message repeated 9 times Mar 19 16:00:21 Host pppd[3022]: Terminating on signal 15. ... Mar 19 16:03:08 Host pppd[237]: CHAP authentication failed Mar 19 16:03:08 Host pppd[237]: Connection terminated. Mar 19 16:03:08 Host pppoe[238]: Session 821 terminated -- received PADT from peer Mar 19 16:03:08 Host pppoe[238]: Sent PADT Mar 19 16:03:08 Host pppd[237]: Using interface ppp0 Mar 19 16:03:08 Host pppd[237]: Connect: ppp0 <--> /dev/pts/0 Mar 19 16:03:08 Host pppoe[682]: PPP session is 462 (0x1ce) Mar 19 16:03:12 Host pppd[237]: CHAP authentication succeeded Log z Errors Mar 19 01:24:26 Host pppoe[238]: Bad TCP checksum 5c98 Mar 19 01:50:02 Host pppoe[238]: Bad TCP checksum faf8 Mar 19 02:23:14 Host pppoe[238]: Bad TCP checksum 9e75 Mar 19 02:53:17 Host pppoe[238]: Bad TCP checksum 3165 Mar 19 03:32:47 Host pppoe[238]: Bad TCP checksum f3ea Mar 19 05:24:22 Host pppoe[238]: Bad TCP checksum 2ca8 Mar 19 05:34:17 Host pppoe[238]: Bad TCP checksum 1f4 Mar 19 05:34:50 Host pppoe[238]: Bad TCP checksum 1065 Mar 19 06:34:31 Host pppoe[238]: Bad TCP checksum f1e9 Mar 19 09:28:16 Host pppoe[238]: Bad TCP checksum b05c Mar 19 09:39:04 Host pppoe[238]: Bad TCP checksum 3083 Mar 19 15:43:30 Host pppoe[238]: Bad TCP checksum b08c Mar 19 15:54:13 Host pppoe[238]: Bad TCP checksum b3a6 Mar 19 15:58:11 Host pppoe[238]: read (asyncReadFromPPP): Session 652: Input/output error Mar 19 15:59:11 Host pppoe[3023]: read (asyncReadFromPPP): Session 767: Input/output error Mar 19 16:00:10 Host pppoe[3214]: read (asyncReadFromPPP): Session 634: Input/output error Mar 19 16:00:21 Host pppoe[3269]: PADT: Generic-Error: RP-PPPoE: Child pppd process terminated tutaj po restarcie maszyny Mar 19 16:02:10 Host kernel: e100: eth0 NIC Link is Up 100 Mbps Full duplex Mar 19 16:03:08 Host pppoe[238]: PADT: Generic-Error: RP-PPPoE: Child pppd process terminated i tutaj o dziwko jak narazie wszystko chodzi. Wina leży po stronie ISP ? czy po mojej ? Z góry dziękuje za pomoc |
Autor: | luki_nowy [ czwartek, 19 marca 2009, 22:55 ] |
Tytuł: | |
pokaz config i pppoe-serwer aha wersje ppp, rp-pppoe ![]() |
Autor: | wo0t?! [ czwartek, 19 marca 2009, 23:22 ] |
Tytuł: | |
standardowy cfg z net_confa opcja neorj zmianie ulegly tylko DNS podałem mojego ISP oraz login i haslo. używam rp-pppoe pppoe.conf Cytuj: #*********************************************************************** # # pppoe.conf # # Configuration file for rp-pppoe. Edit as appropriate and install in # /etc/ppp/pppoe.conf # # NOTE: This file is used by the pppoe-start, pppoe-stop, pppoe-connect and # pppoe-status shell scripts. It is *not* used in any way by the # "pppoe" executable. # # Copyright (C) 2000 Roaring Penguin Software Inc. # # This file may be distributed under the terms of the GNU General # Public License. # # LIC: GPL # $Id: pppoe.conf,v 1.11 2005/08/09 02:49:12 dfs Exp $ #*********************************************************************** # When you configure a variable, DO NOT leave spaces around the "=" sign. # Ethernet card connected to DSL modem ETH="eth0" # PPPoE user name. You may have to supply "@provider.com" Sympatico # users in Canada do need to include "@sympatico.ca" # Sympatico uses PAP authentication. Make sure /etc/ppp/pap-secrets # contains the right username/password combination. # For Magma, use xxyyzz@magma.ca USER="XXXXX" # Bring link up on demand? Default is to leave link up all the time. # If you want the link to come up on demand, set DEMAND to a number indicating # the idle time after which the link is brought down. DEMAND=no #DEMAND=300 # DNS type: SERVER=obtain from server; SPECIFY=use DNS1 and DNS2; # NOCHANGE=do not adjust. DNSTYPE=SERVER # Obtain DNS server addresses from the peer (recent versions of pppd only) # In old config files, this used to be called USEPEERDNS. Changed to # PEERDNS for better Red Hat compatibility PEERDNS=yes DNS1= DNS2= # Make the PPPoE connection your default route. Set to # DEFAULTROUTE=no if you don't want this. DEFAULTROUTE=yes ### ONLY TOUCH THE FOLLOWING SETTINGS IF YOU'RE AN EXPERT # How long pppoe-start waits for a new PPP interface to appear before # concluding something went wrong. If you use 0, then pppoe-start # exits immediately with a successful status and does not wait for the # link to come up. Time is in seconds. # WARNING WARNING WARNING: # # If you are using rp-pppoe on a physically-inaccessible host, set # CONNECT_TIMEOUT to 0. This makes SURE that the machine keeps trying # to connect forever after pppoe-start is called. Otherwise, it will # give out after CONNECT_TIMEOUT seconds and will not attempt to # connect again, making it impossible to reach. CONNECT_TIMEOUT=30 # How often in seconds pppoe-start polls to check if link is up CONNECT_POLL=2 # Specific desired AC Name ACNAME= # Specific desired service name SERVICENAME= # Character to echo at each poll. Use PING="" if you don't want # anything echoed PING="." # File where the pppoe-connect script writes its process-ID. # Three files are actually used: # $PIDFILE contains PID of pppoe-connect script # $PIDFILE.pppoe contains PID of pppoe process # $PIDFILE.pppd contains PID of pppd process CF_BASE=`basename $CONFIG` PIDFILE="/var/run/$CF_BASE-pppoe.pid" # Do you want to use synchronous PPP? "yes" or "no". "yes" is much # easier on CPU usage, but may not work for you. It is safer to use # "no", but you may want to experiment with "yes". "yes" is generally # safe on Linux machines with the n_hdlc line discipline; unsafe on others. SYNCHRONOUS=no # Do you want to clamp the MSS? Here's how to decide: # - If you have only a SINGLE computer connected to the DSL modem, choose # "no". # - If you have a computer acting as a gateway for a LAN, choose "1412". # The setting of 1412 is safe for either setup, but uses slightly more # CPU power. CLAMPMSS=1412 #CLAMPMSS=no # LCP echo interval and failure count. LCP_INTERVAL=20 LCP_FAILURE=3 # PPPOE_TIMEOUT should be about 4*LCP_INTERVAL PPPOE_TIMEOUT=80 # Firewalling: One of NONE, STANDALONE or MASQUERADE FIREWALL=NONE # Linux kernel-mode plugin for pppd. If you want to try the kernel-mode # plugin, use LINUX_PLUGIN=/etc/ppp/plugins/rp-pppoe.so LINUX_PLUGIN= # Any extra arguments to pass to pppoe. Normally, use a blank string # like this: PPPOE_EXTRA="" # Rumour has it that "Citizen's Communications" with a 3Com # HomeConnect DSL Modem DualLink requires these extra options: # PPPOE_EXTRA="-f 3c12:3c13 -S ISP" # Any extra arguments to pass to pppd. Normally, use a blank string # like this: PPPD_EXTRA="" ########## DON'T CHANGE BELOW UNLESS YOU KNOW WHAT YOU ARE DOING # If you wish to COMPLETELY overrride the pppd invocation: # Example: # OVERRIDE_PPPD_COMMAND="pppd call dsl" # If you want pppoe-connect to exit when connection drops: # RETRY_ON_FAILURE=no pppoe-serwer Cytuj: # PPP options for the PPPoE server
# LIC: GPL require-pap login lcp-echo-interval 10 lcp-echo-failure 2 Teraz wszystko jest ok. Jutro po powrocie do domu obstawiam ze na 90% Internetu juz nie bedzie... a gdy lookne w Logi okazac sie moze ze od godziny 9 rano juz go nie bedzie... oczywiscie podaje tylko przyklad wydarzeń. Cały system z pakietami z aktualizowany. |
Strona 1 z 1 | Strefa czasowa UTC+2godz. |
Powered by phpBB® Forum Software © phpBB Group https://www.phpbb.com/ |