[Deganawida-sysadmin] Eth config

[mtoups at indymedia.org]

On Wed, 6 Aug 2003 bks10 at cornell.edu wrote:

> Just curious what's up with dega's ethernet config? Right now it's 
> getting an outside route to the world through the xl interface - is the 
> dhcp server smart enough to give dega the same IP address every time, or 
> does this need to be changed before a reboot?

yes, it will get the same IP address every time from
the DHCP server, though I suggest that since the IP
address is static we configure dega with the static IP
and not use DHCP.  the reason for this is that if there
is a cabling problem or other sort of network outage,
it sucks to lose the DHCP lease and drop off the net
whereas if you have the IP configured directly the
system comes back up as soon as the cabling problem
is resolved.  we've experienced this before with howard.

were you expecting the xl interface to be the "outside
world" NIC or was that supposed to be the fxp interface?

> Also, in the dmesg I don't see the fxp (intel nic) that was in there. Did 
> it get jostled out of the PCI slot when I was doing an interpretive dance 
> with dega and a hammer (or during the bus ride), or is it being used 
> elsewhere? Not a big deal if there is a better use for it, but my 
> understanding was that we'd have 2 nics in there, one for access to 
> walesa, and the other one to access the outside world... I can resolve 
> walesa (to 128.2.41.37), but I can't ping it from dega, which is pretty 
> much the bottleneck in what needs to be done on the machine. Can someone 
> from pitt clue me in?

I don't know what is up with the PCI slot situation as I haven't
touched the box at all, Quinten will have to answer this one.

The reason you can resolve walesa is that I got it an outside
IP address in order to do a reinstall last month.  that was
just a temporary situation and walesa is not normally reachable
from the outside world.  which reminds me, i should get rid of
that IP address now.  that explains why you can't ping it.

you are right about using a dedicated nic for connection to
walesa, but at the moment walesa needs a third NIC before
this can happen.  it is still the plan, though.  it just
involves sending someone to the pittsburgh IMC space to 
retrieve one of the lovely xl0's from ithaca, taking it
to the colo to put into walesa, and crimping a crossover
cable.

i just got back in town and haven't seen or touched dega,
but i can answer these questions at least.

> PS - Also I'm noticing the xl is running at 10baseT - yick - is this a 
> symptom of the hub situation? 

yes, dega (and staughton) are on a lame 10baseT hub at the moment.  
we are short on hubs around here these days, though we could
swap hubs/switches from other locations around and do better.  its 
been "on the list", though since we have no spare hubs around
it has been hard to switch across town since it would involve
downtime.  donated hubs/switches are welcome :)

-matt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 240 bytes
Desc: not available
Url : http://lists.indymedia.org/pipermail/deganawida-sysadmin/attachments/20030806/4e8f322d/attachment.bin