Indeed! Looks like freeradius instantiates its modules before forking.
I've postponed context/socket initialization and now everything works perfectly.
Thank you very much!
2012/7/7 Ian Barber ian.bar...@gmail.com:
On Fri, Jul 6, 2012 at 3:11 PM, Max Kuznecov m...@mek.uz.ua wrote:
Oh, sorry
I'm having a strange asymmetrical problem with tcp PUB/SUB between two boxes -
it appears to fail one way.
Details:
* zeromq version: 3.2, using the Java wrapper.
* Scenario has two machines A (Ubuntu, x64) and B (Angstrom, arm8)
* Both connected directly via wireless interface (B is acting
Try binding to * on box b
when publishing.
Joshua
Mark Sutheran
July 7, 2012 9:42
AM
I'm having a strangeasymmetricalproblem with tcp
PUB/SUB between two boxes - it appears to fail one way.Details:* zeromq version: 3.2,
using the Java wrapper.* Scenario has two
Thanks for the suggestion Joshua. Unfortunately this doesn't fix the problem.(I restricted the publisher to the one interface in order to avoid any possible confusion due topotentialrouting through some other interface)However to add to the information - the SUB on box B can successfully connect
On Sat, Jul 7, 2012 at 8:16 AM, Mark Farnan mark.far...@petrolink.comwrote:
Hi Ben,
** **
HttpS (more specifically SSL) is mandatory requirement in the Industry,
just forget trying to do anything without it that involves the Internet.
I know but you said minimal authentication , if
Ok, apols - looks like it's my bad!Rebuilt all the libs on the client box (A) to the latest and greatest and the problem went away. So I guess this was a backwards-onlycompatibilityissue between different versions (fits the pattern)Cheers,MarkFrom: Mark Sutheran mark_suthe...@yahoo.com To:
