I guess, then, it's worth noting that I only intend to use these
servers from within my own network. For example, after I do
transactions to my checkbook I run the commands:
scp register.txt wam.umd.edu:
ssh wam.umd.edu importregister
scp register.txt 192.168.1.2:
ssh 192.168.1.2 importregister
where the importregister macro does a grandfather-father-son backup
and also runs a diff between the old and new files (so I see only the
new transaction lines) and gives me a chance to say go-nogo on the
update. The problem is with the DHCP address assignment I have to go
look at which IP address the server is using (last time I looked it
was 5, so I had to ssh/scp to 192.168.1.5) and it changes from time to
time.
I don't think this violates TOS. Now, the FTP port open to that
server might actually be a violation. I assume their intent is to
control traffic, so if it only gets used once a month I don't feel too
bad about it.
And as for the Macintosh remote login, it's me talking to my own
machine, who's to say if it's a "server" at all?
On Apr 10, 2008, at 5:35 PM, Nick Cummings wrote:
It's perhaps worth noting here, that if you FIOS home service (as
opposed to business), running a server is technically a violation of
the
TOS.
Nick
Justin Walker wrote:
You can get around the DHCP problem by simply setting your 'server'
machines to static IPs sufficiently high in the range that they won't
get messed with (IE 192.168.1.200 and 201). However, you will
definitely need to get access to the router to open ports.
I don't think it's at all unreasonable to ask for login access to
your
router. They may be unwilling to open ports - many ISPs block them
from their end, but it never hurts to ask.
- Justin
Charles Cranston wrote:
I've had two friends move in with me this weekend (long story, they
lost their lease suddenly and unexpectedly) into a 4 bedroom
single-family house in Burtonsville. They had Verizon networking
and
were adamant about bringing it with them, and I was none too happy
with Comcast networking and video (lots of problems, another story),
so I was not that unhappy when we snipped the Comcast wires and
brought in FIOS.
There is an ONT (Optical Network Terminal) which is connected to a
branched coaxial cable that feeds the three set-top video boxes and
one modem-router-switch-wireless-access-point unit. The router will
service DHCP to all my wireless machines and the two "server"
(desktop) machines I have plugged into their switch.
However, under Comcast I had access to the router (I owned the modem
and a Linksys BEF4W11 something like that). I had it serve DHCP
addresses starting at 64 (192.168.1.64 and up) and reserved lower
addresses for my server machines, I had the Macintosh on 192.168.1.2
and the Linux machine on 192.168.1.3 and everything was well.
I don't have access to the FIOS configuration setup. My friends are
not technical people, so they don't know what I'm talking about, and
the service is not in my name, so it's not clear how I ask Verizon
about changing this situation. Does anybody have any experience
with
Verizon FIOS networks with hardware like this? Is i reasonable for
me to ask for access to the router setup? I'd like to reserve a
small number of fixed IP addresses at the bottom, and open at least
one port from the outside world (I had 3 before, one for X, one for
FTP, and one for a Macintosh remote-management-access protocol,
and I'd like to at least have that third one reinstated)?
