zzz
orignal, still have ack block problems from your router
zzz
looks a little different now
zzz
here's an example
zzz
06-12 07:14:54.163 WARN [ handler 1/1] outer.transport.udp.PeerState2: Bad ACK block
zzz
ACK 72-61 NACK 60 ACK 59--5
zzz
Ack through 72 acnt 11 ranges:
zzz
00000000 01 41 |.A |
zzz
you're acking down to packet -5
zzz
working on relay testing on testnet today
zzz
found an NPE already
orignal
so why is it a problem?
orignal
or I see
orignal
-5 not 5
orignal
the problem bascially is I try to ack everything in last range
orignal
will check that part
zzz
right, you are acking beyond 0
orignal
yes I'm checking
zzz
:)
zzz
I'm chasing relay signature validation failures on testnet
orignal
yes, I see the problem
orignal
now
zzz
making good progress on testnet, fixed at least half a dozen bugs so far
orignal
also wanted to ask about padding size
orignal
how much do you set? up to full packet?
zzz
right now just random 0-32 bytes, but we haven't made any final decisions
orignal
I think we can make it up to MTU
orignal
because no differnce between 100 bytes packet and 1K packet
zzz
it's still bandwidth
orignal
how?
orignal
you need a full packet for 100 bytes
zzz
sure but a 1K packet still takes longer to send than a 100 byte packet and your ISP will count it as 10x bigger
orignal
why it's longer?
zzz
it's still a serial transport, whether ethernet, or DSL, or cable or fiber. more bits = longer
zzz
ISPs do accounting by byte, not by packet
orignal
maybe
zzz
w00t, first successful relay on testnet, took me all day
orignal
great