Just Had DSL Problems, Could My 68U Problem Have Been Related

[jogl]

I just went through 3 days of problems, on the phone with ISP, trying changes on my LAN, etc., and finally found that there was something wrong with the carrier's (Bell) hardware.

Last month I tried all kinds of things to get a 68U working properly and failed, so I took it back to the store and put my old trusty E4200 back into service. When a 2.4G device connected to the 68U, the ADSL connection was dropped. I tried many different firmware revisions / forks, changed all kinds of settings, numerous resets,... nothing worked.

I'm now wondering if problems with the carrier's hardware could have been the cause of my 68U not working properly?

What do you think?

Thanks,
JP.

 

[netwrks]

Is the Bell hardware a modem only, or a router /modem combo? How is your E42oo configured - router mode, Access Point mode?

 

[degrub]

I just went through 3 days of problems, on the phone with ISP, trying changes on my LAN, etc., and finally found that there was something wrong with the carrier's (Bell) hardware.

Last month I tried all kinds of things to get a 68U working properly and failed, so I took it back to the store and put my old trusty E4200 back into service. When a 2.4G device connected to the 68U, the ADSL connection was dropped. I tried many different firmware revisions / forks, changed all kinds of settings, numerous resets,... nothing worked.

I'm now wondering if problems with the carrier's hardware could have been the cause of my 68U not working properly?

What do you think?

Thanks,
JP.

Whatwas replaced on the ATT side ?
Was it their modem at your premises or something on their side of the demarcation. box ?
Frank

 

[jogl]

Something on the carrier (Bell Canada) side was fixed. Not sure if it was faulty hardware or configuration or what. It was not wiring problems (ie,: no ped's under water, etc.), it was something in the local switchhouse or further up line.

E4200 is a wireless router. DSL modem is an old Gnet BB0030. This combination has been very reliable for the last five years or so.

 

[L&LD]

I just went through 3 days of problems, on the phone with ISP, trying changes on my LAN, etc., and finally found that there was something wrong with the carrier's (Bell) hardware.

Last month I tried all kinds of things to get a 68U working properly and failed, so I took it back to the store and put my old trusty E4200 back into service. When a 2.4G device connected to the 68U, the ADSL connection was dropped. I tried many different firmware revisions / forks, changed all kinds of settings, numerous resets,... nothing worked.

I'm now wondering if problems with the carrier's hardware could have been the cause of my 68U not working properly?

What do you think?

Thanks,
JP.

I think it would be worth trying an RT-AC68U (or higher) again.

ISP's routinely do things on the backend that affects users in unknown ways. None of which they will officially admit to.

If your original reasons for trying an RT-AC68U are still valid, time for some leg work again.

Hope this time it exceeds your expectations just like I thought it would when you tried them last.

 

[jogl]

If your original reasons for trying an RT-AC68U are still valid, time for some leg work again.

Hope this time it exceeds your expectations just like I thought it would when you tried them last.

The 68U was beauty, had the features that I wanted, esp. with Merlin's firmware. The 2.4G thing, although not a show stopper, was troubling for a rather expensive gizmo. I will get back to mucking around with routers... probably next fall / winter.

 

[sfx2000]

Something on the carrier (Bell Canada) side was fixed. Not sure if it was faulty hardware or configuration or what. It was not wiring problems (ie,: no ped's under water, etc.), it was something in the local switchhouse or further up line.

E4200 is a wireless router. DSL modem is an old Gnet BB0030. This combination has been very reliable for the last five years or so.

Remember that there was a major Linux security fix that came out last week (glibc) that forces a reboot of the servers once the fix is applied - might be related somehow to your service impact...