is dnswl dead?

Mailman List Mirror (Read Only)
1

% /usr/local/bin/rsync --times rsync2.dnswl.org::dnswl/bind-dnswl-nons.zone /var/dns/primary/org.dnswl
rsync: read error: Connection reset by peer (54)
rsync error: error in socket IO (code 10) at io.c(785) [Receiver=3.1.3]

this has been going on for a while. admins do not respond to email.
and yes, i paid.

would be a bummer. was useful.

randy

2

Hi

List files:

rsync rsync2.dnswl.org::dnswl

Try exactly this command

BIND: rsync --times rsync2.dnswl.org::dnswl/bind-* /some/path/
3

And check first connectivity ping and telnet tcp ports 22 , 873 to ips destination’s from your linuxbox:

Record A rsync2.dnswl.org
139.162.192.198

142.44.243.216

Or use in the command directly the ip.
You are behinds a router, proxy , Nat device. May cause problems or deny filter traffic. If share a Wireshark capture will see what’s happens …

4

List files:
rsync rsync2.dnswl.org::dnswl

sorry. i am a little confused. are you trying to tell me how to use
rsync or that dnswl is not broken for you?

i am an rsync addict, and i still fear dnswl is broken.

# rsync rsync2.dnswl.org::dnswl
rsync: read error: Connection reset by peer (54)
rsync error: error in socket IO (code 10) at io.c(785) [Receiver=3.1.3]

randy

5

/subscribe

6

rsync gets through the 3-packet handshake, and then about 20 packets
ending thusly:

11:34:52.749962 IP 192.168.1.73.42138 > 139.162.192.198.rsync: Flags [.], ack 32, win 502, options [nop,nop,TS val 3218474733 ecr 1658500094], length 0
11:34:52.750309 IP 192.168.1.73.42138 > 139.162.192.198.rsync: Flags [P.], seq 79:87, ack 32, win 502, options [nop,nop,TS val 3218474733 ecr 1658500094], length 8
11:34:52.851104 IP 139.162.192.198.rsync > 192.168.1.73.42138: Flags [.], ack 87, win 227, options [nop,nop,TS val 1658500119 ecr 3218474733], length 0
11:34:53.162604 IP 139.162.192.198.rsync > 192.168.1.73.42138: Flags [R.], seq 32, ack 87, win 227, options [nop,nop,TS val 1658500197 ecr 3218474733], length 0

The far end tosses an ACK for the packet, and then an ACK/RST rather than a FIN.
Rather anti-social - usually indicative of the daemon at the far end crashing and
closing the socket.

(Side note - is it me, or does the rsync dissector for wireshark do a less than optimal job?)

(And yes, I know for a fact that my router doesn't bork rsync, as it works
for other stuff on a regular basis..)