headers
Edi CAHYADI | 2 Oct 2006 07:35

Unable to lookup host registered in hosts file

Hi All,

I have 2 servers:
hostA: RedHat Linux 2.4.21-40.EL
hostB: HP-UX 10.20

From hostA, I can't lookup hostB even though I put its entry in /etc/hosts file.

root <at> hostA:/> host hostB
Host hostB not found: 3(NXDOMAIN)

Nsswitch.conf is configured to search file first:
root <at> hostA:/> grep ^hosts /etc/nsswitch.conf
hosts:      files dns

But ping works:
root <at> hostA:/> ping hostB
PING hostB.domain (<hostB's IP>) 56(84) bytes of data.
64 bytes from hostB.domain (<hostB's IP>): icmp_seq=0 ttl=254 time=0.208 ms
64 bytes from hostB.domain (<hostB's IP>): icmp_seq=1 ttl=254 time=0.231 ms

--- hostB.domain ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1011ms
rtt min/avg/max/mdev = 0.208/0.219/0.231/0.018 ms, pipe 2

Can anybody tell me why is that so, and how to solve it such that host lookup can work just like nslookup in HP Unix?

Regards,
Edi
(Continue reading)

Permalink | Reply | 1 comment |
headers
Adam T. Bowen | 2 Oct 2006 10:36
Favicon

Re: Unable to lookup host registered in hosts file

Hi,

Edi CAHYADI wrote:
> Hi All,
> 
> I have 2 servers:
> hostA: RedHat Linux 2.4.21-40.EL
> hostB: HP-UX 10.20
> 
>>From hostA, I can't lookup hostB even though I put its entry in /etc/hosts file.

Commands like host, dig and nslookup are DNS lookup utilities and so
don't use the configuration defined in /etc/nsswitch.conf.  The switch
file is used to define different ways to find host names (amongst other
things) of which DNS is just one.

Cheers

Adam
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |
headers
Miguel González Castaños | 7 Oct 2006 16:48
Picon

problems with grub

Hello,

 I have Debian testing and I do not know what is happening but when I boot, instead that grub runs the default
kernel after the set timeout, grub keeps waiting...Herewith my grub

default=10

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the 
default entry
# (normally the first entry defined).
timeout=3

# Pretty colours
color cyan/blue white/blue

[...]

title           Debian GNU/Linux, kernel 2.6.18 Default
root            (hd0,1)
kernel          /boot/vmlinuz root=/dev/hda2 ro
savedefault

and then the rest of kernels...

Regards,

Miguel

-
(Continue reading)

Permalink | Reply | 1 comment |
headers
Albert Bicchi | 8 Oct 2006 02:47
Picon

Re: problems with grub

You have a line that says: default=10
I assume that you have at least 10 kernel boot entries on your grub
menu. Also, the "default" number starts counting from 0 and not from
1.

Here is my entry on Ubuntu; perhaps it can help in some way. Notice
the 'boot' option after savedefault.

title        Ubuntu, kernel 2.6.15-27-amd64-k8 Previous
root        (hd0,1)
kernel        /boot/vmlinuz.old root=/dev/sda2 ro quiet splash
initrd        /boot/initrd.img.old
savedefault
boot

On 10/7/06, Miguel González Castaños <mgc <at> tid.es> wrote:
> Hello,
>
>  I have Debian testing and I do not know what is happening but when I boot, instead that grub runs the default
kernel after the set timeout, grub keeps waiting...Herewith my grub
>
>
> default=10
>
> ## timeout sec
> # Set a timeout, in SEC seconds, before automatically booting the
> default entry
> # (normally the first entry defined).
> timeout=3
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
James Grimwood | 8 Oct 2006 10:51
Picon

Sorting maildir mailboxes

I'm running Courier IMAP on my server, with the mail being stored in
maildir directories according to procmail rules I've created - so for
each mailing list I'm on there's a separate folder.

To begin with, what's the correct way to send all the mail from the
main inbox folder back through procmail so it gets resorted?

My next problem is that some of the mailing lists I'm on are quite
high traffic and there's thousands of messages in each IMAP folder,
making them quite hard to navigate. Is there a way I can periodically
sort through all the IMAP folders and archive things monthly, putting
each month in a new sub-folder.

i.e

I have a folder called "Linux-Admin", and after archiving I'd like the
following folder structure:

Linux-Admin / Jan2006
Linux-Admin / Feb2006
...
and so on.

I'd only do this once a month, and don't mind if I need to manually
specify which folders need processing, it doesn't need to recurse
through the entire IMAP directory structure. I also have full
commandline access to my IMAP server so don't need to do this using an
IMAP client.

--

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
Yuri Csapo | 10 Oct 2006 21:04
Picon
Favicon

Re: iscsi woes - SOLVED


It turns out there was a quirkiness in the target I'm using. The good
people developing open-iscsi suggested I use a newer snapshot that
already knows about my hardware as opposed to the debian package. All is
well now.

Hope this is useful to other folk.

Yuri

ycsapo wrote:
> Hi all,
> 
> I wonder if anyone has any idea what error 1006 means in:
> 
> iscsid: detected iSCSI connection (handle 0xf7d16600) error (1006) state (3)
> 
> This shows up in messages whenever I try to mkfs a volume on an SAN
> connected via iSCSI. This is my setup:
> 
> My server (called screms) is a Dell PE1650 running Debian testing
> (etch), kernel 2.6.15-1-686-smp, open-iscsi 1.0-485 as provided by the
> official kernel package.
> 
> The Dell connects to the SAN through its builtin Gig-ethernet NIC (Intel
> PRO/1000). This NIC is connected to a Cisco switch which connects to the
> SAN through one of its Gig-ethernet fiber ports. The SAN is built by
> Hitachi around a McData switch which has 2 fiber-channel and 2 fiber
> ethernet iSCSI ports.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
terry white | 15 Oct 2006 18:23
Favicon

possible SMTP attack: command=HELO/EHLO, count=3 (fwd)


... ciao:

    i'm starting to see a lot of the following.

    and i'm not thinking it a good thing ...

muedsl-82-207-247-115.citykom.de [82.207.247.115]: possible SMTP attack:
command=HELO/EHLO, count=3
IGLD-83-130-135-36.inter.net.il [83.130.135.36]: possible SMTP attack:
command=HELO/EHLO, count=3
bzq-88-153-185-136.red.bezeqint.net [88.153.185.136]: possible SMTP attack:
command=HELO/EHLO, count=3
bzq-88-152-204-198.red.bezeqint.net [88.152.204.198]: possible SMTP attack:
command=HELO/EHLO, count=3
89.1.170.41.dynamic.barak-online.net [89.1.170.41]: possible SMTP attack:
command=HELO/EHLO, count=3

--

-- 
... i'm a man, but i can change,
    if i have to , i guess ...

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 9 comments |
headers
Adrian C. | 15 Oct 2006 20:40

Re: possible SMTP attack: command=HELO/EHLO, count=3 (fwd)


Welcome to the real world :)

No really, have RBL checking w/ or w/o spamassassin and 
you're ok. If you don't use SMTP AUTH disable that too.

--Adrian C.

terry white wrote:
> ... ciao:
> 
>     i'm starting to see a lot of the following.
> 
>     and i'm not thinking it a good thing ...
> 
> 
> muedsl-82-207-247-115.citykom.de [82.207.247.115]: possible SMTP attack:
> command=HELO/EHLO, count=3
> IGLD-83-130-135-36.inter.net.il [83.130.135.36]: possible SMTP attack:
> command=HELO/EHLO, count=3
> bzq-88-153-185-136.red.bezeqint.net [88.153.185.136]: possible SMTP attack:
> command=HELO/EHLO, count=3
> bzq-88-152-204-198.red.bezeqint.net [88.152.204.198]: possible SMTP attack:
> command=HELO/EHLO, count=3
> 89.1.170.41.dynamic.barak-online.net [89.1.170.41]: possible SMTP attack:
> command=HELO/EHLO, count=3
> 
> 

-
(Continue reading)

Permalink | Reply | 0 comments |
headers
Glynn Clements | 16 Oct 2006 09:48

Re: possible SMTP attack: command=HELO/EHLO, count=3 (fwd)


terry white wrote:

>     i'm starting to see a lot of the following.
> 
>     and i'm not thinking it a good thing ...
> 
> 
> muedsl-82-207-247-115.citykom.de [82.207.247.115]: possible SMTP attack:
> command=HELO/EHLO, count=3
> IGLD-83-130-135-36.inter.net.il [83.130.135.36]: possible SMTP attack:
> command=HELO/EHLO, count=3
> bzq-88-153-185-136.red.bezeqint.net [88.153.185.136]: possible SMTP attack:
> command=HELO/EHLO, count=3
> bzq-88-152-204-198.red.bezeqint.net [88.152.204.198]: possible SMTP attack:
> command=HELO/EHLO, count=3
> 89.1.170.41.dynamic.barak-online.net [89.1.170.41]: possible SMTP attack:
> command=HELO/EHLO, count=3

Nothing worth worrying about. If you run your own inbound mail server,
it will inevitably be subjected to various attacks.

The above indicates that a client sent 3 or more HELO/EHLO commands
(which shouldn't occur in normal use), so sendmail has started
throttling the connection.

Once a command is issued too many times, sendmail adds a delay to each
command that it processes. The delay starts at one second then doubles
with each subsequent command, up to a maximum of four minutes. This
prevents you getting DoS'd by brute-force attacks.
(Continue reading)

Permalink | Reply | 1 comment |
headers
terry white | 16 Oct 2006 16:27
Favicon

Re: possible SMTP attack: command=HELO/EHLO, count=3 (fwd)

... ciao:

: on "10-16-2006" "Glynn Clements" writ:

: If you run your own inbound mail server
: ... (which shouldn't occur in normal use)
: ... I'm not entirely sure what an attacker can achieve

    neither could i.  but then, when i think sendmail, bane and existence
come to mind.  i've run sendmail as an mx for a little over four years,
and have 'never' seen this sort of alert.

    let's hope it's 'much ado about noting' ...

--

-- 
... i'm a man, but i can change,
    if i have to , i guess ...

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |

Gmane