It’s not rocket science. Either:
radiusd is not running on the ip and port in question, or something is blocking the packets from reaching the radiusd process (hint: iptables), or radiusd is ignoring the packets (hint: run radius in debug mode). Regards, -- Louis Munro lmu...@inverse.ca :: www.inverse.ca +1.514.447.4918 x125 :: +1 (866) 353-6153 x125 Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) > On Apr 4, 2016, at 12:39 , TOURE Amidou Florian <amidouflorianto...@yahoo.fr> > wrote: > > Yes Sir I can ping the radius server from my switch , I can also ping my > Windows Server machine from the switch. > tcpdumd host "the ip address of the switch " shows me this output,but after > this nothing except the errors that i see in the sh logging of the switch ( > RADIUS: Marking server 192.168.10.1:1812,1813 dead),Thanks: > > 09:33:43.667746 IP 192.168.1.5.radius > 192.168.10.1.radius: RADIUS, Access > Request (1), id: 0x0a length: 162 > 09:33:45.667601 IP 192.168.1.5.radius > 192.168.10.1.radius: RADIUS, Access > Request (1), id: 0x0a length: 162 > 09:33:47.667509 IP 192.168.1.5.radius > 192.168.10.1.radius: RADIUS, Access > Request (1), id: 0x0a length: 162 > 09:33:49.667856 IP 192.168.1.5.radius > 192.168.10.1.radius: RADIUS, Access > Request (1), id: 0x0a length: 162 >
------------------------------------------------------------------------------
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
