DSL service interruption in Santa Rosa.

Thu Apr 21 14:26:11 PDT 2005 — DSL service interruption in Santa Rosa. We are experiencing a general DSL outage affecting much of the Santa Rosa area. ASI is working on the problem and we hope to have service restored soon. -Sonic.net Support

UPDATE – The DSL service interruption in Santa Rosa is due to emergency maintenance being performed by SBC. They hope to have service restored within an hour. -Sonic.net Support

DSL Outage in Santa Rosa.

Wed Apr 20 19:19:34 PDT 2005 — DSL Outage in Santa Rosa. At 5:47pm, ASI reported a general outage in the Santa Rosa area. All circuits on the SNRSCA01BB1 gear are directly affected, though reports of collateral sync-no-surf problems have been reported throughout the area. We have no ETR at this time. -Eli and John F

Update: ASI officially reports that service was successfully restored at 7:00pm. This is consistent with testing from our side at the time. -John F

DSL Firewall Features Roll Out Tomorrow.

Mon Apr 11 16:42:59 PDT 2005 — DSL Firewall Features Roll Out Tomorrow. This is a reminder that we will start rolling out the application of the DSL firewall features Tuesday morning, 4/12/05. We will apply them to successive groups of DSL customers at a rate that our technical support folks can manage. Please see Dane’s previous MOTD for details of this new service. -John, Nathan and Kelsey

BroadLink Scheduled Outage Notification.

Sat Apr 2 12:29:02 PST 2005 — BroadLink Scheduled Outage Notification. BroadLink is currently upgrading their wireless network backhaul, which will yield improved performance for wireless connected customers. BroadLink says:

“An important component of our upgrade plans will require a brief planned outage as we swap an old backhaul radio for a faster unit.

We will be making this change on Saturday morning (April 2nd) beginning at 9:00am. As we fine-tune the new system (or in the case of disaster revert to the old hardware) service will fluctuate significantly. The project should be completed by 12:00 Noon.”

While normally, intrusive network maintenance is done at night, tower safety requirements dictate that this work be done during daylight hours. Additionally, while normally upgrades can be built and tested prior to deployment, with the deployment then just being a quick switch-over, the local radio frequency spectrum usage requires that this upgrade be done with the current link offline, as the two would interfere with each other.

I believe that BroadLink provided this notice via email to their customers, but Sonic.net missed getting it into our MOTD a few days ago, when the information was released. I’m sorry about that! -Dane

Sonic.net announces firewalling for DSL…

Wed Mar 30 17:16:27 PST 2005 — Sonic.net announces firewalling for DSL connections.

I am happy to announce that Sonic.net will be providing firewall protection for DSL connections, beginning on April 12th, about two weeks from now. There are more and more threats to computers which are coming from the Internet, so I’m very pleased that we’re launching this exciting new feature for Sonic.net DSL customers!

Firewalling helps protect your systems from various Internet threats, including worms, viruses and spam relaying. In the next couple weeks, prior to the deployment, you are welcome to change the initial filtering level using our new DSL filtering configuration tool at: sonic.sonic.net/members/dslfilter/

Sonic.net’s DSL port firewalling features provide various levels of protection for DSL connected computers. By using one of the three levels of filtering, you can protect your systems from many common Internet threats. If you’d like to change from the default, we suggest that you to select a level of protection which is appropriate for your type of Internet usage and your understanding of system security. For most customers, the default setting will provide a good degree of protection with little or no impact on your ability to use a full range of Internet applications.

Three levels of filtering are available:

Option One: Complete Inbound TCP Firewalling. This firewall rule set prevents any inbound TCP connections from being established, protecting your system from most types of Internet attacks.

Option Two (the default, recommended by Sonic.net): Common Exploitable Port Firewalling. This is the default firewall rule set applied to DSL circuits. It blocks traffic on port 25 (SMTP email) both to and from a customers circuit to any mail servers other than Sonic.net maintained servers as well as preventing communication on ports used by common Microsoft services that are frequently exploited.

Option Three: Port 25 Firewalling. This firewall rule set only restricts traffic on port 25 (SMTP email) to and from a customers circuit to any mail servers other than sonic.net maintained servers. This is the minimum recommended rule set. This rule set generally prevents your computer from being hijacked and used to send SPAM directly to other mail servers.

Finally, we’ve always offered static IP addresses and we do welcome customers running their own servers on static IPs, so an option to turn off all filtering for those customers is available as well. We recommend that you only exercise this option if you run a mail server yourself on your DSL connection. Please do be careful with system security if you elect to turn off all filtering!

For more details on the specifics, please see our DSL Firewalling FAQ at: www.sonic.net/support/faq/advanced/dsl_firewalling.shtml

For discussions on this topic, please do read and post to the local discussion group at news://news.sonic.net/sonic.dsl

-Dane, Kelsey, Nathan, Chris, etc.

New Inbound Mail Servers.

Wed Mar 23 13:46:37 PST 2005 — New Inbound Mail Servers. We added two new mail servers to handle MX services for inbound mail. The new servers will enable us to continue to make advancements in the quality of our MTA level SPAM, virus and phish blocking while also increasing the availability of our MX cluster. In order to properly utilize the new servers we’ve also updated the MX records for all of the domains that we are authoritative for. If we host MX services for a domain that we are not authoritative for users should update their zones to take advantage of the new servers. Any domain using us for mail should have the following MX records:

IN MX 10 mailin-01.mx.sonic.net. IN MX 10 mailin-02.mx.sonic.net.

Please direct any questions about the new MX servers to news://news.sonic.net/sonic.net -Kelsey and Augie

Scheduled Data Center Maintenance.

Mon Mar 21 17:07:11 PST 2005 — Scheduled Data Center Maintenance. On Tuesday and Wednesday, 3/22-23/05, we will be doing maintenance on the power system in the Santa Rosa data center. This activity will be fully scripted and we anticipate no interruption in service of any kind. -John, Russ and Clay

Office phone system problems.

Wed Mar 16 11:13:36 PST 2005 — Office phone system problems. This morning we experienced a phone system circuit outage which prevented the Sonic.net offices from receiving any inbound calls. All of our dial-up and other Internet services were functioning normally during the outage, but our support department, billing and other service departments were not reachable by phone. We have corrected the problem and apologize for any inconvenience. -Support and Ops

Another brief DoS attack was targeted at one…

Tue Mar 15 09:55:12 PST 2005 — Another brief DoS attack was targeted at one of our DSL subscribers in Santa Rosa. The customer’s circuit has been disabled and their IPs have been blocked at our borders pending further investigation on our part. During this time DSL customers terminated in Santa Rosa may have experience slow performance and packet loss on their DSL circuits. -Kelsey and Nathan

DoS Attack.

Mon Mar 14 11:39:53 PST 2005 — DoS Attack. A brief DoS attack was targeted at our network, most likely at a DSL customer terminated in Santa Rosa. While the attack was underway DSL customers in Santa Rosa may have experienced some loss and latency and associated issues. It’s not believed that the attack had much affect if any on other parts of our network. -Nathan, John and Kelsey