battleop
join:2005-09-28
00000
| Canopy SM NAT Can't pass traffic.
I went out today to turn up a customer who is using a Canopy 9000SMC. The business has only 1 PC and no router. I decided to turn the SM into a router. I turned on NAT, rebooted the radio and renewed the IP on the PC. The PC picks up a DHCP address and I can ping the radio and access the web interface. I can't ping the public IP on the WAN side.
Using my Verizon card I can get into our network and access the radio from the out side. If I disable NAT and use the radio as a bridge I can surf with out a problem.
Am I missing something?
BTW I can ping both interfaces from the CLI in the radio. |
|
hattmardy
join:2007-01-23
Atlanta, GA | Is the DHCP server handing out the correct gateway address (in this case the IP of the Canopy SM)?
-Matt |
|
Believer
join:2002-07-04
Baltimore, MD | What software version of the radio are you using? We've seen odd DHCP issues with the current version of the software.
--
Comtrain Certified Tower Climber |
|
battleop
join:2005-09-28
00000
| reply to hattmardy
The PC and my laptop got the correct ip and gateway from the radio. Here is some info from the CLI that does not match up to what is in the radio.
Software Version : CANOPY 8.2.1 SM-DES
Software BOOT Version : CANOPYBOOT 1.0
Board Type : P10
FPGA Version : 092707
PLD Version : 9
Telnet+> ip
IP (1) addr: 169.254.1.1 This is the LAN side gatway.
IP (2) addr: 192.168.101.2 I don't know where this IP is coming from.
Telnet+> ipconfig
Lan 1 Interface
MAC: 0a-00-3e-93-6c-95
IP Address: 169.254.1.1
Net Mask: 255.255.255.0
Default Gateway: 69.x.x.238 This is the GW at the AP
DHCP Status: Disabled
RF Public Network Interface - Valid only with NAT Enable with Public Addressing.
IP Address: 69.x.x.228
Net Mask: 255.255.255.240
Default Gateway: 69.x.x.238
DHCP Status: Disabled |
|
hattmardy
join:2007-01-23
Atlanta, GA
| 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. |
|
joshg409
join:2005-05-03
Ottumwa, IA
| reply to battleop
That would be my guess, the point of the 169 block on the radio is so that it should never conflict with other devices on the network when first turned on. Change the IP of the private network and then release renew IP and see what happens.
Or default plug the radio and start over. |
|
battleop
join:2005-09-28
00000 | I had the same problem when the radio had 192.168.1.0/24. |
|
