Hi James, The broadcasts you are seeing are RIPv2 (IPv4) not RIPng, which AFAIK is IPv6. But you are right. Unless you have a registered DNS name for a host on your subnet, it is all that you will see on that interface. After you register a host in the DNS, you will also see scans, pings and maybe hacking attempts on your network from the internet :-) But in order to reach other 44 subnets you need the mesh. You can use for testing: tunnel mode ipip tunnel destination 89.122.215.236 subnet 44.182.21.0/24 Feel free to check host 44.182.21.1 for http, telnet (node), dxcluster on tcp/8873, convers on tcp/3600 Marius, YO2LOJ -----Original Message----- From: James Sharp Sent: Sunday, May 08, 2016 00:16 To: AMPRNet working group Subject: [44net] New set up and everything (Please trim inclusions from previous messages) _______________________________________________ Hi all, I've had a /29 allocation for a while but I'm just now getting set up to try to get it working and I have a questions. My edge router is a Cisco 1811 that I've configured a single IP-IP tunnel on. interface Tunnel44 no ip address ip tcp adjust-mss 1436 tunnel source FastEthernet0 tunnel mode ipip tunnel destination 169.228.66.251 end The only traffic I see coming in on that interface is multicast (which I see as being from RIPng). Are hosts on AMPR net reachable from the public internet via the UCD gateway or is the only traffic I'll ever see from there those RIPng packets? And from what I'm guessing, packets sent to the UCD gateway don't get routed to other netblocks/allocations so I'd need to goahead and build tunnels to everyone else to get a full mesh network. Can someone give me a suggestion on netblocks to build to just to test things? Thanks, James Sharp N5XNS james(a)fivecats.org _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net