Alright just when you think you are a pro, I am a bit puzzled: I am trying to deploy a new gateway. The router runs tomato shibby firmware with DMZ pointed to 192.168.1.44, the ampr-gw. When I run tcpdump I see the rip announcements and my route table is populating, but I don't see my test pings, etc coming from the general internet (and there is a dns entry) Do you have to set a special ip rule vs if the wan interface is an outside IP. I have a tried a few things that I thought made sense with no luck. Could someone who is also behind nat share their start script with me? I guess I need to build a gateways with different hardware more often. Thanks 11:50:01.034204 IP (tos 0x0, ttl 49, id 11797, offset 0, flags [none], proto IPIP (4), length 552) 169.228.34.84 > 192.168.1.44: IP (tos 0x0, ttl 255, id 0, offset 0, flags [none], proto UDP (17), length 532) 44.0.0.1.520 > 224.0.0.9.520: [no cksum] RIPv2, Response, length: 504, routes: 25 or less Simple Text Authentication data: pLaInTeXtpAsSwD. AFI IPv4, 44.151.62.1/32, tag 0x0004, metric: 1, next-hop: 88.161.142.195 AFI IPv4, 44.151.67.67/32, tag 0x0004, metric: 1, next-hop: 78.226.112.146 AFI IPv4, 44.151.67.100/32, tag 0x0004, metric: 1, next-hop: 77.202.52.153 AFI IPv4, 44.151.67.101/32, tag 0x0004, metric: 1, next-hop: 82.231.84.133 AFI IPv4, 44.151.69.52/32, tag 0x0004, metric: 1, next-hop: 78.193.255.113 AFI IPv4, 44.151.74.102/32, tag 0x0004, metric: 1, next-hop: 151.80.196.50 AFI IPv4, 44.151.75.15/32, tag 0x0004, metric: 1, next-hop: 82.251.146.223 AFI IPv4, 44.151.77.1/32, tag 0x0004, metric: 1, next-hop: 89.92.44.3 AFI IPv4, 44.151.91.7/32, tag 0x0004, metric: 1, next-hop: 90.63.239.151 AFI IPv4, 44.151.91.12/32, tag 0x0004, metric: 1, next-hop: 90.63.239.151 AFI IPv4, 44.151.91.13/32, tag 0x0004, metric: 1, next-hop: 90.63.239.151 AFI IPv4, 44.151.91.45/32, tag 0x0004, metric: 1, next-hop: 91.160.176.199 AFI IPv4, 44.151.92.10/32, tag 0x0004, metric: 1, next-hop: 78.123.177.245 AFI IPv4, 44.151.92.21/32, tag 0x0004, metric: 1, next-hop: 213.41.152.199 AFI IPv4, 44.151.95.10/32, tag 0x0004, metric: 1, next-hop: 78.225.88.39 AFI IPv4, 44.151.127.1/32, tag 0x0004, metric: 1, next-hop: 217.182.129.131 AFI IPv4, 44.151.240.66/32, tag 0x0004, metric: 1, next-hop: 91.176.67.16 AFI IPv4, 44.153.0.0/23, tag 0x0004, metric: 1, next-hop: 186.124.165.82 AFI IPv4, 44.153.32.97/32, tag 0x0004, metric: 1, next-hop: 190.105.83.232 AFI IPv4, 44.153.35.0/24, tag 0x0004, metric: 1, next-hop: 190.105.83.232 AFI IPv4, 44.153.52.6/32, tag 0x0004, metric: 1, next-hop: 209.13.176.78 AFI IPv4, 44.153.54.0/28, tag 0x0004, metric: 1, next-hop: 190.97.49.15 AFI IPv4, 44.153.54.16/30, tag 0x0004, metric: 1, next-hop: 190.97.49.15 AFI IPv4, 44.153.54.20/32, tag 0x0004, metric: 1, next-hop: 190.1.38.237 0x0000: 0202 0000 ffff 0002 704c 6149 6e54 6558 0x0010: 7470 4173 5377 4400 0002 0004 2c97 3e01 0x0020: ffff ffff 58a1 8ec3 0000 0001 0002 0004 0x0030: 2c97 4343 ffff ffff 4ee2 7092 0000 0001 0x0040: 0002 0004 2c97 4364 ffff ffff 4dca 3499 0x0050: 0000 0001 0002 0004 2c97 4365 ffff ffff 0x0060: 52e7 5485 0000 0001 0002 0004 2c97 4534 0x0070: ffff ffff 4ec1 ff71 0000 0001 0002 0004 0x0080: 2c97 4a66 ffff ffff 9750 c432 0000 0001 0x0090: 0002 0004 2c97 4b0f ffff ffff 52fb 92df 0x00a0: 0000 0001 0002 0004 2c97 4d01 ffff ffff 0x00b0: 595c 2c03 0000 0001 0002 0004 2c97 5b07 0x00c0: ffff ffff 5a3f ef97 0000 0001 0002 0004 0x00d0: 2c97 5b0c ffff ffff 5a3f ef97 0000 0001 0x00e0: 0002 0004 2c97 5b0d ffff ffff 5a3f ef97 0x00f0: 0000 0001 0002 0004 2c97 5b2d ffff ffff