Hello Scott, AFAIK, you always need public addresses for both ends of an IPv6 tunnel, because they are included in the payload as part of the protocol. This means your IPv6 network would have to be connected to the SMC and this router would have to support IPv6 tunneling.
For normal Internet access I don't think you'll have any problems. Basically the address re-writing and port forwarding that allows NAT to work should make each NAT "invisible" to the other. MAC address filtering is a really weak security measure for WiFi, but it's also a very common feature in cable/ADSL routers. Are you sure the SMC one doesn't support it? HTH, André On Jul 10, 2011, at 11:06 PM, Scott Howell wrote: > All, > > Here is the situation. I recently switched to Comcast business class. I was > provided with a SMC Network cable modem. THis box is actually a switch > consisting of four ports. Currently I have my AirPort router plugged into the > SMC and thus I have a double nat situation. THe SMC is configured to handout > DHCP addresses, which is how my AirPort gets its address, but I also am > handing out addresses using DHCP to the devices on my private network. I > actually am using DHCP reservations and for a specific reason. > I have setup mac address filtering to control certain machines on the > network. Unfortunately the SMC lacks some of the features for controlling > machines that are found in the Apple router. However, this double nat > situation can and has created some issues for me. I could of course just > bridge the AirPort and give up the whole deal on controlling machines on the > network. That may very well end up being necessary in the end; however, > before I do so, I wanted to ask if anyone had any thoughts. I did a little > searching around on Google, but unfortunately I'm not sure exactly what to > look for either. I don't think Google would take my message as a search term > either. :) > Although I do not have any plans to do this, the advantage of double nat in > this case is I could strap three more routers onto the gateway (SMC) and have > some fun. Now maybe there is a way around all of this, but seems the current > issue is IP6 tunneling, but I am more concerned if this could pose problems > with other services. So, thoughts welcome and I'll keep poking around and see > what I can learn. The good thing is that all seems to be working for the most > part, so this is not a critical need situation. Just need to make sure I can > vpn into the network at the office. :) > > Thanks, > Scott > > -- > You received this message because you are subscribed to the Google Groups > "MacVisionaries" group. > To post to this group, send email to macvisionaries@googlegroups.com. > To unsubscribe from this group, send email to > macvisionaries+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/macvisionaries?hl=en. > -- You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To post to this group, send email to macvisionaries@googlegroups.com. To unsubscribe from this group, send email to macvisionaries+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/macvisionaries?hl=en.
