hattmardy
Premium
join:2007-01-23
Atlanta, GA
| reply to battleop
Re: Canopy SM NAT Can't pass traffic.
Why are you using the 169.254.x.x address range?
From wikipedia:
A second set of private networks is the link-local address range codified in RFC 3330 and RFC 3927. The intention behind these RFCs is to provide an IP address (and by implication, network connectivity) without a DHCP server being available and without having to configure a network address manually. The network 169.254/16 has been reserved for this purpose. Within this address range, the networks 169.254.0/24 and 169.254.255/24 have been set aside for future use.
Link-local addresses have even more restrictive rules than the private network addresses defined in RFC 1918: packets to or from link-local addresses must not be allowed to pass through a router at all (RFC 3927, section 7).
Maybe this is related? Could you try a standard private IP subnet?
I'm not sure why Telnet+> ip is showng 2 different IPs though 
-Matt |
|
battleop
join:2005-09-28
00000
| I started out with 192.168.1.x. To trouble shoot I set the radio up as a bridge to make sure I could pass traffic. When I turned NAT back on I used the default address that the radio will use.
I can't see any reason why using 169.254.x.x would keep me from pinging the out side interface of the radio. |
|
