Re: Broadcast Address as Gateway

From: Moe Trin (ibuprofin_at_painkiller.example.tld)
Date: 06/23/05

  • Next message: Robert Nichols: "Re: ntp not starting up correctly..." 
    Date: Wed, 22 Jun 2005 20:30:51 -0500

    In the Usenet newsgroup comp.os.linux.networking, in article
    <KNidnSYyTZzyzCTfRVn-rQ@rogers.com>, James Knott wrote:

    >A real mixture. There was OS/2, Windows, AIX, VM/MVS and probably a few
    >others. This was in IBM Canada HQ.

    OS/2 and windoze would be real problems, as they're both single user
    systems, and given the chance a user will screw it up. AIX shouldn't
    be any more of a problem than VM/MVS, and I wouldn't expect them to be
    doing walkies anyway.

    >When I started there, everything was static, but there was a gradual move to
    >DHCP. There were a lot of people coming and going. Many of the employees
    >had ThinkPads.

    That's begging for problems. About a quarter of our scientists/engineers
    have home systems - usually semi-retired workstations - with dedicated
    connections back to here. Woe betide the user who lets family use the
    boxes, so that cuts down problems (plus, they are running a *nix of some
    form). But the rules of the game say that the company computers stay
    where they are, and no personal systems are allowed into the facility.
    Thus, we don't need DHCP for that reason. We have a few systems that do
    wander the halls (projector screen systems used for presentations and
    the like), and we simply have them registered for each subnet in the
    building. When the systems boot, the networking script halts the boot
    until the user enters a network name, and that is used to select the
    right IP from an internal list - along with the NIS crap.

    >I had a static IP, with my first ISP. This was back in the days of dial up
    >& SLIP.

    I've (thankfully) forgotten just about everything I ever knew about
    SLIP. But I suspect that was not "common". For ordinary people, dialing
    into a BBS was probably about as exotic as they got.

    >I agree that routers, servers etc shouldn't have temporary DHCP addresses.
    >However, it is possible, though not recommended to permanently assign a
    >DHCP address to a device.

    My contention with 'permanent' addresses via DHCP is that if you are going
    to jump through the hoops to set that up (and I'm ignoring the DNS end of
    things), why not set the system to static and be done with it.

            Old guy

  • Next message: Robert Nichols: "Re: ntp not starting up correctly..."

    Relevant Pages

    • Re: Broadcast Address as Gateway
      ... we don't need DHCP for that reason. ... When the systems boot, the networking script halts the boot ... There are several IBM locations in the area and many employees would find ...
      (comp.os.linux.networking)
    • Re: New on cable. Bash prompt name changed?
      ... my permanent "back" address? ... It seems you get your address by DHCP from Comcast, ... that it can set your client DNS server address to use for example. ... router. ...
      (Fedora)