|
Seb8517 (banned)
Member
2014-May-10 1:18 pm
Sagemcom de merde ...Salut toute monde
J'ai un drôle de problème ... Jeudi j'ai eux pas moins de 7 reset en même pas 5 heure !!
Voici la version du logiciel du sagemcom Version logicielle: FAST2864_v6843A Version de secours: FAST2864_v7843A
Voici les log
Dec 31 19:00:33 [PPPoE]: THE SYSTEM UP
Dec 31 19:00:33 [PPPoE]: PPPoE Relay enabled
Dec 31 19:00:33 [PPPoE]: Send PADT
Dec 31 19:00:33 [PPPoE]: Send PADI
Dec 31 19:00:33 [PPPoE]: Receive PADO
Dec 31 19:00:33 [PPPoE]: Send PADR
Dec 31 19:00:33 [PPPoE]: Receive PADS
Dec 31 19:00:34 [PPPoE]: Receive PADO
Dec 31 19:00:34 [PPPoE]: PPPoE Passthrough session opened: server=7c:20:64:8a:5c:aa(eth1.35:11), client=48:f8:b3:a1:98:41(eth0:1)
Dec 31 19:00:34 [PPPoE]: Receive PADS
Dec 31 19:00:25 [SYSTEM]: mt_ma: device ppp0 state change (up, ppp reset=0)
Dec 31 19:00:36 [SYSTEM]: Got new time: May 7 21:16:50 2014
May 7 21:17:06 [DHCP]: [SERVER] DHCPNAK on 192.168.1.115 to bc:ee:7b:79:40:01 via br0
May 7 21:17:07 [DHCP]: [SERVER] DHCPDISCOVER from bc:ee:7b:79:40:01
May 7 21:17:07 [DHCP]: [SERVER] DHCP_OFFER sent
May 7 21:17:07 [SYSTEM]: [HPNA]: HPNA Link Up
May 7 21:17:09 [DHCP]: [SERVER] DHCP_ACK sent
May 7 21:17:34 [PPPoE]: Receive PADT
May 7 21:18:47 [PPPoE]: PPPoE Passthrough session closed: server=7c:20:64:8a:5c:aa(eth1.35:11), client=48:f8:b3:a1:98:41(eth0:1): Received PADT
May 7 21:18:47 [PPPoE]: Receive PADT
May 7 21:18:51 [INTERFACE]: [WIRELESS] WIFI is now running
May 7 20:26:39 [DHCP]: [SERVER] DHCPNAK on 192.168.1.115 to bc:ee:7b:79:40:01 via br0
May 7 20:27:01 [DHCP]: [SERVER] DHCPDISCOVER from d8:31:cf:f7:73:0f
May 7 20:27:01 [DHCP]: [SERVER] DHCP_OFFER sent
May 7 20:27:01 [DHCP]: [SERVER] DHCPNAK on 192.168.1.127 to d8:31:cf:f7:73:0f via br0
May 7 20:31:05 [INTERFACE]: [ETHERNET]: WAN LINK IS DOWN
May 7 20:32:25 [INTERFACE]: [ETHERNET]:WAN LINK IS UP
May 7 20:32:45 [PPPoE]: Serial link appears to be disconnected.
May 7 20:32:45 [PPPoE]: Link Down
May 7 20:32:45 [SYSTEM]: mt_ma: device ppp0 state change (down, ppp reset=0)
May 7 20:32:46 [PPPoE]: Disconnecting
May 7 20:32:46 [PPPoE]: Send PADT
May 7 20:32:46 [PPPoE]: Connection terminated.
May 7 20:33:16 [PPPoE]: Send PADT
May 7 20:33:16 [PPPoE]: Send PADI
May 7 20:33:16 [PPPoE]: Receive PADO
May 7 20:33:16 [PPPoE]: Send PADR
May 7 20:33:16 [PPPoE]: Receive PADS
May 7 20:33:16 [PPPoE]: PPP Connexion
May 7 20:33:19 [PPPoE]: Link Established
May 7 20:33:19 [PPPoE]: Remote message: Login ok
May 7 20:33:19 [PPPoE]: Local IP address 69.157.138.237
May 7 20:33:19 [PPPoE]: Remote IP address 10.11.16.145
May 7 20:33:19 [PPPoE]: Primary DNS address 207.164.234.129
May 7 20:33:19 [PPPoE]: Secondary DNS address 207.164.234.193
May 7 20:33:20 [SYSTEM]: mt_ma: device ppp0 state change (up, ppp reset=0)
May 7 20:33:22 [SYSTEM]: Got new time: May 7 20:33:20 2014
May 7 20:34:21 [DHCP]: [SERVER] DHCPNAK on 192.168.1.115 to bc:ee:7b:79:40:01 via br0
May 7 20:34:21 [DHCP]: [SERVER] DHCPDISCOVER from bc:ee:7b:79:40:01
May 7 20:34:21 [DHCP]: [SERVER] DHCP_OFFER sent
May 7 20:34:23 [DHCP]: [SERVER] DHCP_ACK sent
May 7 07:10:41 [SYSTEM]: Got new time: May 7 07:09:13 2014
May 6 17:47:28 [DHCP]: [SERVER] DHCPREQUEST for 192.168.2.23 from 38:6b:bb:f0:e5:b3, SET TOP BOX Connected
May 6 17:47:28 [DHCP]: [SERVER] DHCP_ACK sent
May 6 17:53:35 [DHCP]: [SERVER] DHCPREQUEST for 192.168.2.11 from 38:6b:bb:f0:df:e3, SET TOP BOX Connected
May 6 17:53:35 [DHCP]: [SERVER] DHCP_ACK sent
May 6 17:53:52 [DHCP]: [SERVER] DHCPREQUEST for 192.168.2.10 from 38:6b:bb:f0:df:ca, SET TOP BOX Connected
May 6 17:53:52 [DHCP]: [SERVER] DHCP_ACK sent
May 6 19:37:52 [SYSTEM]: Got new time: May 6 19:36:31 2014
Mais j'ai enlever mon linksys et le problemme se produit plus ! |
|
Nitra join:2011-09-15 Montreal |
Nitra
Member
2014-May-10 2:41 pm
Looks like you have a line problem...... Things like this happen when it warms up outside. |
|
|
Seb8517 (banned)
Member
2014-May-10 2:46 pm
Je suis en FTTH ... |
|
Nitra join:2011-09-15 Montreal |
Nitra
Member
2014-May-10 2:50 pm
Call Bell. There's a line issue. It's clear from the log, it's losing PPPOE. |
|
1 edit |
said by Nitra:Call Bell. There's a line issue. It's clear from the log, it's losing PPPOE. Losing PPPOE could be du to plenty of things. Logs from the Sagemcom don't even follow a time order... wth lol. |
|
Glen1These Are The Good Ol' Days. MVM join:2002-05-24 GTA Canada |
to Seb8517
You say it is FTTH, check the connection between the modem (Sagemcom) and the Fiber termination...the line: "Serial link appears to be disconnected" might be the key to it. The fiber itself might be experiencing trouble...call your provider. Check the ethernet cable between the two possibly exchanging it for another cable...check the RJ45 connectors to make sure they are firmly connected. |
|
|
|
Seb8517 (banned)
Member
2014-May-14 3:20 pm
J'ai reset tous me équipement et voici le log que j'ai
May 14 14:32:24 [PPPoE]: THE SYSTEM UP
May 14 14:32:25 [PPPoE]: PPPoE Relay enabled
May 14 14:32:25 [PPPoE]: Send PADT
May 14 14:32:25 [PPPoE]: Send PADI
May 14 14:32:25 [PPPoE]: Receive PADO
May 14 14:32:25 [PPPoE]: Send PADR
May 14 14:32:25 [PPPoE]: Receive PADS
May 14 14:32:26 [DHCP]: [SERVER] DHCP_ACK sent
May 14 14:32:45 [SYSTEM]: [HPNA]: HPNA Link Down
May 14 14:32:57 [SYSTEM]: [UPnP]: NAT entry deletion not possible
May 14 14:32:59 [SYSTEM]: [UPnP]: NAT entry deletion not possible
May 14 14:33:01 [SYSTEM]: [UPnP]: Entry Add
May 14 14:33:04 [SYSTEM]: [UPnP]: Entry Add
May 14 14:33:08 [SYSTEM]: [HPNA]: HPNA Link Up
May 14 14:33:16 [DHCP]: [SERVER] DHCP_ACK sent
May 14 14:33:40 [SYSTEM]: mt_ma: device ath0 state change (down, ppp reset=0)
May 14 14:33:40 [INTERFACE]: [WIRELESS] WIFI is now OFF
May 14 14:33:51 [INTERFACE]: [WIRELESS] WIFI is now running
May 14 14:45:19 [SYSTEM]: mt_ma: device eth1.36 state change (down, ppp reset=0)
May 14 14:45:19 [INTERFACE]: [ETHERNET]: DEV eth1.36 is UP
May 14 14:45:19 [DHCP]: [CLIENT] DHCP Client opened successfully for dev eth1.36
May 14 14:45:19 [INTERFACE]: [SYSTEM]IGMP changed: interface: eth1.36
May 14 14:45:19 [INTERFACE]: [ETHERNET]: DEV eth1.36 is UP
May 14 14:45:19 [DHCP]: [CLIENT] DHCP Client opened successfully for dev eth1.36
May 14 14:45:20 [DHCP]: [CLIENT] DHCPDISCOVER on eth1.36
May 14 14:45:20 [DHCP]: [CLIENT] DHCPOFFER received
May 14 14:45:20 [DHCP]: [CLIENT] DHCPREQUEST on eth1.36
May 14 14:45:21 [DHCP]: [CLIENT] DHCPACK Received
May 14 14:45:21 [DHCP]: [CLIENT] Update existing Lease
May 14 14:45:21 [DHCP]: [CLIENT] lease_time = 604800, renew_time = 1400395521
May 14 14:45:21 [SYSTEM]: mt_ma: device eth1.36 state change (up, ppp reset=0)
May 14 14:45:28 [SYSTEM]: mt_ma: device ppp0 state change (down, ppp reset=0)
May 14 14:45:28 [PPPoE]: Link Down
May 14 14:45:28 [PPPoE]: Connection terminated.
May 14 14:45:29 [PPPoE]: Disconnecting
May 14 14:45:29 [PPPoE]: Send PADT
May 14 14:45:29 [PPPoE]: DEV_PPPOE DOWN
May 14 14:45:29 [PPPoE]: PPP DEVICE UP
May 14 14:45:30 [PPPoE]: PPP Connexion
May 14 14:45:30 [PPPoE]: Send PADT
May 14 14:45:30 [PPPoE]: Send PADI
May 14 14:45:30 [PPPoE]: Receive PADO
May 14 14:45:30 [PPPoE]: Send PADR
May 14 14:45:30 [PPPoE]: Receive PADS
May 14 14:45:33 [PPPoE]: Link Established
May 14 14:45:33 [PPPoE]: Remote message: Login ok
May 14 14:45:34 [PPPoE]: Local IP address 70.29.204.250
May 14 14:45:34 [PPPoE]: Remote IP address 10.11.16.145
May 14 14:45:34 [PPPoE]: Primary DNS address 207.164.234.129
May 14 14:45:34 [PPPoE]: Secondary DNS address 207.164.234.193
May 14 14:45:34 [SYSTEM]: mt_ma: device ppp0 state change (up, ppp reset=0)
May 14 14:46:27 [SYSTEM]: [UPnP]: Entry Add
May 14 14:46:29 [SYSTEM]: [UPnP]: Entry Add
May 14 14:56:41 [SYSTEM]: mt_ma: device ath0 state change (down, ppp reset=0)
May 14 14:56:41 [INTERFACE]: [WIRELESS] WIFI is now OFF
May 14 14:59:42 [DHCP]: [SERVER] DHCPDISCOVER from 48:f8:b3:a1:98:41
May 14 14:59:42 [DHCP]: [SERVER] DHCP_OFFER sent
May 14 14:59:44 [DHCP]: [SERVER] DHCP_ACK sent
May 14 14:59:59 [PPPoE]: Receive PADO
May 14 14:59:59 [PPPoE]: PPPoE Passthrough session opened: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1)
May 14 14:59:59 [PPPoE]: Receive PADS
May 14 14:59:59 [PPPoE]: PPPoE Passthrough session closed: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1): Received PADT
May 14 15:00:13 [DHCP]: [SERVER] DHCP_ACK sent
May 14 15:00:13 [DHCP]: [SERVER] DHCPRELEASE of 192.168.2.13 from 48:f8:b3:a1:98:41 via br0 (found)
May 14 15:00:29 [PPPoE]: Receive PADO
May 14 15:00:29 [PPPoE]: PPPoE Passthrough session opened: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1)
May 14 15:00:29 [PPPoE]: Receive PADS
May 14 15:00:32 [PPPoE]: PPPoE Passthrough session closed: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1): Received PADT
May 14 15:00:32 [PPPoE]: Receive PADT
May 14 15:01:05 [PPPoE]: Receive PADO
May 14 15:01:05 [PPPoE]: PPPoE Passthrough session opened: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1)
May 14 15:01:05 [PPPoE]: Receive PADS
May 14 15:01:09 [PPPoE]: PPPoE Passthrough session closed: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1): Received PADT
May 14 15:01:09 [PPPoE]: Receive PADT
May 14 15:01:32 [PPPoE]: Receive PADO
May 14 15:01:32 [PPPoE]: PPPoE Passthrough session opened: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1)
May 14 15:01:32 [PPPoE]: Receive PADS
May 14 15:01:35 [PPPoE]: PPPoE Passthrough session closed: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1): Received PADT
May 14 15:01:35 [PPPoE]: Receive PADT
May 14 15:02:08 [PPPoE]: Receive PADO
May 14 15:02:08 [PPPoE]: PPPoE Passthrough session opened: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1)
May 14 15:02:08 [PPPoE]: Receive PADS
May 14 15:02:11 [PPPoE]: PPPoE Passthrough session closed: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1): Received PADT
May 14 15:02:11 [PPPoE]: Receive PADT
May 14 15:02:36 [PPPoE]: Receive PADO
May 14 15:02:36 [PPPoE]: PPPoE Passthrough session opened: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1)
May 14 15:02:36 [PPPoE]: Receive PADS
May 14 15:02:39 [PPPoE]: PPPoE Passthrough session closed: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1): Received PADT
May 14 15:02:39 [PPPoE]: Receive PADT
May 14 15:03:12 [PPPoE]: Receive PADO
May 14 15:03:12 [PPPoE]: PPPoE Passthrough session opened: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1)
May 14 15:03:12 [PPPoE]: Receive PADS
May 14 15:03:16 [PPPoE]: PPPoE Passthrough session closed: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1): Received PADT
May 14 15:03:16 [PPPoE]: Receive PADT
May 14 15:03:39 [PPPoE]: Receive PADO
May 14 15:03:39 [PPPoE]: PPPoE Passthrough session opened: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1)
May 14 15:03:39 [PPPoE]: Receive PADS
May 14 15:03:42 [PPPoE]: PPPoE Passthrough session closed: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1): Received PADT
May 14 15:03:42 [PPPoE]: Receive PADT
May 14 15:04:15 [PPPoE]: Receive PADO
May 14 15:04:15 [PPPoE]: PPPoE Passthrough session opened: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1)
May 14 15:04:15 [PPPoE]: Receive PADS
May 14 15:04:18 [PPPoE]: PPPoE Passthrough session closed: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1): Received PADT
May 14 15:04:18 [PPPoE]: Receive PADT
May 14 15:04:43 [PPPoE]: Receive PADO
May 14 15:04:43 [PPPoE]: PPPoE Passthrough session opened: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1)
May 14 15:04:43 [PPPoE]: Receive PADS
May 14 15:04:46 [PPPoE]: PPPoE Passthrough session closed: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1): Received PADT
May 14 15:04:46 [PPPoE]: Receive PADT
May 14 15:05:15 [PPPoE]: Receive PADO
May 14 15:05:15 [PPPoE]: PPPoE Passthrough session opened: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1)
May 14 15:05:15 [PPPoE]: Receive PADS
May 14 15:05:44 [PPPoE]: Receive PADO
May 14 15:05:44 [PPPoE]: PPPoE Passthrough session opened: server=7c:20:64:8a:5c:aa(eth1.35:2), client=48:f8:b3:a1:98:41(eth0:2)
May 14 15:05:44 [PPPoE]: Receive PADS
May 14 15:05:45 [PPPoE]: PPPoE Passthrough session closed: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1): Received PADT
May 14 15:05:45 [PPPoE]: Receive PADT
May 14 15:09:20 [DHCP]: [SERVER] DHCPNAK on 192.168.1.115 to bc:ee:7b:79:40:01 via br0
May 14 15:09:20 [DHCP]: [SERVER] DHCPDISCOVER from bc:ee:7b:79:40:01
May 14 15:09:20 [DHCP]: [SERVER] DHCP_OFFER sent
May 14 15:09:22 [DHCP]: [SERVER] DHCP_ACK sent
May 14 15:09:28 [SYSTEM]: [UPnP]: Entry Add
May 14 15:09:28 [SYSTEM]: [UPnP]: NAT is in conflict
May 14 15:09:30 [SYSTEM]: [UPnP]: Entry Add
May 14 15:09:31 [SYSTEM]: [UPnP]: Entry Add
May 14 15:09:31 [SYSTEM]: [UPnP]: NAT is in conflict
May 14 15:09:31 [SYSTEM]: [UPnP]: Entry Add
May 14 15:09:32 [SYSTEM]: [UPnP]: Entry Add
May 14 15:09:33 [SYSTEM]: [UPnP]: Entry Add
May 14 15:09:35 [SYSTEM]: [UPnP]: Entry Add
May 14 15:09:36 [SYSTEM]: [UPnP]: Entry Add
C'est quoi c'est ligne suivante
May 14 15:05:44 [PPPoE]: PPPoE Passthrough session opened: server=7c:20:64:8a:5c:aa(eth1.35:2), client=48:f8:b3:a1:98:41(eth0:2)
May 14 15:05:44 [PPPoE]: Receive PADS
May 14 15:05:45 [PPPoE]: PPPoE Passthrough session closed: server=7c:20:64:8a:5c:aa(eth1.35:1), client=48:f8:b3:a1:98:41(eth0:1): Received PADT
May 14 15:05:45 [PPPoE]: Receive PADT
May 14 15:09:20 [DHCP]: [SERVER] DHCPNAK on 192.168.1.115 to bc:ee:7b:79:40:01 via br0
May 14 15:09:20 [DHCP]: [SERVER] DHCPDISCOVER from bc:ee:7b:79:40:01
May 14 15:09:31 [SYSTEM]: [UPnP]: NAT is in conflict |
|
Frank_IT Premium Member join:2003-11-01 Montreal |
to Seb8517
Appelle.. c'est le best..
malgre que la derniere ligne est bizarre |
|
|
Seb8517 (banned)
Member
2014-May-14 3:45 pm
Je vais voir si sa cause de reset avent .. sinon je vais rester avec le sagemcom jusqu'au lancement des nouveau Sagemcom .. Je vais lécher des culs pour l'avoir sans tech.. .... |
|
|
the_riddler to Seb8517
Anon
2014-May-16 8:46 am
to Seb8517
Is your Linksys router PPPoE setup for connecting on-demand or always on? |
|
|
Seb8517 (banned)
Member
2014-May-16 12:38 pm
Alway on si je me trompe pas |
|
|
Quel est l'IP interne de ton SAGEMCOM et ensuite celle de ton LinkSYS? |
|
|
Seb8517 (banned)
Member
2014-May-16 1:29 pm
192.168.2.1 et .1.1 |
|
|
to Seb8517
Et si tu fais pas de passtrough? Ça reset quand même? |
|
Martin Premium Member join:2005-05-05 Blainville, QC |
to Seb8517
said by Seb8517:Je vais lécher des culs pour l'avoir sans tech.. .... Pour ton info, tu pourra l'avoir sans devoir lécher des culs comme tu dit mais tu devra sortir ton porte-feuille!!!! Pour les clients actuels, il y aura un frais de location permanente de 200$ facturé automatiquement au compte si le Sagemcon actuel est remplacé par le modèle 2000 outch!!!! Et espère pas te le faire créditer, ce sera impossible. |
|
|
to Seb8517
Pogne toi un routeur qui supporte le vlan tagging.... Pis plug toi dans le port deux de l'ont. |
|
|
Seb8517 (banned)
Member
2014-May-24 3:22 pm
said by demonte21:Pogne toi un routeur qui supporte le vlan tagging.... Pis plug toi dans le port deux de l'ont. De 1, le port 2a4 du ont est bloquer, De 2 si je fais sa je peux pas garder mon b1 dans sagemcom si je fait... Mais la solution de la Switch est plus envisageable |
|
Frank_IT Premium Member join:2003-11-01 Montreal |
Frank_IT
Premium Member
2014-May-24 5:33 pm
Bah, enlever les apps de la tivi.. pas si dramatique que ca c de meme que je suis depuis le debut et men plaint pas |
|
|
Seb8517 (banned)
Member
2014-May-24 6:32 pm
BTW je suis entrain de lecher cul a un de mes contact chez Bell |
|