And all I get is 1.5mbps DSL because they are still using ancient copper out in my neck of the woods. C'mon... PLEASE.
There's nothing wrong with copper or its age. You're too far from the CO.
If competitive carriers like CenturyLink had access to facilities that THE PUBLIC PAID FOR that now belong to Verizon et. al. they could put gear in the patch cabinets much closer to their subscribers (this is known as FTTC). In the UK there are several carriers using VDSL2 technology to provide 80mbps down/20mbps up service over "ancient copper" for a little more than the price of a normal DSL line, because their gear is only 300m from the subscriber in the neighborhood patch cabinet.
But the US Congress repealed the legislation requiring incumbents to allow acces to their facilities in 2005, so the end result is that the broadband situation in the US for most folks is:
- Incumbent DSL that isn't faster than it was 10 years ago
- Cable
- If you're very lucky, fibre
Maybe it's because a whole lot of people don't want to screw around with a full-blown PC anymore & just get on with doing what they need to do instead of fighting with Windows Update & malware all the time.
Including our CEO, who does all his work on the road with...
Personally, I'm lazy. I've been using Pine (now Alpine) directly on a mail server for all my mail since 1995 (on my own servers since '97). Old habits die hard.
It works great over really low bandwidth connections (though sometimes high latency can be annoying), you can view any attachments you need automagically with X11 forwarding via SSH, and you don't care at all about which machine you're accessing it from. Also you get to read the TEXT in your mails & not HTML, most of which is useless garbage when it comes to emails (for the 0.1% of HTML mail I do actually need to read as HTML, such as tables, Linx often gets the job done, & if not I just bounce it to my gmail account, which is pretty much full of spam otherwise).
When various folders get Too Big (or I move on to another job, or whatever) I move them into an "archive" folder (& I have an "old-archive" folder for the really ancient stuff) and bzip2 them. I archive my inbox files at the beginning of every year too. When I need to find something old, I just bzgrep for it. After an archiving session (which takes all of 5 minutes) the whole thing gets backed up from my mail server to my NAS at home.
Did I mention that my backup MX is a SparcStation 20 and still works just fine for all this? Of course I don't keep much on it but if my main server dies I can still send & receive mail just fine.
Note that this is not exactly something I sat down & spent time thinking about, I just started moving mail out of the way like this when I left college & built a couple of OpenBSD mail & DNS servers, and kept doing it as it works well enough.
Run your own IMAP server. For the past decade or so, Dovecot has by far & away become the best choice. If you've set up any other daemons before it's really not very complicated software.
Why would you need an appliance for something that can be done in software?!? The only "appliance" you need is an ethernet switch between your residential connection bridges and your firewall.
Mkay, so I followed the link & translated his new regional metro fiber carrier's FAQ from German. It seems like they're pretty clued in & have a reasonably OK explanation of why their customers only get NATted IPv4. I think they're possibly lacking a bit in funds, clue, or both.
The OP should make sure someone from his ISP goes to the next RIPE meeting in Dublin in May. There are plenty of ways to provide better service to their customers without breaking the bank, and the folks at RIPE will tell you how.
Your ISP should at least be giving you a block of static ports on a static public IPv4 address so that you can just map them on your home router afterwards. It's called "port block allocation". See this slide deck for more details.
Port control protocol is also very close to being reality. It's a bit like a combination of UPnP and DHCP that allows static IPv4 ports to be requested by and allocated to an end user like IP addresses are now.
You should pester your ISP about these two services monthly until they have a satisfactory response for you. Frankly it's irresponsible on their part if they don't have a FAQ explaining this stuff and a policy for helping customers deal with these things. To do otherwise is demeaning to their customers.
A really good reason to run OpenBSD on sparc64 hardware is that the logical domain support is stable now, so you can use the processor's built-in virtualization framework: http://undeadly.org/cgi?action=article&sid=20121214153413
A really good reason to run OpenBSD on sparc64 hardware is that the logical domain support is stable now, so you can use the processor's built-in virtualization framework: http://undeadly.org/cgi?action=article&sid=20121214153413
agree. we love old hardware for personal nostalgic reasons. which is why my backup MX/secondary DNS is still on a SparcStation 20 (running OpenBSD).
To the OP, I'd recommend running OpenBSD on it, as there are a lot of servers in the project that still run on Sparc boxen. Sparc64 support is top notch, and actually supports some machines that OpenSolaris (IllumOS) & Linux don't: http://www.openbsd.org/sparc64.html
Slashdot Mirror
And all I get is 1.5mbps DSL because they are still using ancient copper out in my neck of the woods. C'mon... PLEASE.
There's nothing wrong with copper or its age. You're too far from the CO.
If competitive carriers like CenturyLink had access to facilities that THE PUBLIC PAID FOR that now belong to Verizon et. al. they could put gear in the patch cabinets much closer to their subscribers (this is known as FTTC). In the UK there are several carriers using VDSL2 technology to provide 80mbps down/20mbps up service over "ancient copper" for a little more than the price of a normal DSL line, because their gear is only 300m from the subscriber in the neighborhood patch cabinet.
But the US Congress repealed the legislation requiring incumbents to allow acces to their facilities in 2005, so the end result is that the broadband situation in the US for most folks is:
- Incumbent DSL that isn't faster than it was 10 years ago
- Cable
- If you're very lucky, fibre
Unless you block them (ahem, hosts file), they do have data on you...
NoScript does the trick pretty nicely too...
n/t
Maybe it's because a whole lot of people don't want to screw around with a full-blown PC anymore & just get on with doing what they need to do instead of fighting with Windows Update & malware all the time.
Including our CEO, who does all his work on the road with...
a 10" iPad.
Personally, I'm lazy. I've been using Pine (now Alpine) directly on a mail server for all my mail since 1995 (on my own servers since '97). Old habits die hard.
It works great over really low bandwidth connections (though sometimes high latency can be annoying), you can view any attachments you need automagically with X11 forwarding via SSH, and you don't care at all about which machine you're accessing it from. Also you get to read the TEXT in your mails & not HTML, most of which is useless garbage when it comes to emails (for the 0.1% of HTML mail I do actually need to read as HTML, such as tables, Linx often gets the job done, & if not I just bounce it to my gmail account, which is pretty much full of spam otherwise).
When various folders get Too Big (or I move on to another job, or whatever) I move them into an "archive" folder (& I have an "old-archive" folder for the really ancient stuff) and bzip2 them. I archive my inbox files at the beginning of every year too. When I need to find something old, I just bzgrep for it. After an archiving session (which takes all of 5 minutes) the whole thing gets backed up from my mail server to my NAS at home.
Did I mention that my backup MX is a SparcStation 20 and still works just fine for all this? Of course I don't keep much on it but if my main server dies I can still send & receive mail just fine.
Note that this is not exactly something I sat down & spent time thinking about, I just started moving mail out of the way like this when I left college & built a couple of OpenBSD mail & DNS servers, and kept doing it as it works well enough.
Run your own IMAP server. For the past decade or so, Dovecot has by far & away become the best choice. If you've set up any other daemons before it's really not very complicated software.
Does pfsense support automatic shutting down from UPS/low battery alerts?
yep
Great idea.
The fact that the protocol supports this without requiring changes to the applications is pretty impressive.
NOOOooo...
Why would you need an appliance for something that can be done in software?!? The only "appliance" you need is an ethernet switch between your residential connection bridges and your firewall.
but he's a week too early!
dupes are really just not that hard to eliminate...
Because, contrary to popular judeo-christian mythology, evolution is NOT magic.
Please defend your statement by pointing out the section of the Bible where evolution is discussed.
Because folks confusing what a bunch of right-wing fundamentalist nutjobs spout on TV vs. actual Christian religious tradition is part of the problem.
n/t
it Just Worked, and they weren't trying to screw around with adding useless UI elements to it all the time
Who would redo the same today?
Iran & North Korea.
During the Battle of Blair Mountain in 1921.
So don't think it can't happen.
n/t
Mkay, so I followed the link & translated his new regional metro fiber carrier's FAQ from German. It seems like they're pretty clued in & have a reasonably OK explanation of why their customers only get NATted IPv4. I think they're possibly lacking a bit in funds, clue, or both.
The OP should make sure someone from his ISP goes to the next RIPE meeting in Dublin in May. There are plenty of ways to provide better service to their customers without breaking the bank, and the folks at RIPE will tell you how.
Your ISP should at least be giving you a block of static ports on a static public IPv4 address so that you can just map them on your home router afterwards. It's called "port block allocation". See this slide deck for more details.
Port control protocol is also very close to being reality. It's a bit like a combination of UPnP and DHCP that allows static IPv4 ports to be requested by and allocated to an end user like IP addresses are now.
You should pester your ISP about these two services monthly until they have a satisfactory response for you. Frankly it's irresponsible on their part if they don't have a FAQ explaining this stuff and a policy for helping customers deal with these things. To do otherwise is demeaning to their customers.
...not states. Like Virginia did. Or rather tried...
Maybe they should work on breeding smarter (instead of fatter) cattle so they can figure out where they need to shit?
A really good reason to run OpenBSD on sparc64 hardware is that the logical domain support is stable now, so you can use the processor's built-in virtualization framework: http://undeadly.org/cgi?action=article&sid=20121214153413
A really good reason to run OpenBSD on sparc64 hardware is that the logical domain support is stable now, so you can use the processor's built-in virtualization framework: http://undeadly.org/cgi?action=article&sid=20121214153413
OpenBSD now has mature support for sparc64 logical domains: http://undeadly.org/cgi?action=article&sid=20121214153413
agree. we love old hardware for personal nostalgic reasons. which is why my backup MX/secondary DNS is still on a SparcStation 20 (running OpenBSD).
To the OP, I'd recommend running OpenBSD on it, as there are a lot of servers in the project that still run on Sparc boxen. Sparc64 support is top notch, and actually supports some machines that OpenSolaris (IllumOS) & Linux don't: http://www.openbsd.org/sparc64.html