search for: tcp46

...that fail to do so and rely on the old IPv4 mapped addresses will end up handling IPv6 only. Symptoms on typical IPv6-enabled but only IPv4-connected hosts are that the daemon appears to be running fine but can't be reached. netstat -a will show a protocol type of tcp6 instead of the expected tcp46. Workarounds for IPv4-only users include specifying an appropriate --address or building rsync with --disable-ipv6. Currently, rsync in daemon mode is only designed to read from a single socket. Extending this to two sockets will require a bit of reworking, e.g. introducing a select(2) loop. Th...

When rsync starts I get the following messages in my log file Jan 11 11:00:04 WEB1 rsyncd[31281]: rsync: bind failed on port 873 Jan 11 11:00:04 WEB1 rsyncd[31281]: rsync error: error in socket IO (code 10) at socket.c(361) Anybody know what might be causing this? David

...*.* > LISTEN >tcp4 0 0 localhost.locald.8005 *.* > LISTEN >tcp4 0 0 *.9008 *.* > LISTEN >tcp4 0 0 *.8009 *.* > LISTEN >tcp46 0 0 *.https *.* > LISTEN >tcp46 0 0 *.http *.* > LISTEN >tcp4 0 0 *.9080 *.* > LISTEN >tcp4 0 0 *.8180 *.*...

Dear W.D. Do you understand that by adding the rules into kernel space numbered from zero to sixty five thousand five hundred thirty four you may alter the behavior of the rule number sixty five thousand five hundred thirty five can you please define and list the goals you are trying to achieve by altering default rule in the terms you can both explain and understand. ----- Original Message

Hi peeps, After compiling ipfw into the new 6.2 kernel, and typing "ipfw list", all I get is: "65535 deny ip from any to any" From reading the docs, this might indicate that this is the default rule. (I am certainly protected this way--but can't be very productive ;^) ) By the way, when I run "man ipfw" I get nothing. Using this instead: