Hi Alan,

Thanks for the response. My original email was very lengthy, but at the bottom you can see a wireshark capture showing the packet arrival. (My understanding is wireshark is a pretty GUI based on tcpdump)

What is strange is I tried to do the test in the reverse direction and it works i.e.

10.10.10.11 = radisusd server <=== 10.10.10.10 = radtest client

Does not work

10.10.10.11 = radtest client ===> 10.10.10.10 = radiusd server 

Works

The host 10.10.10.11 is running 32 bit OpenSuse 11.1

while host 10.10.10.10 is running 64bit OpenSuse 11.1

I have fallen back to default install with only the following files [edits users & clients.conf] (to reflect the opposite endpoints)

So far the 32 bit machine appears to be silently dead as far as radiusd

Date: Sat, 7 Mar 2009 19:29:05 +0000

From: A.L.M.Buxey@lboro.ac.uk

Subject: Re: radiusd server does not respond to radtest from another

    host

To: FreeRadius users mailing list

    <freeradius-users@lists.freeradius.org>

Message-ID: <20090307192905.GA28192@lboro.ac.uk>

Content-Type: text/plain; charset=us-ascii

Hi,

> Next I tried testing radiusd using radtest from a 2nd host (10.10.10.10), 

which I had added previously added to the clients.conf (Note I can successfully 

ping the radius server 10.10.10.11 from this 2nd host 10.10.10.10).?But, I get 

no response from radius acc-request on either the radiusd terminal window or the 

radtest terminal window.

just like another current thread - have a couple of terminal windows

opn.

in one, run

tcpdump -eqnnntl -i eth0 port 1812  (change eth0 if necessary)

in the other, run

radiusd -X

now, run the test.  does anything show packets?  have you enabled

the firewall to allow port 1812 inbound from 10.10.10.10? 

alan