The crappy Actiontec F2250 modem/router that Frontier supplied me only supports the 2.4 ghz band and its range is not good enough to cover my whole house. So in order to be able to use a dual band router with better range I bridged the Actiontec and connected it to a Netgear dual band router. Once I did that I got better results on my home network. Then last night my Internet went out. So I called Frontier support to inquire if there is an outage in my area and lo and behold the rep that I talked to said that he could not help me because they do not offer support for bridged devices. I think this is just plain wrong. How do they expect me to be able to use a dual band router which is pretty much becoming essential nowadays? They didn't provide a dual band router yet when I get one myself I lose the ability to get support from them. Anyway I guess it was an outage on their end because the Internet came back on this morning. So does anyone know if Frontier does supply a good dual band router? If so how can I get one? Can I call them to request a better router? If so, who to call, tech support or an account rep? Or am I just shit out of luck? If I keep my present setup then I guess I am not eligible for the technical support I pay for. I wish there was another broadband ISP in my area but there is only a fixed wireless ISP that offers even slower speeds than Frontier offers. Thanks.

The HIGH setting within this router indicates that IMAP and POP3 are OK when internal firewall is set to HIGH. However, after considerable troubleshooting it has come down to the HIGH setting not receiving for POP3 clients. Send is OK, IMAP is OK both send and receive. Simply changing the firewall to LOW or OFF allows the POP3 emails to be received. Several client systems (IOS, WinXP, Win7, Linux) and several email programs all have this same failure and it doesn't make any difference who the isp is. To me this seems like a firmware problem within the router. Any opinions/help? Mike Cebula

So it seems like channel 7/507 (CBS - KIRO) has been completely removed from the programming guide in the Seattle area about a month ago. This would seem to indicate that things are not going well with the Cox negotiations. When Frontier had a similar dispute with Sinclair a year and a half ago, they gave us free HBO while it took 2+ months to negotiate with Sinclair. This time around Frontier doesn't seem interested in doing anything for their customers that have lost access to CBS. At this point I'm needing to pay $10 a month for a CBS all-access pass to fill in the gap. This may be the last straw for me with Frontier. Is anyone else getting frustrated?

I use the native Pandora iOS app on my iPad every day while I work, iPad mounted to my desk with a magnetic disc on the back. I've used it this way every day for the last several months without any issues. Roughly 3 days ago, I noticed that my iPad would claim "Cannot connect to Pandora. Please check your network connection and try again." for no reason. Reboots, reconfiguring networks, etc. all results in the same message. I connect my iPad to my phone's hotspot while driving and it works instantly there. I did the same in my office connecting it to my phone's hotspot and it works as expected. No errors. I have my own WiFi router behind the Frontier router, to isolate my LAN from their annoying DNS hijacking. I enabled the wireless network on _their_ router, and connected my iPad to it, same error message. Their router plugs directly into the incoming cable from the street, so nothing on my end is between it, and their upstream network access point. I reset the network settings on my iPad, recreated the network connections to all networks, same error. But it still continues to work when the iPad is connected my phone's hotspot, every single time. I tried uninstalling the Pandora app from my iPad as recommended by Applel and reinstalled it. Same error. I hard-reset my iPad, set up the iPad as a fresh, clean iPad and installed the Pandora app. Same error. I tried changing the DNS settings on the iPad side to point to Google's DNS, Cloudflare's secure DNS, my own DNS, Frontier's DNS on the router, Frontier's upstream DNS, and other public DNS servers. All resulted in the same exact error. The native Pandora app on my Android phone, continues to work fine when connected to the same wireless routers that the iPad Pandora app fails on. It works every time on Android. It may be falling back to my data connection though, even under Airplane Mode. Pandora running in a desktop browser works fine on all machines (Mac, Win, Linux), no issues at all. The _only_ place this is no longer working, is the native app running directly on the iPad itself. The last thing I'm going to test, is connecting the iPad through a proxy I run here on my LAN, so I can look at the logs and see which service endpoint Frontier is blocking when the app launches. This is 100% on their end, because nothing at all has changed on my devices, Pandora version is the same as it has been for weeks prior, and my networking equipment hasn't changed at all, and it continues to fail when connected directly through their router. Has anyone else ever seen this before, and what did you do to resolve it? I'm hoping this isn't more of their anti-Net Neutrality over-reach. Their DNS hijacking is already causing no end of pain for me on my LAN and lab testing at the home office. Thanks in advance!

Hey Everyone, I am downgrading my tripple play due to increasing costs. Ive already placed my downgrade order subtracting the phone out of the picture. Has anyone ported out before the double play takes affect and does it cause entire account to be cancelled or will i be fine? Thanks

I have a family member moving and therefore ending frontier service but uses their frontiernet e-mail for everything. Does frontier offer any sort of solution to keep the e-mail address or is there any grace period after canceling? I assume not (why would they serve a non-cusomter) but wanted to check if anyone knew of any solution.

Frontier and Nokia partner up to deliver 10-gigabit speeds in the U.S. https://www.neowin.net/news/frontier-and-nokia-partner-up-to-deliver-10-gigabit-speeds-in-the-us The technology will allow Frontier to offer speeds of up to 10Gb/s, starting with customers in the Dallas and Fort Worth areas of Texas. From there, the service will expand to the rest of the state, as well as Florida and California. In Nokia's announcement, the company states the Frontier will be able to deploy the new service speeds to its customers using its existent fiver network.

We were with Frontier FiOS initially. My dad cancelled the home phone service thinking it's not needed, but my grandpa stopped calling him because he thinks international calls to mobile costs more than landline (it doesn't). So he tried to reactivate the home phone service, but the Frontier reps told him that there will be a $50 fee or something. He ended up cancelling Frontier and got Spectrum instead. I think we're paying $45 for 100/15 internet and $25 for the home phone right now. I noticed Frontier has a 100/100mbps internet plan for $40 for 24 months, but installation ($75) and activation fees are not included. Is it possible to do a self-install and get our own router so we don't have to pay $10/month? We would get Internet only for Frontier. We had frontier FiOS up until a few months ago so everything in the ONT should still be working. I don't know if we still qualify as a new customer, the services have been cancelled but we have a bill we didn't pay off yet. Any ideas? Should I take the deal, or is it too much hassle to try to switch again?

