Be warned: Verizon absolutely forbids users to run ANY kind of server on their network. No email or web hosting especially. They enforce this by locking down incoming ports on the DSL router they provide (and if you provide your own, they force you to configure it like theirs and lock your access out of it.) I don't know if you can even telnet into a machine on Verizon's network. I suspect not, since you can't forward the telnet port.
Reliably, they've been excellent, but they don't want users who are going to do things much more advanced than read email and surf the web.
That is, in fact, a show-stopper. :-( Even if I'm not telnetting home to read all my mail, I absolutely must be able to get back to my home machines to access files and tools stored there, including old mail archived off of whatever main mail machine I'm using, a few spreadsheets, sheet music, music typesetting tools (most of these via telnet, a few via ftp) ... And though I don't need it often, the times I need to access my Windows machines using VNC (http://www.realvnc.com/) I really need that to work.
I can deal fine with not running my own web server (it'd be nice to be able to host a special-purpose web site but I was already planning to continue to have the public one hosted outside my house). I can cope with not having SMTP directly into my in-house mail server (I'll grumble, but I don't have that now anyhow). I'd prefer to have outbound SMTP directly, but if they make it easy to point Sendmail on my main Linux box to their relay, I'll deal. But I must have telnet and VNC access to my home machines from outside of my house.
Note that if I'm connecting from somebody else's computer and they don't already have a VNC client installed, I've got two choices: download and install VNC on their machine, or hit the minimal web server built into the VNC server and run the Javascript VNC client it sends me. It's not on the default HTTP port, but if Verizon blocks everything inbound by default, it'll still break.
(no subject)
Reliably, they've been excellent, but they don't want users who are going to do things much more advanced than read email and surf the web.
(no subject)
That is, in fact, a show-stopper. :-( Even if I'm not telnetting home to read all my mail, I absolutely must be able to get back to my home machines to access files and tools stored there, including old mail archived off of whatever main mail machine I'm using, a few spreadsheets, sheet music, music typesetting tools (most of these via telnet, a few via ftp) ... And though I don't need it often, the times I need to access my Windows machines using VNC (http://www.realvnc.com/) I really need that to work.
I can deal fine with not running my own web server (it'd be nice to be able to host a special-purpose web site but I was already planning to continue to have the public one hosted outside my house). I can cope with not having SMTP directly into my in-house mail server (I'll grumble, but I don't have that now anyhow). I'd prefer to have outbound SMTP directly, but if they make it easy to point Sendmail on my main Linux box to their relay, I'll deal. But I must have telnet and VNC access to my home machines from outside of my house.
(no subject)