Christian Magnusson [EMAIL PROTECTED] wrote:
I think it listens on 127.0.0.1:5005 as default if you only type
-p 5005, that makes owserver unreachable for remote hosts. Then
you have to connect with owhttpd -p 8080 -s 127.0.0.1:5005
OK, now a run into another Problem with owtcl:
tclsh8.4
No change was intended. Sounds like a new bug.
Paul
On Sunday 31 July 2005 06:35 am, Sven Geggus wrote:
Christian Magnusson [EMAIL PROTECTED] wrote:
You might need to bind owserver to listen on all addresses such as
owserver -u -p 0.0.0.0:5005
owhttpd -p 8080 -s 5005
Hm, I did not
On Sunday 31 July 2005 03:27 pm, Paul Alfille wrote:
No change was intended. Sounds like a new bug.
Paul
On Sunday 31 July 2005 06:35 am, Sven Geggus wrote:
Christian Magnusson [EMAIL PROTECTED] wrote:
You might need to bind owserver to listen on all addresses such as
owserver -u
I think I found the problem.. I have probably been tired or something
when adding a row in ow_net.c which clears AI_PASSIVE.
The cvs is unreachable for me right now, so could somebody
else checkin the patch later?
diff --exclude '*Entries' -ruw cvs/owfs/module/owlib/src/c/ow_net.c
On Sun, 2005-07-31 at 21:57, Paul Alfille wrote:
On Sunday 31 July 2005 03:27 pm, Paul Alfille wrote:
No change was intended. Sounds like a new bug.
Paul
On Sunday 31 July 2005 06:35 am, Sven Geggus wrote:
Christian Magnusson [EMAIL PROTECTED] wrote:
You might need to bind