My contract ends in August. I am moving to NV sometime Nov-Feb. I would want to keep all 3 services but drop a STB and some movie channels. What are my options?

Wondering if this is a concern, and if so, any thoughts on if/when a firmware update will be available? And on the subject, how does one obtain a firmware update or are they automagically rolled out by Frontier?

I'm almost afraid to post this in case it's a weird mistake on my node, but is anyone else in the DFW area suddenly getting gigabit download speeds on FIOS? I am a 150/150 subscriber and I've reached out to a couple friends that are also Frontier in the area and they aren't seeing it. The only notable difference is I have Quantum and they don't, but I'm not sure that would have any effect on Internet at all. I kind of wondered if they were just testing something around here, but it's been going on at least 3 days, and that's just since I've noticed.

Does anyone know if you can bridge a frontier modem (or offbrand modem) to use pppoe? Right now its on dhcp..

Server stopped responding to e-mail client and test requests (used multiple online tools to verify) around 5:30pm, PDT. E-mail was coming into Seamonkey mail (Thunderbird) just fine 15 minutes prior to that time. Weird thing is that e-mail appears to be arriving fine into the Yahoo webmail interface--there must be a different server repository, and that server makes a hand-off (or something) to pop3.frontier.com. At any rate, anyone else experiencing problems at this time? Misery loves company, y'know :huh: -- -- KingCheetah

I've been asked to post here about a short meeting with a Frontier tech who was hanging some cable in front of my house. There were two trucks and they were unspooling and hanging some moderately large cable going down the street. When I asked him what they were putting in he said we would have "Fiber To The Home" soon! I thought that sounded pretty nice! I'm on Comcast now but fiber would be a big draw for me. Here is a pic of the loop on the pole outside my house. The gray box is the Comcast cable, the loop below that is the new Frontier cable.

The last 3-4 days been required to dial area code for local calls. Never had to do this before. Any answers?

The internet giant's password system sends users a two-factor code when they initiate a reset, but ZDNet reports that the system lets you enter as many codes as you want, opening up users' accounts to a breach. Spotted by security researcher Ryan Stevenson, the bug means a determined attacker with some time on their hands could get into an account with just a username or an email address.quote: "Out of an abundance of caution while the matter is being investigated, Frontier has shut down the functionality of changing a customer's password via the web," a company spokesperson said.Source: https://www.engadget.com/2018/06/08/frontier-communications-password-bug-account-breach/

We got a new FIOS router today and I'm struggling to replicate some of the port forwarding rules I had on my old Actiontec to allow remote viewing of my security cameras. Can anyone point me to a good primer on setting up both UDP and TCP porting, add does anyone know if the newer routers prevent port forwarding on port 80?

Hello all, New user to frontier communications fios service. Very glad to have some competition in my southern california area and have been impressed. So far, the service has been very good, with faster speeds compared to my spectrum internet service. The issue i do have are the random disconnects, happens through out the day. My equipment is a frontier supplied ONT (hope that is right) and a third party router, a tp-link archer c8, dual band router. Not sure if the line was provisioned for ethernet, does that makes a difference? and if yes, confirm with call to customer service? lastest test results:

