OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Abdul Rehman Gani (abdulgeastcoast.co.za)
Date: Wed Feb 21 2001 - 01:03:47 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Hi,

    I posted this last week and received no response. I realise this is a
    voluntary list but, frankly, I am concerned about what happened and would
    like to take steps to prevent it from happenening again. I would really
    appreciate some help on this or pointers to try to resolve it.

    Thanks,

    Abdul

    > -----Original Message-----
    > From: owner-miscopenbsd.org [mailto:owner-miscopenbsd.org]On Behalf Of
    > Abdul Rehman Gani
    > Sent: 15 February 2001 10:31
    > To: OBSD-Misc
    > Subject: arpresolve: unable to allocate llinfo
    >
    >
    > Hi,
    >
    > Two of my OBSD servers had exhibited strange behaviour in the last week.
    >
    > The first, on Sunday, was a 2.7 server running Squid 2.2-stable5
    > and tinydns
    > from djbdns 1.02. It started displaying '/bsd: arpresolve: can't allocate
    > llinfo' and no connections could be made to it. I rebooted and it's been
    > fine since.
    >
    > Then this morning another server running OBSD 2.6, with qmail
    > 1.03, vpopmail
    > 4.9.6-1, httpd and dnscachex from djbdns 1.04 also started displaying the
    > error and stop accepting connections. I rebooted and it's been fine.
    >
    > I have searched the misc archive and most indicators seem to be
    > that it's a
    > routing or netmask problem. Thing is, these machines have been in service
    > for over 6 months and 1 year respectively and this is the first
    > time I have
    > seen this problem - no changes to any routing/tcp-ip/netmask
    > table recently,
    > except that I changed from named to dnscache on the second machine at the
    > end of Jan and installed tinydns on the first in November. I have another
    > 2.7 machine running tinydns and a 2.8 running dnscache and those have not
    > exhibited these problems (yet).
    >
    > What should I look for to try to diagnose this problem (one of
    > the messages
    > in the archive hinted a arp poisoning!?!)? I did not try to check anything
    > before rebooting, but I would appreciate some pointers about where to look
    > or what to do if this happens again.
    >
    > Thanks,
    >
    > Abdul
    >
    > --
    > East Coast Access (http://www.eastcoast.co.za)
    > Tel: +27-31-267-0169
    > Fax: +27-31-267-0168
    >
    >
    >