O Canada! > Canadian > Bell Canada > [Internet] Trouble with Fibe 25 and Sagemcom Modem

[Internet] Trouble with Fibe 25 and Sagemcom Modem

I have the same problem... that's why I've limited my usages of torrents to 1 at the time and during non throttling hours.

Nobody seems to know whats the probleme... I never have this trouble when using newgroups (download). Always have this probleme with torrents. So it's something with to much connection open or upload... is it cause by DPI machine or another Bell equipement, dont know.

Interesting. Glad to know I'm not the only one. But recently this has been happening even when I'm not doing any torrenting. But it does seem to only happen during "peak hours" when the DPI boxes are up and running.

Same, once every night around midnight. Although the outage lasts for 2 minutes

Nov 26 23:47:50 DHCP [581]: dhcp_detect: No DHCP server detected on dev eth2.36
Nov 26 23:50:09 DHCP [581]: DHCPINFORM from 192.168.2.12
Nov 26 23:50:12 DHCP [581]: DHCPINFORM from 192.168.2.12
Nov 26 23:50:33 DHCP [581]: DHCPDISCOVER from 00:09:34:0a:ff:08 via br0
Nov 26 23:50:33 DHCP [581]: DHCPDISCOVER from 00:09:34:0a:ff:08 via br0. Requested IP: 0.0.0.0
Nov 26 23:50:33 DHCP [581]: Added new lease for IP: 192.168.2.14, new ID 1
Nov 26 23:50:35 DHCP [581]: DHCPDISCOVER from 00:09:34:0a:ff:08 via br0
Nov 26 23:50:35 DHCP [581]: DHCPDISCOVER from 00:09:34:0a:ff:08 via br0. Requested IP: 0.0.0.0
Nov 26 23:50:35 DHCP [581]: Abandoning IP address 192.168.2.14: unvalid
Nov 26 23:50:35 DHCP [581]: Added new lease for IP: 192.168.2.14, new ID 1
Nov 26 23:50:36 DHCP [581]: DHCPOFFER on 192.168.2.14 to 00:09:34:0a:ff:08 via br0 (eth0)
Nov 26 23:50:36 DHCP [581]: DHCPREQUEST for 192.168.2.14 from 00:09:34:0a:ff:08 via br0
Nov 26 23:50:36 DHCP [581]: DHCPACK on 192.168.2.14 to 00:09:34:0a:ff:08 via br0 (eth0)
Nov 26 23:50:37 DHCP [581]: DHCPOFFER on 192.168.2.14 to 00:09:34:0a:ff:08 via br0 (eth0)
Nov 26 23:51:09 DHCP [581]: DHCPREQUEST for 192.168.2.12 from 00:26:c7:44:78:de via br0
Nov 26 23:51:09 DHCP [581]: DHCPACK on 192.168.2.12 to 00:26:c7:44:78:de via br0 (ath0)
Nov 26 23:51:21 DHCP [581]: DHCPINFORM from 192.168.2.12
Nov 26 23:51:24 DHCP [581]: DHCPINFORM from 192.168.2.12
Nov 26 23:51:50 DHCP [581]: DHCPDISCOVER from 00:0e:08:fa:81:7a via br0
Nov 26 23:51:50 DHCP [581]: DHCPDISCOVER from 00:0e:08:fa:81:7a via br0. Requested IP: 0.0.0.0
Nov 26 23:51:50 DHCP [581]: Added new lease for IP: 192.168.2.15, new ID 5
Nov 26 23:51:53 DHCP [581]: DHCPOFFER on 192.168.2.15 to 00:0e:08:fa:81:7a via br0 (eth0)
Nov 26 23:51:53 DHCP [581]: DHCPREQUEST for 192.168.2.15 from 00:0e:08:fa:81:7a via br0
Nov 26 23:51:53 DHCP [581]: DHCPACK on 192.168.2.15 to 00:0e:08:fa:81:7a via br0 (eth0)
Nov 26 23:53:54 DHCP [581]: DHCPDISCOVER from cc:55:ad:92:41:3b via br0
Nov 26 23:53:54 DHCP [581]: DHCPDISCOVER from cc:55:ad:92:41:3b via br0. Requested IP: 0.0.0.0
Nov 26 23:53:54 DHCP [581]: Abandoning IP address 192.168.2.11: unvalid
Nov 26 23:53:54 DHCP [581]: Added new lease for IP: 192.168.2.11, new ID 3
Nov 26 23:53:55 DHCP [581]: DHCPDISCOVER from cc:55:ad:92:41:3b via br0
Nov 26 23:53:55 DHCP [581]: DHCPDISCOVER from cc:55:ad:92:41:3b via br0. Requested IP: 0.0.0.0
Nov 26 23:53:55 DHCP [581]: Abandoning IP address 192.168.2.11: unvalid
Nov 26 23:53:55 DHCP [581]: Added new lease for IP: 192.168.2.11, new ID 3
Nov 26 23:53:57 DHCP [581]: DHCPOFFER on 192.168.2.11 to cc:55:ad:92:41:3b via br0 (ath0)
Nov 26 23:53:57 DHCP [581]: DHCPREQUEST for 192.168.2.11 from cc:55:ad:92:41:3b via br0
Nov 26 23:53:57 DHCP [581]: DHCPACK on 192.168.2.11 to cc:55:ad:92:41:3b via br0 (ath0)
Nov 26 23:53:57 DHCP [581]: DHCPOFFER on 192.168.2.11 to cc:55:ad:92:41:3b via br0 (ath0)
Nov 26 23:54:04 DHCP [581]: DHCPDISCOVER from 14:74:11:bc:2a:6f via br0
Nov 26 23:54:04 DHCP [581]: DHCPDISCOVER from 14:74:11:bc:2a:6f via br0. Requested IP: 0.0.0.0
Nov 26 23:54:05 DHCP [581]: DHCPDISCOVER from 14:74:11:bc:2a:6f via br0
Nov 26 23:54:05 DHCP [581]: DHCPDISCOVER from 14:74:11:bc:2a:6f via br0. Requested IP: 0.0.0.0
Nov 26 23:54:05 DHCP [581]: already acking lease 192.168.2.13
Nov 26 23:54:06 DHCP [581]: DHCPDISCOVER from 14:74:11:bc:2a:6f via br0
Nov 26 23:54:06 DHCP [581]: DHCPDISCOVER from 14:74:11:bc:2a:6f via br0. Requested IP: 0.0.0.0
Nov 26 23:54:06 DHCP [581]: already acking lease 192.168.2.13
Nov 26 23:54:07 DHCP [581]: DHCPOFFER on 192.168.2.13 to 14:74:11:bc:2a:6f via br0 (ath0)
Nov 26 23:54:07 DHCP [581]: DHCPREQUEST for 192.168.2.13 from 14:74:11:bc:2a:6f via br0
Nov 26 23:54:07 DHCP [581]: DHCPACK on 192.168.2.13 to 14:74:11:bc:2a:6f via br0 (ath0)
Nov 26 23:57:01 DHCP [581]: DHCPDISCOVER from 00:0e:08:fa:81:7a via br0
Nov 26 23:57:01 DHCP [581]: DHCPDISCOVER from 00:0e:08:fa:81:7a via br0. Requested IP: 0.0.0.0
Nov 26 23:57:03 DHCP [581]: DHCPOFFER on 192.168.2.15 to 00:0e:08:fa:81:7a via br0 (eth0)
Nov 26 23:57:03 DHCP [581]: DHCPREQUEST for 192.168.2.15 from 00:0e:08:fa:81:7a via br0
Nov 26 23:57:03 DHCP [581]: DHCPACK on 192.168.2.15 to 00:0e:08:fa:81:7a via br0 (eth0)
Nov 26 23:59:22 DHCP [581]: DHCPREQUEST for 192.168.2.12 from 00:26:c7:44:78:de via br0
Nov 26 23:59:22 DHCP [581]: DHCPACK on 192.168.2.12 to 00:26:c7:44:78:de via br0 (ath0)
Nov 26 23:59:25 DHCP [581]: DHCPINFORM from 192.168.2.12
Nov 26 23:59:28 DHCP [581]: DHCPINFORM from 192.168.2.12
Nov 27 00:04:29 DHCP [581]: DHCPINFORM from 192.168.2.12
Nov 27 00:04:32 DHCP [581]: DHCPINFORM from 192.168.2.12
Nov 27 00:11:58 DHCP [581]: DHCPINFORM from 192.168.2.12
Nov 27 00:12:01 DHCP [581]: DHCPINFORM from 192.168.2.12
Nov 27 00:12:33 DHCP [581]: DHCPDISCOVER from 00:09:34:0a:ff:08 via br0
Nov 27 00:12:33 DHCP [581]: DHCPDISCOVER from 00:09:34:0a:ff:08 via br0. Requested IP: 0.0.0.0
Nov 27 00:12:34 DHCP [581]: DHCPDISCOVER from 00:09:34:0a:ff:08 via br0
Nov 27 00:12:34 DHCP [581]: DHCPDISCOVER from 00:09:34:0a:ff:08 via br0. Requested IP: 0.0.0.0
Nov 27 00:12:34 DHCP [581]: already acking lease 192.168.2.14
Nov 27 00:12:35 DHCP [581]: DHCPOFFER on 192.168.2.14 to 00:09:34:0a:ff:08 via br0 (eth0)
Nov 27 00:12:35 DHCP [581]: DHCPREQUEST for 192.168.2.14 from 00:09:34:0a:ff:08 via br0
Nov 27 00:12:35 DHCP [581]: DHCPACK on 192.168.2.14 to 00:09:34:0a:ff:08 via br0 (eth0)
Nov 27 00:12:43 DHCP [581]: DHCPDISCOVER from 00:09:34:0a:ff:08 via br0
Nov 27 00:12:43 DHCP [581]: DHCPDISCOVER from 00:09:34:0a:ff:08 via br0. Requested IP: 0.0.0.0
Nov 27 00:12:44 DHCP [581]: DHCPDISCOVER from 00:09:34:0a:ff:08 via br0
Nov 27 00:12:44 DHCP [581]: DHCPDISCOVER from 00:09:34:0a:ff:08 via br0. Requested IP: 0.0.0.0
Nov 27 00:12:44 DHCP [581]: already acking lease 192.168.2.14
Nov 27 00:12:45 DHCP [581]: DHCPOFFER on 192.168.2.14 to 00:09:34:0a:ff:08 via br0 (eth0)
Nov 27 00:12:45 DHCP [581]: DHCPREQUEST for 192.168.2.14 from 00:09:34:0a:ff:08 via br0
Nov 27 00:12:45 DHCP [581]: DHCPACK on 192.168.2.14 to 00:09:34:0a:ff:08 via br0 (eth0)

