* [9fans] Announce and Sockets
@ 1998-12-09 17:45
0 siblings, 0 replies; 3+ messages in thread
From: @ 1998-12-09 17:45 UTC (permalink / raw)
When I use announce:
announce("tcp!143.106.24.121!9877", adir);
term% netstat
tcp 0 nojento Listen 143 0 0.0.0.0
The question is: Why the port used is always 143? Because with this
problem, I have to use dial ("tcp!143.106.24.121!143", 0, devdir, 0).
And
this problem is extended to sockets: I have a program, that use sockets,
that works on Linux and don't work on Plan 9. Because:
server: socket() - bind() - listen() - accept() - read() - write() -
read() - close()
client: socket() - connect()
-write() - read - close()
The client have to connect to server, and it's don't occur.
Franklin.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [9fans] Announce and Sockets
@ 1998-12-09 23:11 forsyth
0 siblings, 0 replies; 3+ messages in thread
From: forsyth @ 1998-12-09 23:11 UTC (permalink / raw)
>>announce("tcp!143.106.24.121!9877", adir);
>>The question is: Why the port used is always 143? Because with this
use
announce("tcp!*!9877", adir)
because /sys/src/9/port/devip.c is misinterpreting
the ip address as a port number (note that your ip address starts with 143!).
i was a bit confused because my own copy of the source has this fixed/changed
for some reason (perhaps it came with beto's multicast changes).
by using "*" in the host part, cs will produce just the port
number for announce to give to the driver.
i don't think the documentation makes it clear.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [9fans] Announce and Sockets
@ 1998-12-09 16:53
0 siblings, 0 replies; 3+ messages in thread
From: @ 1998-12-09 16:53 UTC (permalink / raw)
When I use announce:
announce("tcp!143.106.24.121!9877", adir);
term% netstat
tcp 0 nojento Listen 143 0 0.0.0.0
The question is: Why the port used is always 143? Because with this
problem, I have to use dial ("tcp!143.106.24.121!143", 0, devdir, 0). And
this problem is extended to sockets: I have a program, that use sockets,
that works on Linux and don't work on Plan 9. Because:
server: socket() - bind() - listen() - accept() - read() - write() - read
() - close()
client: socket() - connect() -
write() - read - close()
The client have to connect to server, and it's don't occur.
Franklin.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~1998-12-09 23:11 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1998-12-09 17:45 [9fans] Announce and Sockets
-- strict thread matches above, loose matches on Subject: below --
1998-12-09 23:11 forsyth
1998-12-09 16:53
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).