On Wed, 21 Feb 2001, Chris Ralph wrote:
>
> Slight misunderstanding here. We disconnected the Win machine and used it's
> cable connection. Normally this machine is used to route to 2 other Win
> machines, but that was not what we tried. We just pulled the plug from the
> Win machine and put it into the PCMCIA interface connection.
That doesn't always work - some cable/DSL modems are tied to the first
Ethernet MAC address they see, and need to be reset or power-cycled when
you switch computers.
> Thanks to an abnormally helpful person in Optus, I do have my "username",
> "password", "hostname", IP address, gateway and netmask.
> Apparently they don't normally bother to give this out - unless you are
> running a particular version of Macintosh software.
They'd better give *some* of it out in other cases. :-)
With a bridging setup, the username and password are completely irrelevant
to getting connected, although the hostname may matter for DHCP. Most
likely the username and password are for accessing the mailserver, not for
merely getting connected.
On Wed, 21 Feb 2001, Tim Seifert wrote:
> By: Chris Ralph <[EMAIL PROTECTED]>
> On: Wednesday, February 21, 2001, 7:23:26 AM
>
> CR> Is there any reason to prefer either way of connecting? Static/DHCP?
>
> Static IPs have the advantage that you're always reachable at the same
> address. Essential for running a server, "properly."
Yes, although @Home officially prohibits servers, anyway.
> The disadvantage is that a hacker always knows where you are, and you
> can't just disconnect, and reconnect with a new IP to escape them.
Though that's less important with less vulnerable software like MiamiDx.
> However, what I don't know from your e-mail, is whether your ISP gives you
> a static address, and you're asking whether it's better to just program
> the address into your configuration permanently, or let the software find
> it out itself, each time it connects (using DHCP).
Yes, there are two different issues - whether the address is static, and
whether the means of configuring it is static.
AFAIK, @Home is still using static IPs, although they support DHCP and may
require it at some point. They officially prefer the DHCP-based setup,
since it won't need to change if they stop assigning addresses statically.
However, the tech who installed @Home here set it up statically, and gave
two reasons:
1) The modem provisioning takes a while, and he can do the static config
in parallel with that. With DHCP he'd have to wait.
2) Sometimes their DHCP servers are down. :-)
Fred Wright
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