reply to andrewhaji
I've been wrestling with this problem for a few months now. I need reliable internet service because I am using the Bell line for work as well. For some reason Bell technicians cannot wrap their minds around the problem, and they cannot understand no matter how many times I tell them that IT IS SIGNIFICANT that you can ping and DNS resolve names. They tell me to reboot computers, they come checking the wires etc.

Have you guys come onto any solution with Bell ? At this point I am debating switching to TekSavvy.

Where do you live? Perhaps this is a localized issue? I'm in the Yonge/Sheppard area of Toronto.

reply to gummysock

FWIW, I used to have Bell Entertainment (also FTTN) service with a CellPipe 7130 modem at this very same location, and it didn't have these problems.

reply to andrewhaji
I have been having similiar problems with my fibe 25 service on the sagecom modem, its been running great since october and now it seems that randomly itll stop working but the modem retains sync and my router shows a connection, haven't tried pining out though, but the web pages will just sit on loading, if i reboot the modem its back just like nothing happened

I've got a personal thread going on the help side of this forum and am hoping that it can be resolved, I am wondering if its a firmware issue or something

edit: it happened again and I tried a tracert and it worked just fine to multiple sites, but the same web site would not load normally

I have the same thing going on. Hopefully they find out what the issue is and fix it. I got my Cellpipe replaced with a Sagecom and it didn't help.

