amprgw has a filter in it that only allows traffic to hosts that
are in the DNS. 44.131.56.1 is there; 44.131.56.2 is not, so pings
and other traffic to 44.131.56.2 will not be forwarded.
- Brian
On Sat, Nov 15, 2014 at 09:02:09AM -0000, John Wiseman wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Hi folks.
I'm adding a rip44 processor and ipip tunnel support to my BPQ32/LinBPQ
networking software.
I've set up an encap entry for 44.131.56.0/27 and I receive the block of
RIP44 messages every 5 minutes, and random packets addressed to 44.131.56.1,
presumably from network scanners. If I ping 44.131.56.1 from a normal
internet host I also see the encapsulated packets. So far so good. But if I
try pinging any other address in my subnet, I don't get anything. I'd expect
amprgw to send me packets for any address in my subnet.
Am I misunderstanding how amprgw is supposed to work?
Thanks,
John G8BPQ
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net