I have bonded DSL. A couple weeks ago, my DSL Line 1 went completely out. Frontier came out, replaced the modem and repatched the lines on their side. From there I've been back to a solid connection at 13953 Down / 1206 Up (I have a 12/1 subscription). However, since then, I've been getting intermittent disconnects even though both DSL lines show a solid connection at the speed mentioned above. Frontier hasn't been able to find the problem yet. So, I was just wondering if anyone here might be able to give some pointers if you have experience for this. My log is below (IP addresses have been changed for security reasons). P0000-00-00T00:00:53 L3 sdb[1097]: ELAN: Port lan-3 is UP. (eth3) speed 100 duplex full P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[system.uptime] val[00:00:00:54] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[system.last-reboot-reason] val[Reboot command: WEBUI] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.up-rate] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.up-snr-margin] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.up-attenuation] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.up-attainable-rate] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.down-rate] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.down-snr-margin] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.down-attenuation] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.down-attainable-rate] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.showtime-start] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.last-showtime-start] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.total.retrain-count] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.total.errored-secs] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.total.atuc-errored-secs] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.total.severely-errored-secs] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.total.atuc-severely-errored-secs] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.up-rate] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.up-snr-margin] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.up-attenuation] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.up-attainable-rate] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.down-rate] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.down-snr-margin] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.down-attenuation] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.down-attainable-rate] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.showtime-start] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.last-showtime-start] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.total.retrain-count] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.total.errored-secs] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.total.atuc-errored-secs] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.total.severely-errored-secs] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.total.atuc-severely-errored-secs] val[0] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].rx-bytes] val[] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].rx-packets] val[] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].tx-bytes] val[] P0000-00-00T00:00:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].tx-packets] val[] P0000-00-00T00:00:54 L3 dslstarth[1807]: DSL: Subsystem is set to bonding. P0000-00-00T00:00:54 L3 dslstarth[1807]: DSL: Start line 1 P0000-00-00T00:00:54 L3 dslstarth[1807]: DSL: Start line 2 P0000-00-00T00:01:18 L3 sdb[1097]: DSL: line-1: Mode ADSL2+ (ATM) P0000-00-00T00:01:18 L3 sdb[1097]: DSL: line-1: Sync Rate in kbps D/S 6976 U/S 603 P0000-00-00T00:01:18 L3 sdb[1097]: DSL: line-1: Latency path Fast P0000-00-00T00:01:18 L3 sdb[1097]: DSL: line-1: Trellis D/S:ON U/S:ON P0000-00-00T00:01:18 L3 sdb[1097]: DSL: line-1: CO Vendor b5004946544e71c5 P0000-00-00T00:01:18 L3 sdb[1097]: DSL: line-1: Link showtime counter since boot 1 P0000-00-00T00:01:18 L3 sdb[1097]: DSL: line-1: Retrain Reason System Startup P0000-00-00T00:01:18 L3 sdb[1097]: DSL: line-2: Mode ADSL2+ (ATM) P0000-00-00T00:01:18 L3 sdb[1097]: DSL: line-2: Sync Rate in kbps D/S 6976 U/S 603 P0000-00-00T00:01:18 L3 sdb[1097]: DSL: line-2: Latency path Fast P0000-00-00T00:01:18 L3 sdb[1097]: DSL: line-2: Trellis D/S:ON U/S:ON P0000-00-00T00:01:18 L3 sdb[1097]: DSL: line-2: CO Vendor b5004946544e71c5 P0000-00-00T00:01:18 L3 sdb[1097]: DSL: line-2: Link showtime counter since boot 1 P0000-00-00T00:01:18 L3 sdb[1097]: DSL: line-2: Retrain Reason System Startup P0000-00-00T00:01:22 L3 sdb[1097]: DSL: Turn off DSL status alarm handler for ATM/ATM BOND P0000-00-00T00:01:22 L3 sdb[1097]: DSL: Turn off DSL crcvc alarm handler for ATM/ATM BOND P0000-00-00T00:03:28 L3 sdb[1097]: DSL: Autosense: Process event BONDED_LINE_ATM. P0000-00-00T00:03:43 L3 sdb[1097]: ATM: VC 1, vpi=0, vci=35 QoS No P0000-00-00T00:03:44 L3 sdb[1097]: ATM: VC vpi=0 vci=35 vc-1 atm0 P0000-00-00T00:03:49 L5 cwmp[2841]: DSLF_WanMgmtChg path[system.uptime] val[00:00:03:50] P0000-00-00T00:03:49 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.up-rate] val[603] P0000-00-00T00:03:49 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.up-snr-margin] val[ 292] P0000-00-00T00:03:49 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.up-attenuation] val[ 160] P0000-00-00T00:03:49 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.up-attainable-rate] val[1360] P0000-00-00T00:03:49 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.down-rate] val[6976] P0000-00-00T00:03:49 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.down-snr-margin] val[ 206] P0000-00-00T00:03:49 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.down-attenuation] val[ 345] P0000-00-00T00:03:49 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.down-attainable-rate] val[12584] P0000-00-00T00:03:49 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.showtime-start] val[150] P0000-00-00T00:03:49 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.last-showtime-start] val[151] P0000-00-00T00:03:49 L5 pppd[3793]: pppd 2.4.6 started by root, uid 0 P0000-00-00T00:03:49 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.up-rate] val[603] P0000-00-00T00:03:49 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.up-snr-margin] val[ 210] P0000-00-00T00:03:49 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.up-attenuation] val[ 164] P0000-00-00T00:03:50 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.up-attainable-rate] val[1272] P0000-00-00T00:03:50 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.down-rate] val[6976] P0000-00-00T00:03:50 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.down-snr-margin] val[ 101] P0000-00-00T00:03:50 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.down-attenuation] val[ 385] P0000-00-00T00:03:50 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.down-attainable-rate] val[8716] P0000-00-00T00:03:50 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.showtime-start] val[150] P0000-00-00T00:03:50 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.last-showtime-start] val[151] P0000-00-00T00:03:50 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.total.errored-secs] val[42] P0000-00-00T00:03:50 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.total.severely-errored-secs] val[4] P0000-00-00T00:03:52 L4 pppd[3793]: Connected to 00:31:46:6b:c3:f7 via interface br2 P0000-00-00T00:03:52 L5 pppd[3793]: Connect: ppp2 br2 P0000-00-00T00:03:52 L5 pppd[3793]: PAP authentication succeeded P0000-00-00T00:03:52 L5 pppd[3793]: peer from calling number 00:31:46:6B:C3:F7 authorized P0000-00-00T00:03:52 L5 pppd[3793]: local IP address 182.16.223.81 P0000-00-00T00:03:52 L5 pppd[3793]: remote IP address 74.42.128.121 P0000-00-00T00:03:52 L5 pppd[3793]: primary DNS address 74.40.74.40 P0000-00-00T00:03:52 L5 pppd[3793]: secondary DNS address 74.40.74.41 P0000-00-00T00:03:53 L5 sdb[1097]: route[1]: forcing onlink route for nexthop (74.42.128.121) P0000-00-00T00:03:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[system.uptime] val[00:00:03:53] P0000-00-00T00:03:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.up-snr-margin] val[ 290] P0000-00-00T00:03:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.showtime-start] val[152] P0000-00-00T00:03:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.last-showtime-start] val[154] P0000-00-00T00:03:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.up-snr-margin] val[ 230] P0000-00-00T00:03:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.down-snr-margin] val[ 173] P0000-00-00T00:03:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.down-attainable-rate] val[11396] P0000-00-00T00:03:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.showtime-start] val[152] P0000-00-00T00:03:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.last-showtime-start] val[154] P0000-00-00T00:03:53 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].ipaddr] val[182.16.223.81] P0000-00-00T00:03:53 L3 cwmp[2841]: DSLF_WANIPChgProc 2 P0000-00-00T00:03:53 L3 sdb[1097]: mcp_send_msg: send error! P0000-00-00T00:03:54 L5 mcp[4111]: mcp: kernel's mcfwd_upstream_if is 26 (ppp2) 2018-06-09T06:50:29-04:00 L3 sdb[1097]: IGMP Proxy not responding...Restarting now! 2018-06-09T06:50:29-04:00 L4 mcp[4111]: mcp: processing STOP signal 2018-06-09T06:50:29-04:00 L4 mcp[4111]: mcp: MRT_DEL_MFC error sock=4 src=0x00000000 grp=0xEFFFFFFA if= - No such file or directory 2018-06-09T06:50:30-04:00 L5 ntph[4191]: Update system date & time from NTP server 74.40.74.60 2018-06-09T06:50:30-04:00 L5 ntph[4191]: NTP: waiting for 86400 secs... 2018-06-09T06:50:31-04:00 L5 mcp[4208]: mcp: kernel's mcfwd_upstream_if is 26 (ppp2) 2018-06-09T06:50:34-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[system.uptime] val[00:00:04:03] 2018-06-09T06:50:34-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.up-snr-margin] val[ 291] 2018-06-09T06:50:34-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.down-attainable-rate] val[12600] 2018-06-09T06:50:34-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.showtime-start] val[162] 2018-06-09T06:50:34-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.last-showtime-start] val[164] 2018-06-09T06:50:34-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.up-snr-margin] val[ 269] 2018-06-09T06:50:34-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.up-attainable-rate] val[1260] 2018-06-09T06:50:34-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.down-attainable-rate] val[11400] 2018-06-09T06:50:34-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.showtime-start] val[162] 2018-06-09T06:50:34-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.last-showtime-start] val[164] 2018-06-09T06:50:34-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].rx-bytes] val[55451] 2018-06-09T06:50:34-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].rx-packets] val[78] 2018-06-09T06:50:34-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].tx-bytes] val[35716] 2018-06-09T06:50:34-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].tx-packets] val[104] 2018-06-09T06:50:34-04:00 L5 cwmp[2841]: next Periodic Inform after 29293 s 2018-06-09T06:50:34-04:00 L4 cwmp[2841]: Resolving ACS URL - Retry 0 2018-06-09T06:50:34-04:00 L5 cwmp[2841]: Connect to https://secure.acs.frontier.com [216.52.29.165] Retry 0 2018-06-09T06:50:35-04:00 L3 sdb[1097]: DSL: Autosense: Duplicate event BONDED_LINE_ATM. Event not ignored. 2018-06-09T06:50:35-04:00 L3 sdb[1097]: DSL: Autosense: Process event BONDED_LINE_ATM. 2018-06-09T06:50:35-04:00 L3 sdb[1097]: DSL: line-2: Mode ADSL2+ (ATM) 2018-06-09T06:50:35-04:00 L3 sdb[1097]: DSL: line-2: Sync Rate in kbps D/S 6976 U/S 603 2018-06-09T06:50:35-04:00 L3 sdb[1097]: DSL: line-2: Latency path Fast 2018-06-09T06:50:35-04:00 L3 sdb[1097]: DSL: line-2: Trellis D/S:ON U/S:ON 2018-06-09T06:50:35-04:00 L3 sdb[1097]: DSL: line-2: CO Vendor b5004946544e71c5 2018-06-09T06:50:35-04:00 L3 sdb[1097]: DSL: line-2: Link showtime counter since boot 2 2018-06-09T06:50:35-04:00 L3 sdb[1097]: DSL: line-2: Retrain Reason System Startup 2018-06-09T06:50:35-04:00 L3 sdb[1097]: ELAN: Port lan-3 is UP. (eth3) speed 100 duplex full 2018-06-09T06:50:35-04:00 L3 sdb[1097]: ELAN: Port lan-2 is UP. (eth2) speed 100 duplex full 2018-06-09T06:50:36-04:00 L5 cwmp[2841]: (SSL) Connect Success: secure.acs.frontier.com 2018-06-09T06:50:36-04:00 L5 cwmp[2841]: (SSL) Certificate Verify Success: secure.acs.frontier.com 2018-06-09T06:50:44-04:00 L5 cwmp[2841]: Post Inform - reason 1 BOOT 4 VALUE CHANGE 2018-06-09T06:50:45-04:00 L5 cwmp[2841]: Server auth challenge received 2018-06-09T06:50:45-04:00 L5 cwmp[2841]: Receive InformResponse 2018-06-09T06:50:45-04:00 L5 cwmp[2841]: Post 0 2018-06-09T06:50:45-04:00 L5 cwmp[2841]: Receive GetParameterNames 2018-06-09T06:50:45-04:00 L5 cwmp[2841]: Post GetParameterNamesResponse 2018-06-09T06:50:46-04:00 L5 cwmp[2841]: Receive GetParameterNames 2018-06-09T06:50:46-04:00 L5 cwmp[2841]: Post GetParameterNamesResponse 2018-06-09T06:50:46-04:00 L5 cwmp[2841]: Receive GetParameterNames 2018-06-09T06:50:46-04:00 L5 cwmp[2841]: Post GetParameterNamesResponse 2018-06-09T06:50:46-04:00 L5 cwmp[2841]: Receive GetParameterNames 2018-06-09T06:50:46-04:00 L5 cwmp[2841]: Post GetParameterNamesResponse 2018-06-09T06:50:46-04:00 L5 cwmp[2841]: Receive GetParameterNames 2018-06-09T06:50:46-04:00 L5 cwmp[2841]: Post GetParameterNamesResponse 2018-06-09T06:50:47-04:00 L5 cwmp[2841]: Receive GetParameterValues 2018-06-09T06:50:47-04:00 L5 cwmp[2841]: Post GetParameterValuesResponse (chunk-length - 5509) 2018-06-09T06:50:47-04:00 L5 cwmp[2841]: Continue GetParameterValuesResponse (chunk-length - 0) 2018-06-09T06:50:47-04:00 L5 cwmp[2841]: Receive GetParameterValues 2018-06-09T06:50:47-04:00 L5 cwmp[2841]: Post GetParameterValuesResponse (chunk-length - 5328) 2018-06-09T06:50:47-04:00 L5 cwmp[2841]: Continue GetParameterValuesResponse (chunk-length - 0) 2018-06-09T06:50:47-04:00 L5 cwmp[2841]: Receive GetParameterValues 2018-06-09T06:50:47-04:00 L5 cwmp[2841]: Post GetParameterValuesResponse (chunk-length - 2124) 2018-06-09T06:50:47-04:00 L5 cwmp[2841]: Continue GetParameterValuesResponse (chunk-length - 0) 2018-06-09T06:50:48-04:00 L5 cwmp[2841]: Closing connection on HTTP 204 2018-06-09T06:50:48-04:00 L5 cwmp[2841]: (SSL) Closing Connection: secure.acs.frontier.com 2018-06-09T06:50:50-04:00 L3 sdb[1097]: ATM: VC 1, vpi=0, vci=35 QoS No 2018-06-09T06:50:51-04:00 L3 sdb[1097]: ATM: VC vpi=0 vci=35 vc-1 atm0 2018-06-09T06:50:51-04:00 L3 sdb[1097]: Speedtest: Fail to find queue 2018-06-09T06:51:11-04:00 L3 dnsmasq[2898]: no responses from nameserver '74.40.74.40' 2018-06-09T06:51:12-04:00 L3 dnsmasq[2898]: no responses from nameserver '74.40.74.41' 2018-06-09T06:51:47-04:00 L4 mcp[4208]: mcp[handle_igmpv2_leave_msg]: missing expected data rep=0xC0A80174 grp=0xE00000FB 2018-06-09T06:52:53-04:00 L5 pppd[3793]: Serial link appears to be disconnected. 2018-06-09T06:52:59-04:00 L5 pppd[3793]: Connection terminated. 2018-06-09T06:52:59-04:00 L5 pppd[3793]: Modem hangup 2018-06-09T06:52:59-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[system.uptime] val[00:00:06:29] 2018-06-09T06:52:59-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.up-snr-margin] val[ 290] 2018-06-09T06:52:59-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.up-attainable-rate] val[1356] 2018-06-09T06:52:59-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.down-snr-margin] val[ 207] 2018-06-09T06:52:59-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.down-attainable-rate] val[12616] 2018-06-09T06:52:59-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.showtime-start] val[308] 2018-06-09T06:52:59-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.last-showtime-start] val[310] 2018-06-09T06:52:59-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.up-snr-margin] val[ 268] 2018-06-09T06:52:59-04:00 L4 mcp[4208]: mcp: processing STOP signal 2018-06-09T06:52:59-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.up-attainable-rate] val[1308] 2018-06-09T06:52:59-04:00 L4 mcp[4208]: mcp: MRT_DEL_MFC error sock=4 src=0x00000000 grp=0xEFFFFFFA if= - No such file or directory 2018-06-09T06:52:59-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.down-snr-margin] val[ 181] 2018-06-09T06:52:59-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.down-attainable-rate] val[11736] 2018-06-09T06:52:59-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.showtime-start] val[308] 2018-06-09T06:52:59-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.last-showtime-start] val[310] 2018-06-09T06:52:59-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.total.errored-secs] val[43] 2018-06-09T06:52:59-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].rx-bytes] val[] 2018-06-09T06:52:59-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].rx-packets] val[] 2018-06-09T06:52:59-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].tx-bytes] val[] 2018-06-09T06:52:59-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].tx-packets] val[] 2018-06-09T06:53:19-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[system.uptime] val[00:00:06:49] 2018-06-09T06:53:19-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.up-attainable-rate] val[1360] 2018-06-09T06:53:19-04:00 L5 pppd[4856]: pppd 2.4.6 started by root, uid 0 2018-06-09T06:53:19-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.down-attainable-rate] val[12604] 2018-06-09T06:53:19-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.showtime-start] val[328] 2018-06-09T06:53:19-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.last-showtime-start] val[330] 2018-06-09T06:53:19-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.up-snr-margin] val[ 265] 2018-06-09T06:53:19-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.up-attainable-rate] val[1304] 2018-06-09T06:53:19-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.down-snr-margin] val[ 182] 2018-06-09T06:53:19-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.down-attainable-rate] val[11756] 2018-06-09T06:53:19-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.showtime-start] val[328] 2018-06-09T06:53:19-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.last-showtime-start] val[330] 2018-06-09T06:53:19-04:00 L4 pppd[4856]: Connected to 00:31:46:6b:c3:f7 via interface br2 2018-06-09T06:53:19-04:00 L5 pppd[4856]: Connect: ppp2 br2 2018-06-09T06:53:19-04:00 L5 pppd[4856]: PAP authentication succeeded 2018-06-09T06:53:19-04:00 L5 pppd[4856]: peer from calling number 00:31:46:6B:C3:F7 authorized 2018-06-09T06:53:19-04:00 L5 pppd[4856]: local IP address 182.16.223.81 2018-06-09T06:53:19-04:00 L5 pppd[4856]: remote IP address 74.42.128.121 2018-06-09T06:53:19-04:00 L5 pppd[4856]: primary DNS address 74.40.74.40 2018-06-09T06:53:19-04:00 L5 pppd[4856]: secondary DNS address 74.40.74.41 2018-06-09T06:53:19-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].ipaddr] val[182.16.223.81] 2018-06-09T06:53:20-04:00 L5 sdb[1097]: route[1]: forcing onlink route for nexthop (74.42.128.121) 2018-06-09T06:53:20-04:00 L3 cwmp[2841]: DSLF_WANIPChgProc 2 2018-06-09T06:53:20-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].rx-bytes] val[54] 2018-06-09T06:53:20-04:00 L4 cwmp[2841]: Resolving ACS URL - Retry 0 2018-06-09T06:53:20-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].rx-packets] val[3] 2018-06-09T06:53:20-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].tx-bytes] val[54] 2018-06-09T06:53:20-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].tx-packets] val[5] 2018-06-09T06:53:20-04:00 L5 cwmp[2841]: Connect to https://secure.acs.frontier.com [216.52.29.165] Retry 0 2018-06-09T06:53:21-04:00 L5 mcp[4943]: mcp: kernel's mcfwd_upstream_if is 28 (ppp2) 2018-06-09T06:53:21-04:00 L5 cwmp[2841]: (SSL) Connect Success: secure.acs.frontier.com 2018-06-09T06:53:21-04:00 L5 cwmp[2841]: (SSL) Certificate Verify Success: secure.acs.frontier.com 2018-06-09T06:53:32-04:00 L5 cwmp[2841]: Post Inform - reason 4 VALUE CHANGE 2018-06-09T06:53:32-04:00 L5 cwmp[2841]: Receive InformResponse 2018-06-09T06:53:32-04:00 L5 cwmp[2841]: Post 0 2018-06-09T06:53:32-04:00 L5 cwmp[2841]: Receive GetParameterValues 2018-06-09T06:53:32-04:00 L5 cwmp[2841]: Post GetParameterValuesResponse (chunk-length - 3978) 2018-06-09T06:53:32-04:00 L5 cwmp[2841]: Continue GetParameterValuesResponse (chunk-length - 0) 2018-06-09T06:53:33-04:00 L5 cwmp[2841]: Closing connection on HTTP 204 2018-06-09T06:53:33-04:00 L5 cwmp[2841]: (SSL) Closing Connection: secure.acs.frontier.com 2018-06-09T06:53:50-04:00 L3 sdb[1097]: Wi-Fi: Client 88:b4:a6:7c:e8:3a associated with C3P0 2018-06-09T06:53:50-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 5GHz radio 1 2018-06-09T07:21:46-04:00 L3 sdb[1097]: Wi-Fi: Client 8c:25:05:40:8a:1c associated with C3P0 2018-06-09T07:21:46-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 1 2018-06-09T07:26:45-04:00 L3 sdb[1097]: Wi-Fi: Client 8c:25:05:40:8a:1c left C3P0 2018-06-09T07:26:45-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 0 2018-06-09T07:26:45-04:00 L3 sdb[1097]: Wi-Fi: Client 8c:25:05:40:8a:1c associated with C3P0 2018-06-09T07:26:45-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 5GHz radio 2 2018-06-09T07:34:25-04:00 L3 sdb[1097]: Wi-Fi: Client 8c:25:05:40:8a:1c left C3P0 2018-06-09T07:34:25-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 5GHz radio 1 2018-06-09T07:44:06-04:00 L3 sdb[1097]: Wi-Fi: 8c:25:05:40:8a:1c re-joined C3P0 after 0 days 0 hours 17 minutes 21 seconds 2018-06-09T07:44:06-04:00 L3 sdb[1097]: Wi-Fi: Client 8c:25:05:40:8a:1c associated with C3P0 2018-06-09T07:44:06-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 5GHz radio 2 2018-06-09T07:46:14-04:00 L3 sdb[1097]: Wi-Fi: Client 88:b4:a6:7c:e8:3a left C3P0 2018-06-09T07:46:14-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 5GHz radio 1 2018-06-09T07:50:13-04:00 L3 sdb[1097]: Wi-Fi: Client 6c:fd:b9:67:53:94 associated with C3P0 2018-06-09T07:50:13-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 1 2018-06-09T07:51:22-04:00 L3 sdb[1097]: Wi-Fi: Client 8c:25:05:40:8a:1c left C3P0 2018-06-09T07:51:22-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 5GHz radio 0 2018-06-09T07:51:22-04:00 L3 sdb[1097]: Wi-Fi: 8c:25:05:40:8a:1c re-joined C3P0 after 0 days 0 hours 29 minutes 36 seconds 2018-06-09T07:51:22-04:00 L3 sdb[1097]: Wi-Fi: Client 8c:25:05:40:8a:1c associated with C3P0 2018-06-09T07:51:22-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 2 2018-06-09T07:51:30-04:00 L3 sdb[1097]: Wi-Fi: Client 8c:25:05:40:8a:1c left C3P0 2018-06-09T07:51:30-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 1 2018-06-09T07:51:47-04:00 L3 sdb[1097]: Wi-Fi: 6c:fd:b9:67:53:94 re-joined C3P0 after 0 days 0 hours 1 minutes 34 seconds 2018-06-09T07:51:47-04:00 L3 sdb[1097]: Wi-Fi: Client 6c:fd:b9:67:53:94 associated with C3P0 2018-06-09T07:51:47-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 1 2018-06-09T08:08:55-04:00 L3 sdb[1097]: Wi-Fi: Client 6c:fd:b9:67:53:94 left C3P0 2018-06-09T08:08:55-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 0 2018-06-09T09:14:13-04:00 L3 sdb[1097]: Wi-Fi: 88:b4:a6:7c:e8:3a re-joined C3P0 after 0 days 2 hours 20 minutes 23 seconds 2018-06-09T09:14:13-04:00 L3 sdb[1097]: Wi-Fi: Client 88:b4:a6:7c:e8:3a associated with C3P0 2018-06-09T09:14:13-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 5GHz radio 1 2018-06-09T09:16:49-04:00 L3 sdb[1097]: Wi-Fi: Client 88:b4:a6:7c:e8:3a left C3P0 2018-06-09T09:16:49-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 5GHz radio 0 2018-06-09T11:43:48-04:00 L3 sdb[1097]: Wi-Fi: 88:b4:a6:7c:e8:3a re-joined C3P0 after 0 days 4 hours 49 minutes 58 seconds 2018-06-09T11:43:48-04:00 L3 sdb[1097]: Wi-Fi: Client 88:b4:a6:7c:e8:3a associated with C3P0 2018-06-09T11:43:48-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 5GHz radio 1 2018-06-09T11:58:12-04:00 L3 sdb[1097]: Wi-Fi: Client f0:6e:0b:0c:f3:2e associated with C3P0 2018-06-09T11:58:12-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 5GHz radio 2 2018-06-09T11:58:14-04:00 L3 sdb[1097]: Wi-Fi: 6c:fd:b9:67:53:94 re-joined C3P0 after 0 days 4 hours 8 minutes 1 seconds 2018-06-09T11:58:14-04:00 L3 sdb[1097]: Wi-Fi: Client 6c:fd:b9:67:53:94 associated with C3P0 2018-06-09T11:58:14-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 1 2018-06-09T12:03:17-04:00 L3 dnsmasq[2898]: no responses from nameserver '74.40.74.41' 2018-06-09T12:10:45-04:00 L3 dnsmasq[2898]: nameserver '74.40.74.41' is now responding 2018-06-09T12:20:19-04:00 L3 dnsmasq[2898]: no responses from nameserver '74.40.74.40' 2018-06-09T12:31:40-04:00 L3 sdb[1097]: Wi-Fi: Client 88:b4:a6:7c:e8:3a left C3P0 2018-06-09T12:31:40-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 5GHz radio 1 2018-06-09T12:33:36-04:00 L3 dnsmasq[2898]: nameserver '74.40.74.40' is now responding 2018-06-09T13:16:57-04:00 L3 sdb[1097]: Wi-Fi: Client 00:19:9d:df:fa:7b associated with C3P0 2018-06-09T13:16:57-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 2 2018-06-09T13:24:37-04:00 L3 sdb[1097]: Wi-Fi: 8c:25:05:40:8a:1c re-joined C3P0 after 0 days 5 hours 57 minutes 52 seconds 2018-06-09T13:24:37-04:00 L3 sdb[1097]: Wi-Fi: Client 8c:25:05:40:8a:1c associated with C3P0 2018-06-09T13:24:37-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 5GHz radio 2 2018-06-09T13:28:57-04:00 L3 sdb[1097]: Wi-Fi: Client 00:19:9d:df:fa:7b left C3P0 2018-06-09T13:28:57-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 1 2018-06-09T13:30:02-04:00 L3 sdb[1097]: Wi-Fi: 00:19:9d:df:fa:7b re-joined C3P0 after 0 days 0 hours 13 minutes 5 seconds 2018-06-09T13:30:02-04:00 L3 sdb[1097]: Wi-Fi: Client 00:19:9d:df:fa:7b associated with C3P0 2018-06-09T13:30:02-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 2 2018-06-09T13:30:57-04:00 L3 sdb[1097]: Wi-Fi: Client 00:19:9d:df:fa:7b left C3P0 2018-06-09T13:30:57-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 1 2018-06-09T13:31:37-04:00 L3 sdb[1097]: Wi-Fi: 00:19:9d:df:fa:7b re-joined C3P0 after 0 days 0 hours 14 minutes 40 seconds 2018-06-09T13:31:37-04:00 L3 sdb[1097]: Wi-Fi: Client 00:19:9d:df:fa:7b associated with C3P0 2018-06-09T13:31:37-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 2 2018-06-09T13:49:45-04:00 L3 dnsmasq[2898]: no responses from nameserver '74.40.74.40' 2018-06-09T13:49:48-04:00 L3 dnsmasq[2898]: nameserver '74.40.74.40' is now responding 2018-06-09T13:50:34-04:00 L3 dnsmasq[2898]: no responses from nameserver '74.40.74.41' 2018-06-09T13:51:02-04:00 L3 sdb[1097]: Wi-Fi: Client 6c:fd:b9:67:53:94 left C3P0 2018-06-09T13:51:02-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 1 2018-06-09T13:52:48-04:00 L3 sdb[1097]: Wi-Fi: Client f0:6e:0b:0c:f3:2e left C3P0 2018-06-09T13:52:48-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 5GHz radio 1 2018-06-09T13:55:04-04:00 L3 sdb[1097]: Wi-Fi: Client 8c:25:05:40:8a:1c left C3P0 2018-06-09T13:55:04-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 5GHz radio 0 2018-06-09T13:55:05-04:00 L3 sdb[1097]: Wi-Fi: 8c:25:05:40:8a:1c re-joined C3P0 after 0 days 6 hours 33 minutes 19 seconds 2018-06-09T13:55:05-04:00 L3 sdb[1097]: Wi-Fi: Client 8c:25:05:40:8a:1c associated with C3P0 2018-06-09T13:55:05-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 2 2018-06-09T14:05:12-04:00 L3 dnsmasq[2898]: nameserver '74.40.74.41' is now responding 2018-06-09T14:15:08-04:00 L3 sdb[1097]: Wi-Fi: Client 00:19:9d:df:fa:7b left C3P0 2018-06-09T14:15:08-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 1 2018-06-09T14:15:48-04:00 L3 sdb[1097]: Wi-Fi: 00:19:9d:df:fa:7b re-joined C3P0 after 0 days 0 hours 58 minutes 51 seconds 2018-06-09T14:15:48-04:00 L3 sdb[1097]: Wi-Fi: Client 00:19:9d:df:fa:7b associated with C3P0 2018-06-09T14:15:48-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 2 2018-06-09T14:16:08-04:00 L3 sdb[1097]: Wi-Fi: Client 00:19:9d:df:fa:7b left C3P0 2018-06-09T14:16:08-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 1 2018-06-09T14:55:13-04:00 L3 sdb[1097]: Wi-Fi: 00:19:9d:df:fa:7b re-joined C3P0 after 0 days 1 hours 38 minutes 16 seconds 2018-06-09T14:55:13-04:00 L3 sdb[1097]: Wi-Fi: Client 00:19:9d:df:fa:7b associated with C3P0 2018-06-09T14:55:13-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 2 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[system.uptime] val[00:08:12:16] 2018-06-09T14:58:46-04:00 L4 cwmp[2841]: Resolving ACS URL - Retry 0 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.up-snr-margin] val[ 301] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.up-attainable-rate] val[1340] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.down-snr-margin] val[ 193] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.down-attainable-rate] val[12096] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.showtime-start] val[29454] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.last-showtime-start] val[29457] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.total.errored-secs] val[158] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.tr98-stats.total.atuc-errored-secs] val[85] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.up-snr-margin] val[ 268] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.up-attainable-rate] val[1288] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.down-snr-margin] val[ 166] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.down-attainable-rate] val[10572] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.showtime-start] val[29454] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.last-showtime-start] val[29457] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.total.errored-secs] val[628] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.total.atuc-errored-secs] val[62] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[phy.dsl.bonded-line.tr98-stats.total.severely-errored-secs] val[80] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].rx-bytes] val[2060741939] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].rx-packets] val[39017] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].tx-bytes] val[252951861] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: DSLF_WanMgmtChg path[conn[2].tx-packets] val[37505] 2018-06-09T14:58:46-04:00 L5 cwmp[2841]: Connect to https://secure.acs.frontier.com [216.52.29.165] Retry 0 2018-06-09T14:58:47-04:00 L5 cwmp[2841]: (SSL) Connect Success: secure.acs.frontier.com 2018-06-09T14:58:47-04:00 L5 cwmp[2841]: (SSL) Certificate Verify Success: secure.acs.frontier.com 2018-06-09T14:58:56-04:00 L5 cwmp[2841]: Post Inform - reason 2 PERIODIC 4 VALUE CHANGE 2018-06-09T14:58:56-04:00 L5 cwmp[2841]: Receive InformResponse 2018-06-09T14:58:56-04:00 L5 cwmp[2841]: Post 0 2018-06-09T14:58:56-04:00 L5 cwmp[2841]: next Periodic Inform after 86391 s 2018-06-09T14:58:57-04:00 L5 cwmp[2841]: Receive GetParameterValues 2018-06-09T14:58:57-04:00 L5 cwmp[2841]: Post error 9005 2018-06-09T14:58:57-04:00 L5 cwmp[2841]: Receive GetParameterValues 2018-06-09T14:58:57-04:00 L5 cwmp[2841]: Post GetParameterValuesResponse (chunk-length - 5530) 2018-06-09T14:58:57-04:00 L5 cwmp[2841]: Continue GetParameterValuesResponse (chunk-length - 0) 2018-06-09T14:58:57-04:00 L5 cwmp[2841]: Receive GetParameterValues 2018-06-09T14:58:58-04:00 L5 cwmp[2841]: Post GetParameterValuesResponse (chunk-length - 4244) 2018-06-09T14:58:58-04:00 L5 cwmp[2841]: Continue GetParameterValuesResponse (chunk-length - 0) 2018-06-09T14:58:58-04:00 L5 cwmp[2841]: Receive GetParameterValues 2018-06-09T14:58:58-04:00 L5 cwmp[2841]: Post GetParameterValuesResponse (chunk-length - 2124) 2018-06-09T14:58:58-04:00 L5 cwmp[2841]: Continue GetParameterValuesResponse (chunk-length - 0) 2018-06-09T14:58:58-04:00 L5 cwmp[2841]: Closing connection on HTTP 204 2018-06-09T14:58:58-04:00 L5 cwmp[2841]: (SSL) Closing Connection: secure.acs.frontier.com 2018-06-09T15:29:27-04:00 L3 sdb[1097]: Wi-Fi: 6c:fd:b9:67:53:94 re-joined C3P0 after 0 days 7 hours 39 minutes 14 seconds 2018-06-09T15:29:27-04:00 L3 sdb[1097]: Wi-Fi: Client 6c:fd:b9:67:53:94 associated with C3P0 2018-06-09T15:29:27-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 3 2018-06-09T15:44:28-04:00 L4 mcp[4943]: mcp[handle_igmpv2_leave_msg]: missing expected data rep=0xC0A80174 grp=0xE00000FB 2018-06-09T16:08:22-04:00 L3 sdb[1097]: Wi-Fi: Client 8c:25:05:40:8a:1c left C3P0 2018-06-09T16:08:22-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 2 2018-06-09T16:12:36-04:00 L3 sdb[1097]: Wi-Fi: Client 6c:fd:b9:67:53:94 left C3P0 2018-06-09T16:12:36-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 1 2018-06-09T16:12:55-04:00 L3 sdb[1097]: Wi-Fi: 6c:fd:b9:67:53:94 re-joined C3P0 after 0 days 8 hours 22 minutes 42 seconds 2018-06-09T16:12:55-04:00 L3 sdb[1097]: Wi-Fi: Client 6c:fd:b9:67:53:94 associated with C3P0 2018-06-09T16:12:55-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 2 2018-06-09T16:15:37-04:00 L3 sdb[1097]: Wi-Fi: Client 6c:fd:b9:67:53:94 left C3P0 2018-06-09T16:15:37-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 1 2018-06-09T16:15:48-04:00 L3 sdb[1097]: Wi-Fi: 6c:fd:b9:67:53:94 re-joined C3P0 after 0 days 8 hours 25 minutes 35 seconds 2018-06-09T16:15:48-04:00 L3 sdb[1097]: Wi-Fi: Client 6c:fd:b9:67:53:94 associated with C3P0 2018-06-09T16:15:48-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 2 2018-06-09T16:34:42-04:00 L3 sdb[1097]: Wi-Fi: Client 6c:fd:b9:67:53:94 left C3P0 2018-06-09T16:34:42-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 1 2018-06-09T16:35:41-04:00 L3 sdb[1097]: Wi-Fi: 8c:25:05:40:8a:1c re-joined C3P0 after 0 days 9 hours 13 minutes 55 seconds 2018-06-09T16:35:41-04:00 L3 sdb[1097]: Wi-Fi: Client 8c:25:05:40:8a:1c associated with C3P0 2018-06-09T16:35:41-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 2 2018-06-09T16:48:45-04:00 L3 sdb[1097]: Wi-Fi: Client 00:19:9d:df:fa:7b left C3P0 2018-06-09T16:48:45-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 1 2018-06-09T16:49:25-04:00 L3 sdb[1097]: Wi-Fi: 00:19:9d:df:fa:7b re-joined C3P0 after 0 days 3 hours 32 minutes 28 seconds 2018-06-09T16:49:25-04:00 L3 sdb[1097]: Wi-Fi: Client 00:19:9d:df:fa:7b associated with C3P0 2018-06-09T16:49:25-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 2 2018-06-09T16:50:45-04:00 L3 sdb[1097]: Wi-Fi: Client 00:19:9d:df:fa:7b left C3P0 2018-06-09T16:50:45-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 1 2018-06-09T17:02:23-04:00 L3 sdb[1097]: Wi-Fi: 6c:fd:b9:67:53:94 re-joined C3P0 after 0 days 9 hours 12 minutes 10 seconds 2018-06-09T17:02:23-04:00 L3 sdb[1097]: Wi-Fi: Client 6c:fd:b9:67:53:94 associated with C3P0 2018-06-09T17:02:23-04:00 L3 sdb[1097]: Wi-Fi: Number of clients associated on 2.4GHz radio 2 2018-06-09T17:18:14-04:00 L4 mcp[4943]: mcp[igmp_stats_del_host]: host (0x7401A8C0) not found to be removed in fwdgrp 1

I'm planning to get internet from frontier anew since on 'paper' they seem to have better deals than Comcast/Xfinity in my area. (see attachment at bottom) [ I'm currently using my phone's 22 Gig data plan for internet, but my daughter will be here, and she can use up that much data in a couple of days. :uhh: ] However, I do have a few questions about their plans and policies: 1. Aside from having no price increase for 2 years, what exactly "2 year price guarantee & no annual contract" entails? Does that mean that I have a 2 years long contract, or that I can cancel, say, after 9 months? 2. I may have some visitors for a few months. Can I add TV for, say, 6 months, and then go back to internet only service without penalties? 3. I may be out of the country for some time and I would have someone else live here during that time. How easy is to change the name on the account? Would that also reset the contract? 4. What are the actual prices (approximate) compared to advertised prices? [ATT=1]