dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
3
share rss forum feed


TSI Martin
Premium
join:2006-02-23
Chatham, ON
kudos:33
reply to vikingisson

Re: Sagemcom VDSL in bridge mode?

test@test only connects to the BAS. It won't allow anything else then connecting to the BAS.

vikingisson

join:2010-01-22
Mississauga, ON
said by TSI Martin:

test@test only connects to the BAS. It won't allow anything else then connecting to the BAS.

Does it need to be specifically test@test? This needs to be in the docs or mentioned much earlier in the service requests. My unsavvy users and angry boss have lost all faith in me so this is likely my last days with them. All the friends and family I've setup know that my skills are good but they don't pay me.

It's too early to call it fixed but this is where it's at:
factory reset modem. turn off all features such as DHCP, wireless, and make sure the services are only internet and not IPTV. Set the PPPoE to test@test and a random password. Router setup normally.


HiVolt
Premium
join:2000-12-28
Toronto, ON
kudos:21
Reviews:
·TekSavvy DSL
·TekSavvy Cable
said by vikingisson:

Does it need to be specifically test@test?

This is the only way that I know to make the sagemcom not be able to contact bell's management server. It will not update the time (if you reboot it) and it will not update firmware either.

The Cellpipe had a built in bell management login too, but you were actually able to erase it and leave the field blank. In the Sagemcom you can't leave the field blank, it auto-populates the field...
--


vikingisson

join:2010-01-22
Mississauga, ON
said by HiVolt:

said by vikingisson:

Does it need to be specifically test@test?

This is the only way that I know to make the sagemcom not be able to contact bell's management server. It will not update the time (if you reboot it) and it will not update firmware either.

The Cellpipe had a built in bell management login too, but you were actually able to erase it and leave the field blank. In the Sagemcom you can't leave the field blank, it auto-populates the field...

That's exactly what I've discovered with those modems. Thanks for the test@test tip. Usually I'm really peeved at not having a proper clock but if it stops acting like 1980 tech I'll be happy enough.

I know one thing, I'll never buy VDSL again. even knowing the tricks this is subpar technology especially for a business.


HiVolt
Premium
join:2000-12-28
Toronto, ON
kudos:21
Reviews:
·TekSavvy DSL
·TekSavvy Cable
There's nothing wrong with VDSL. It's just that Bell's early implementation of VDSL was on crappy hardware (Lucent Stingers) and requires the use of proprietary modems...

Not sure if by being in MIssissauga you're on an Alcatel 7330 remote, but if you are, you can get yourself a Zyxel modem without all the bullshit of dealing with Bell's proprietary locked down hardware.

vikingisson

join:2010-01-22
Mississauga, ON
My problem isn't so much the technology but the insane way that Bell is using it. It's unacceptable.

This particular issue is about a remote site in Montreal. Just two users but they have been a major pain in the side and soon I'm out of a job because of it. Nope, not touching VDSL until Bell plays nicely. Not for me and not for anyone else since I'll be the one to take the heat.


HiVolt
Premium
join:2000-12-28
Toronto, ON
kudos:21
Reviews:
·TekSavvy DSL
·TekSavvy Cable
said by vikingisson:

My problem isn't so much the technology but the insane way that Bell is using it. It's unacceptable.

This particular issue is about a remote site in Montreal. Just two users but they have been a major pain in the side and soon I'm out of a job because of it. Nope, not touching VDSL until Bell plays nicely. Not for me and not for anyone else since I'll be the one to take the heat.

It's about having control... Rogers just sells/rents all in one routers which are a pain in the ass, and they've been known to push firmware updates that reset the users wireless settings, leaving the wifi wide open.
--


vikingisson

join:2010-01-22
Mississauga, ON
said by HiVolt:

It's about having control... Rogers just sells/rents all in one routers which are a pain in the ass, and they've been known to push firmware updates that reset the users wireless settings, leaving the wifi wide open.

yipes. At least with cable I still have the choice to buy my own modem and whatever router I choose. I'm lucky where I currently have cable modems but I know that isn't always the case.

The customer pays and should be entitled to some control. Not all businesses even small ones are clueless so deserve to control their side of the demarc. I don't have a problem with offering the all in one crap as long as I have the option to do it the right way. That's not happening with VDSL so for now it's off my option list.

If this current issue settles down I'll be happy but I'm afraid it's too late for me to save face.

vikingisson

join:2010-01-22
Mississauga, ON
Well 48 hours uptime ain't bad I suppose. No, actually that sucks.

Nov 16 10:21:31 PPP [581]: Connection terminated.
Nov 16 10:21:32 PPP [581]: Exit.
Nov 16 10:22:26 PPP [581]: ppp1 started
Nov 16 10:22:27 PPP [581]: Connecting: ppp1
Nov 16 10:22:29 PPP [581]: local IP address 10.6.223.173
Nov 16 10:22:29 PPP [581]: remote IP address 10.6.223.1
Nov 16 10:22:30 [290.7]PPPoE Passthrough session opened: server=00:90:1a:a2:43:f9(eth2.35:9959), client=84:1b:5e:df:9a:e1(eth0:2)
Nov 16 10:23:05 [290.7]PPPoE Passthrough session closed: server=00:90:1a:a2:43:f9(eth2.35:4951), client=84:1b:5e:df:9a:e1(eth0:3): Received PADT

vikingisson

join:2010-01-22
Mississauga, ON
Number two for the day. That does it, VDSL will be cancelled. (side note, clock is drifting. This is apparently from the future)

Nov 16 10:56:16 PPP [581]: Connection terminated.
Nov 16 10:56:17 PPP [581]: Exit.
Nov 16 10:57:12 PPP [581]: ppp1 started
Nov 16 10:57:16 PPP [581]: Connecting: ppp1
Nov 16 10:57:18 PPP [581]: local IP address 10.6.223.175
Nov 16 10:57:18 PPP [581]: remote IP address 10.6.223.1
Nov 16 10:57:23 [290.7]PPPoE Passthrough session opened: server=00:90:1a:a2:43:f9(eth2.35:10529), client=84:1b:5e:df:9a:e1(eth0:3)
Nov 16 10:57:46 [290.7]PPPoE Passthrough session closed: server=00:90:1a:a2:43:f9(eth2.35:9959), client=84:1b:5e:df:9a:e1(eth0:2): Received PADT

vikingisson

join:2010-01-22
Mississauga, ON
3 times and it's not even noon yet.

Nov 16 11:48:40 PPP [581]: Connection terminated.
Nov 16 11:48:41 PPP [581]: Exit.
Nov 16 11:49:31 PPP [581]: ppp1 started
Nov 16 11:49:34 PPP [581]: Connecting: ppp1
Nov 16 11:49:37 PPP [581]: local IP address 10.6.223.177
Nov 16 11:49:37 PPP [581]: remote IP address 10.6.223.1
Nov 16 11:49:45 [290.7]PPPoE Passthrough session opened: server=00:90:1a:a2:43:f9(eth2.35:11356), client=84:1b:5e:df:9a:e1(eth0:2)

vikingisson

join:2010-01-22
Mississauga, ON
no sense in posting more logs, it's not going to be stable no matter what now. Quiet late afternoon and a few more reconnects overnight with more happening today. It's up to the boss now but surely the DSL will be dumped.
been through: 512/512, 6, 10/7, modems, routers, cables, line switches, and wasted time.