Hi Chaley
Thanks for getting back to me, really is appreciated.
I will answer your questions so that we can try to resolve this:
Quote:
|
Are TCP connections to port 9091 allowed through your firewall?
|
Yes, I had opened up that on the linux machine. *** At the moment my firewall on the laptop is down completely:
Code:
ant@localhost ~ % sudo ufw status
Status: inactive
Quote:
|
Does your home router have any filtering set up?
|
Not as far as I'm aware. Using a mikrotik router, but the entire setup is working in bridge mode, as in the whole lan should not be filtered or anything, all comms are allowed to pass. I went as far as disabling all the rules on the mikrotik, still to no avail.
Quote:
|
What happens if you turn off the content server in calibre then change the WD port to 8080?
|
Tried this, and it's currently on that port setting; not working.
Quote:
|
Do you have any intrusion detection software running on your Linux box?
|
No, I've installed nothing on this machine, no snort etc etc.
Quote:
|
I note from your tcpdump that port 9091 is identified as xmltec-xmlmail. Do you have any sort of auto-start based on port numbers? What happens if you set the calibre WD port to something bizarre (and unassigned) such as 14802?
|
I think that's just the "standard" port numbering that is held with tcpdump. It's just resolving numbers to names. I did try on port 14802, and still nothing.
I also did a dump of a torch running on the router, it shows what's going through:
Code:
[admin@MikroTik] /tool> torch bridge src-address=192.168.88.253/32 ip-protocol=any freeze-frame-interval=8s
MAC-PROTOCOL IP-PROTOCOL SRC-ADDRESS TX RX TX-PACKETS RX-PACKETS
ip igmp 192.168.88.253 0bps 0bps 0 0
ip udp 192.168.88.253 0bps 824bps 0 1
ipv6 udp 0bps 0bps 0 0
0bps 824bps 0 1
-- [Q quit|D dump|C-z continue]
This next one is from the linux machine, and seems to show that the data is coming through:
Code:
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
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