O Canada! > Canadian > TekSavvy > [DSL] Cellpipe random reboots / loss of sync (Check logs please?

reply to Roop

Re: [DSL] Cellpipe random reboots / loss of sync (Check logs ple

I think so... The time/date is wrong in the cell pipe and I see no way to set it, nor configure an NTP server.

There is an option to send the cell pipe's syslogs to a syslog server but it doesn't seem to work and everytime the problem happens, the settings I've added like the route to the syslog server get wiped...

I certainly was seeing reboots in the logs like yours, if they are from the exact same instance I think is likely but I can't say 100% given the time/date mismatch.

Yeah the dates are totally bogus... I'm doing the syslog thing and it doesn't catch everything but it does at least help in eliminating the guesswork of when stuff happened. I've also taken to clearing the log and checking it after it does stuff so that I know for sure that anything in the log is since I last cleared it.

I haven't had trouble with it deleting the syslog server settings but then again these things appear to be junk so anything is possible.

I'm glad to hear that it is not just me. Hopefully we can get this sorted out without too much more grief.

I'm still waiting on teksavvy after their latest questions to me. They asked me to leave the modem just plugged into the DSL line but with no PPPoE (either on the modem or on the router) connection active and see if it still rebooted. Of course it did. I think they are now out of things to try in order to eliminate other possible causes and it is just a question of how to talk to Bell about this now. We'll know soon enough.

Thanks again for your testing - I look forward to the results.

interesting test from bell - only the phone line plugged in. i have seen circumstances where malicious traffic can cause devices to reboot, maybe that's what they were guessing.

no email alerts yet with the sagemcom but it's too early to say for sure. if the sagemcom lasts for 48 hours without a connection drop, i'll let TSI know and ask they replace the cellpipe with a sagemcom.

I'm in North Kanata on a 7330 card. Where are you abouts in Ottawa?

I'm downtown in the Glebe on a 7330 (25/7 only became available mid december here - so brand new).

i have not received a WAN down alert email since i did the modem swap yesterday. looking at the router logs, there have been no PPP renegotiations since the swap either. it's a bit early to say for sure if the sagemcom is more stable but so far this is the longest uptime i've had without a WAN down email.

update:
>24 hours without a single reset.

reply to Roop
I think I see where this is going...

So just for kicks I unplugged the phone line from the modem and let it sit for a day. Guess what - yup the modem still reboots itself...

uh... that can only happen if there's some bug in the cellpipe code causing this to occur.

if we're lucky this is due to something in the code. i never tried factory resetting mine. if you factory reset yours does it stabilize?

if we're unlucky this is a bug in the firmware itself and it will reboot in any cofig. given there are people working well with cellpipes, perhaps it's just the 7330 firmware.

-------------

I did a factory reset from the web interface. all that did was enable all the crap i disabled. i figured what the hell, so i just disabled WIFI and left everything else alone.

i'm connected through the cellpipe now. let's see if i get and WAN down emails. the pattern has been a few in 24 hours so we'll see.

sagemcom had none...

Yeah it does look like it is the code and only for the 7330. I've tested everything after a factory reset so that doesn't seem to help.

reply to Phibian
I've passed on the details to teksavvy and requested a plan of action to get us working modems. I'm waiting for a response but don't expect anything until Monday.

i don't recall having this problem right from day one, i seem to recall it started after a period of time.

i had factory reset the cellpipe last night at 9:46pm. i logged into it and only made one single change: disabling wifi. i left everything else alone and PPPoE'd through it. it's been online since without an issue.

things i was changing before:
network IP, it's 192.168.2.1 by default, i changed this
disable HPNA
disable the vlan35/36 thing
disable dhcp configured syslog server
added one static route to get to the syslog server

I've had the problem from day one (Mid December).

I disable wifi and dhcp
Set a new static IP (192.168.2/3.254) 2 for one and 3 for the other modem so that I can easily access the GUIs through the router/firewall.
Set to PPPoE (Internet Only) and don't enter any login.
Set an admin login and password.
No static routes or anything else.
I only started doing the syslog thing when I was trying to figure out the timing since the log times are wrong as you know.

I typically see at least one reboot event within 24 hours but on rare occasions it has made it slightly longer than 24 hours.

None of this should impact anything though. It is not like either of us are setting all sorts for crazy filters on it (which it should be able to handle just fine). We are using it in about the dumbest mode it can run in.

Oh and how did you disable HPNA? I can't seem to find that in the menus.

Honestly if the sagemcom works and I had the option of buying a pair for something resembling a reasonable price I would. I just need this to work.

Still no response from teksavvy. Come Monday I'm turning up the heat on them because this is ridiculous.

I had the same issue with the same firmware. I am using the modem in bridge mode with my WNDR3700 router. I am located in the east end of Ottawa.

This is my disconnection log from the week leading up to the tech visit

Internet disconnected] Sunday, January 08,2012 21:24:04
Internet disconnected Sunday, January 08,2012 16:36:40
Internet disconnected Sunday, January 08,2012 13:19:19
Internet disconnected Sunday, January 08,2012 10:04:27
Internet disconnected Saturday, January 07,2012 04:48:11
Internet disconnected Saturday, January 07,2012 00:34:31
Internet disconnected Thursday, January 05,2012 08:37:55
Internet disconnected Thursday, January 05,2012 03:52:55
Internet disconnected Monday, January 02,2012 07:20:29
Internet disconnected Saturday, December 31,2011 16:51:58
Internet disconnected Saturday, December 31,2011 15:37:49
Internet disconnected Friday, December 30,2011 05:33:55

I pestered teksavvy as my install was still under the one month warranty. They escalated to Bell, and a Bell contractor came out. I explained the issue and showed him the reboot logs that were identical to yours. He had brought along a Bell Cellpipe modem with firmware 1.0.4.3EF-ISAM and I attached that. He got permission from his supervisor to leave that modem at my apt and have me monitor. It has been almost a week and I have not had a single disconnect.

reply to Phibian
here's how to get 2 sagemcoms:

get DSL directly from bell (25/7 is $27 right now)
that's the first sagemcom. tell them you lost it/ate it/set it on fire and pay for another one. do that again and bam. two sagemcoms.

cellpipe is still connected.

hpna is an option somewhere i seem to recall.

reply to Phibian
During a crash, does ping work?

reply to marknotmarc
Thanks for the info. If there is a working firmware then that would be great. I'll talk to teksavvy about that.

reply to Cloneman
Ping to the outside world does not work. I haven't tried a ping to the modem itself.

reply to Phibian
i'm still online with my factory resetted cellpipe. my router's PPPoE logs show no reconnection attempts since I last put the cellpipe back in service.

Phibian, could you try doing the same thing? factory reset your modem and only disable wifi. Don't change it's IP or anything else. I think of all the things I did, changing the IP was the most likely to cause this. perhaps bell/alcatel never tested/QA'd the firmware for different addresses and maybe that's when it runs into a bug.

Will do.