I'll stick it out if they can resolve the issue but if it continues i'll look to go back to regular DSL.

reply to andrewhaji

reply to agreen416

reply to andrewhaji

reply to andrewhaji
i have the same problem since i got the fibe25 installed beginning of this month......when using bit torrent.....

Exact same problem with a buttpipe on fibe 25/7 in North York, starting about a week ago, with outages lasting from 10 minutes to 2 hours, and generally fixable by rebooting the modem. No surfing, but ping/dns resolution/tracert were fine, even soulseek downloads continued to work for a while. No apparent correlation with torrent use or time of day. Went through a few levels of tech support, then they sent a guy out with a Sagem to replace the cellpipe. He took a look at the drop, and replaced a bunch of old cruddy looking wire. Also, he noticed that someone had set my profile to include Fibe TV, which I don't subscribe to, so he fixed that. No idea if that was part of the problem or not. I must say, I was pleased with the attentiveness and thoroughness of all the non-Indian components of the tech support chain.

The tech said this was known as the "sync-no-surf" problem, and that intermittent problems like this were both well-known and difficult to diagnose and get rid of. Maybe it would be helpful to use that phrase when talking to phone support, instead of fogging them out by talking about tracert etc?

Since the replacement yesterday, I haven't experienced the symptoms. Hoping for the best now, but not expecting much.

...and, still getting sync-with-no-surf problems despite new modem and new wire.
what next?

reply to andrewhaji
Experiencing the same here and have been for a while. Sagemcom maintains sync but no surfing or P2P. This is happening with or without Bittorrent running. When it happens I can still open a command window and run successful traceroutes.

I have complained to Bell extensively and had a Supervisor in the Line Test department admit to me that the problem stems from the throttling tech that Bell is using although I have never seen any speed influence on my torrenting and just the disconnects.

End result is that basically everyone in normal Bell support has either told me to go pound salt, hung up on me or told me there is nothing that can be done. I'm currently waiting for a call back from Corporate Bell customer service.

The easiest solution would be to have your account pulled from the general ip pool and put into the Business pool where there is no throttling tech in place. Thus far, everyone I have asked has refused to do so.

reply to andrewhaji
This isn't the first time we have experienced the "synch no surf" issue. Remember the SS5200 issue and the subsequent firmware upgrade mentioned in this FAQ: »Bell Canada Internet FAQ »Where can I obtain updated firmware for the 5200? ? I am not sure it is the same type of problem...as you have the issue with 2 separate devices. It could be on the oslam side or as you mentioned the throttling devices. There are always "side effects" with new firmware...perhaps this is one of them. I have experienced it with my FibeTV but not to the extent that you people seem to have. We have to reboot he Cellpipe to bring back the picture...but sometimes it comes back on its own. Most of the time the channel changing becomes very slow and I have to reboot the PVR (main set top box) to correct that. So this is something that is more widespread and common that thought.
--
My Canada includes Quebec.
Disclaimer: If I express an opinion, it is my own opinion, not that of Bell or its related companies.