| gary on 18 Dec 2017 13:15:32 -0800 |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
| Re: [PLUG] New Comcast wireless modem with old Buffalo wireless router |
The FiOS folks did something similarly antisocial to me. I've been
running for years with the same router that they gave me when I signed
up, but then they decided they didn't want to support that router model
any more, so they gave me two choices: 1) pay them a ludicrous price
for a refurbished router, or 2) pay them a monthly "maintenance fee" to
keep the current router. Amazingly enough, my email asking what that
fee buys me went unanswered. Naturally, there is no way I could get a
"supported" router from a third party provider. I'd be tempted to try
to start up an ISP utilizing wireless mesh and a fiber backbone, but I
know there would be far too many obstacles.
Gary Duzan
=> Ugh, that XB3 sounds horrible. Glad I moved to Fios. (Until Fios does the
=> same thing.)
=>
=> On Sun, Dec 17, 2017 at 8:28 PM, Rich Mingin (PLUG) <plug@frags.us> wrote:
=>
=>> So a few things;
=>>
=>> The Cocmast XB3 is required because it's part of Cocmast's new IPTV
=>> initiative. It's a fully integrated modem, WAP, and router in one. While
=>> you can disable the customer-facing Wifi, you do not have root on the
=>> device and cannot power off the wifi radios, this is by design. It'll
=>> continue broadcasting the "Xfinity_Free_Wifi" or whatever SSID. On the
=>> other hand, you aren't liable for what happens on that SSID, and it
=>> doesn't
=>> count against your transfer cap nor speed caps (normally). You can't
=>> fully
=>> disable the router part, you *might* be able to forward all ports by
=>> default to your Buffalo, but you will always be double-NATed. Also, any
=>> ports that Cocmast grabs on the XB3 will *not* be forwarded to the
=>> Buffalo,
=>> and you don't have any control over that.
=>>
=>> Sorry for the bad news. Also sorry I don't have any guides to do what
=>> you're trying, but the XB3 rollout was only just starting when I left.
=>> Support might be able to help, but good luck.
=>>
=>> On Sun, Dec 17, 2017 at 8:23 PM, Walt Mankowski <waltman@pobox.com>
=>> wrote:
=>>
=>>> Cool. Hopefully those will be obvious settings once I hook it up?
=>>>
=>>> On Sun, Dec 17, 2017 at 08:18:13PM -0500, Eric Lucas wrote:
=>>> > I always disable the wireless in the (vendor-provided) router.
=>>> > If possible, just configure it to pass-through the external IP to the
=>>> > LAN network interface on the router and then just configure your
=>>> > Buffalo WAN to use that.
=>>> >
=>>> > I've done that for both Comcast and Verizon in years past.
=>>> >
=>>> > Eric
=>>> >
=>>> > On Sun, Dec 17, 2017 at 7:36 PM, Walt Mankowski <waltman@pobox.com>
=>>> wrote:
=>>> >
=>>> > > I've been a Comcast internet customer since 2012. Recently they
=>>> told
=>>> > > me my old modem will longer be supported after January, and a few
=>>> days
=>>> > > ago they sent me a brand new XB3 modem.
=>>> > >
=>>> > > Currently I've got my old modem plugged into a Buffalo WZR-600DHP
=>>> > > AirStation running DD-WRT. I've got a desktop and a laptop plugged
=>>> > > into its RJ-45 ports, and it also handles a bunch of wireless
=>>> devices.
=>>> > >
=>>> > > I'm concerned because this new modem is also a wireless router. If
=>>> I
=>>> > > just replace the old modem with the new one, will everything still
=>>> > > work? Or do I need to consolidate and move all my settings from
=>>> the
=>>> > > Buffalo router onto the Comcast device? Has anyone tried this
=>>> before?
=>>> > > I'm also concerned that if I mess anything up, the old modem will
=>>> have
=>>> > > been deactivated and I won't easily be able to fall back once I
=>>> start.
=>>> > >
=>>> > > Thanks.
=>>> > >
=>>> > > Walt
=>>> > >
=>>> > > ____________________________________________________________
=>>> > > _______________
=>>> > > Philadelphia Linux Users Group --
=>>> > > http://www.phillylinux.org
=>>> > > Announcements - http://lists.phillylinux.org/
=>>> > > mailman/listinfo/plug-announce
=>>> > > General Discussion -- http://lists.phillylinux.org/
=>>> > > mailman/listinfo/plug
=>>> > >
=>>> > >
=>>>
=>>> > ____________________________________________________________
=>>> _______________
=>>> > Philadelphia Linux Users Group --
=>>> http://www.phillylinux.org
=>>> > Announcements - http://lists.phillylinux.org/m
=>>> ailman/listinfo/plug-announce
=>>> > General Discussion -- http://lists.phillylinux.org/
=>>> mailman/listinfo/plug
=>>>
=>>>
=>>> ____________________________________________________________
=>>> _______________
=>>> Philadelphia Linux Users Group --
=>>> http://www.phillylinux.org
=>>> Announcements - http://lists.phillylinux.org/m
=>>> ailman/listinfo/plug-announce
=>>> General Discussion -- http://lists.phillylinux.org/
=>>> mailman/listinfo/plug
=>>>
=>>>
=>>
=>> ____________________________________________________________
=>> _______________
=>> Philadelphia Linux Users Group --
=>> http://www.phillylinux.org
=>> Announcements - http://lists.phillylinux.org/
=>> mailman/listinfo/plug-announce
=>> General Discussion -- http://lists.phillylinux.org/
=>> mailman/listinfo/plug
=>>
=>>
=>
___________________________________________________________________________
=> Philadelphia Linux Users Group --
=> http://www.phillylinux.org
=> Announcements -
=> http://lists.phillylinux.org/mailman/listinfo/plug-announce
=> General Discussion --
=> http://lists.phillylinux.org/mailman/listinfo/plug
=>
___________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug