Office friend still can't ping me. The campus friend can ping me but can't reach my website. I never trusted campus friend to be on a clean network so it's a bit fruitless to test his connection.
My ISP's equipment is entirely a modem right now, bridging straight to my pfsense router. It's not doing any weird filtering.
Here are the results of those from office friend
Server: unifi.localdomain
Address: 192.168.0.1
Non-authoritative answer:
Name: drkt.eu
Addresses: 2a05:f6c7:8039::1337
89.150.135.135
Tracing route to drkt.eu [89.150.135.135]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms unifi.localdomain [192.168.0.1]
2 1 ms <1 ms <1 ms 5.186.33.65.static.fibianet.dk [5.186.33.65]
3 4 ms 4 ms 3 ms 89.150.66.104
4 4 ms 4 ms 4 ms ae2.core01-tkbg.bb.fibianet.dk [89.150.64.25]
5 * * * Request timed out.
6 3 ms 3 ms 3 ms 89.150.69.66
7 2 ms 4 ms 2 ms 217.74.211.104
8 3 ms 4 ms 4 ms 194.182.97.132
9 4 ms 4 ms 3 ms ae22-0.khk7nqp7.dk.ip.tdc.net [195.215.109.46]
10 4 ms 4 ms 4 ms ae1-0.khk7nqp8.dk.ip.tdc.net [83.88.12.15]
11 3 ms 4 ms 4 ms cpe.ae20-0.khk7nqp8.dk.customer.tdc.net [87.61.121.169]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
* Rebuilt URL to: https://drkt.eu/
* Trying 89.150.135.135...
* TCP_NODELAY set
* connect to 89.150.135.135 port 443 failed: Timed out
* Failed to connect to drkt.eu port 443: Timed out
* Closing connection 0
curl: (7) Failed to connect to drkt.eu port 443: Timed out
UPDATE
Office friends pinged me 4 times, all timed out on his end. His IP showed up in my state table and I captured these 2 packets
State table:
Interface Protocol Source -> Destination State Packets Bytes
WAN icmp 5.186.33.87:1 -> 89.150.135.135:1 0:0 4 / 4 240 B / 240 B
Packet capture: (the only 2, despite the 4 pings, and they have bad checksums?) All 8 expected packets show up but all do have bad checksums. I'm seeing a LOT of bad checksums. A known working connection from fourth friend did not show bad checksums in this same test.
5.186.33.87 > 89.150.135.135: ICMP echo request, id 1, seq 43476, length 40
12:38:19.843890 d0:50:99:81:48:17 > 4c:6d:58:4a:97:d4, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 21715, offset 0, flags [none], proto ICMP (1), length 60, bad cksum 0 (->1dc0)!)
89.150.135.135 > 5.186.33.87: ICMP echo reply, id 1, seq 43476, length 40
12:38:20.219177 d0:50:99:81:48:17 > 4c:6d:58:4a:97:d4, ethertype IPv4 (0x0800), length 43: (tos 0x0, ttl 64, id 32958, offset 0, flags [none], proto ICMP (1), length 29, bad cksum 0 (->3f6d)!)
He went to my domain while I was collecting packets from ANY protocol filtering his IP It's a bit long, so here's the cap file https://u.drkt.eu/iiUsH7.cap