Hi Lynwood,
My ISP (or RSP as they're known here now) is a company called TPG. They're one of the largest in the country. I am both sending and receiving ipencap just fine from what I can see, here's a capture of a ping through my gateway to 44.88.0.9: 12:00:18.839944 IP 192.168.1.2 > 24.34.225.54: IP 44.136.24.2 > 44.88.0.9: ICMP echo request, id 9, seq 0, length 80 (ipip-proto-4) 12:00:19.130214 IP 24.34.225.54 > 192.168.1.2: IP 44.88.0.9 > 44.136.24.2: ICMP echo reply, id 9, seq 0, length 80 (ipip-proto-4) 12:00:19.161423 IP 192.168.1.2 > 24.34.225.54: IP 44.136.24.2 > 44.88.0.9: ICMP echo request, id 9, seq 1, length 80 (ipip-proto-4) 12:00:19.451597 IP 24.34.225.54 > 192.168.1.2: IP 44.88.0.9 > 44.136.24.2: ICMP echo reply, id 9, seq 1, length 80 (ipip-proto-4)
My vdsl modem is a Huawei HG659b. The modem routes all DMZ traffic to an interface on a Broadcom based AP running OpenWRT via a cisco WS-C3750g-24PS. I can see all manner of connections hitting my DMZ interface from my public IP (typical portscans etc) so the modem->DMZ forwarding seems ok. My gateway has an address from my 44 subnet on its tunnel interface, and another on an ethernet port that connects to my switch's vlan 44. I can connect to and from other tunnels from my gateway, my switch's vlan44 interface and from other devices connected to vlan 44.
Josh - VK2HFF
On 16/06/2017 11:30 AM, lleachii--- via 44Net wrote:
Josh,
I'm more than happy to see if you are sending IPENCAP (IP Protocol No. 4)...but you're not receiving...
Let's first make sure:
- Who is your ISP?
- Let's make sure you're receiving IPENCAAP (IP Protocol No. 4)
- What's the make and model of router?
- how are your configuring your device to receive IPENCAP and
processes them?
If you WERE receiving them and they disappeared, did you (or your ISP) make any known changes?
- Lynwood
KB3VWG
You may want to read my white page about being bitten by the dog.
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net