[chaley]

Originally Posted by neural

This next one is from the linux machine, and seems to show that the data is coming through:

ant@localhost ~ % sudo tcpdump -v -nn -i wlp3s0 src 192.168.88.253 or dst 192.168.88.253
tcpdump: listening on wlp3s0, link-type EN10MB (Ethernet), capture size 262144 bytes
10:32:32.415537 IP (tos 0x0, ttl 64, id 17773, offset 0, flags [DF], proto UDP (17), length 37)
    192.168.88.253.54982 > 255.255.255.255.54982: UDP, length 9
10:32:32.416451 IP (tos 0x0, ttl 64, id 17775, offset 0, flags [DF], proto UDP (17), length 37)
    192.168.88.253.48123 > 255.255.255.255.48123: UDP, length 9
10:32:32.417921 IP (tos 0x0, ttl 64, id 17776, offset 0, flags [DF], proto UDP (17), length 37)
    192.168.88.253.39001 > 255.255.255.255.39001: UDP, length 9
10:32:32.418826 IP (tos 0x0, ttl 64, id 17777, offset 0, flags [DF], proto UDP (17), length 37)
    192.168.88.253.44044 > 255.255.255.255.44044: UDP, length 9
10:32:32.419849 IP (tos 0x0, ttl 64, id 17778, offset 0, flags [DF], proto UDP (17), length 37)
    192.168.88.253.59678 > 255.255.255.255.59678: UDP, length 9
10:32:33.011204 IP (tos 0x0, ttl 64, id 6413, offset 0, flags [DF], proto UDP (17), length 83)
    192.168.88.251.54982 > 192.168.88.253.54982: UDP, length 55
10:32:33.033724 IP (tos 0x0, ttl 255, id 2768, offset 0, flags [DF], proto UDP (17), length 79)
    192.168.88.253.5353 > 224.0.0.251.5353: 0 PTR (QM)? _calibresmartdeviceapp._tcp.local. (51)
10:32:33.036114 IP (tos 0x0, ttl 255, id 2769, offset 0, flags [DF], proto UDP (17), length 79)
    192.168.88.253.5353 > 224.0.0.251.5353: 0 PTR (QM)? _calibresmartdeviceapp._tcp.local. (51)
10:32:35.337139 IP (tos 0x0, ttl 64, id 12654, offset 0, flags [DF], proto TCP (6), length 60)
    192.168.88.253.46273 > 192.168.88.251.8080: Flags [S], cksum 0x3077 (correct), seq 3573462255, win 65535, options [mss 1460,sackOK,TS val 8226177 ecr 0,nop,wscale 8], length 0
10:32:36.369294 IP (tos 0x0, ttl 64, id 12655, offset 0, flags [DF], proto TCP (6), length 60)
    192.168.88.253.46273 > 192.168.88.251.8080: Flags [S], cksum 0x2f4a (correct), seq 3573462255, win 65535, options [mss 1460,sackOK,TS val 8226478 ecr 0,nop,wscale 8], length 0
10:32:38.245672 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.88.253 tell 192.168.88.251, length 28
10:32:38.306012 ARP, Ethernet (len 6), IPv4 (len 4), Reply 192.168.88.253 is-at 44:80:eb:1d:60:ef, length 28
10:32:38.346543 IP (tos 0x0, ttl 64, id 12656, offset 0, flags [DF], proto TCP (6), length 60)
    192.168.88.253.46273 > 192.168.88.251.8080: Flags [S], cksum 0x2cf0 (correct), seq 3573462255, win 65535, options [mss 1460,sackOK,TS val 8227080 ecr 0,nop,wscale 8], length 0
10:32:40.455618 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.88.251 tell 192.168.88.253, length 28
10:32:40.455648 ARP, Ethernet (len 6), IPv4 (len 4), Reply 192.168.88.251 is-at 34:e6:ad:b2:2d:3e, length 28

What this shows is CC's UPD "are you there" broadcasts getting through to calibre. The first 5 lines are CC trying "random" ports. The 6th line is calibre's wireless device answering. The next few lines are (I think) CC asking bonjour for an address and calibre answering. We then see two lines (plus some ARPs) where CC attempts to open a TCP connection to calibre. The connection is not created and calibre never responds. And of course that is the problem.

This is really confusing, If you have other suggestions, or what I could look at more specifically, let me know, and I will try.

Thanks

I have one more idea. There could be some IPv6 thing happening where calibre is getting confused about what interface it is listening on. The wireless device (WD) does not work with v6.

By default the WD listens on all interfaces. You can tell the WD to listen on a specific interface by going to calibre / Preferences / Plugins, searching for SmartDevice, then pressing "Customize plugin". Enter the v4 IP address of the calibre computer into the "Use this IP address" box.