It's taken me over a year, but I was FINALLY able to get IPv6 working with my Comcast connection through the Zywall USG 20W. Well, at least I can visit IPv6 Web sites anyway; baby steps, right? I don't even know if I'll try to get my "servers" (including a web server) accessible via IPv6 for awhile. The web server is on a VM installed over top WinXP so I tend to think I should just wait until I'm able to update the hardware/OS anyway.
Because I don't fully understand the security precautions I should be taking or really what I've done, I thought I'd ask if there is anything security-wise I should be careful with while I try to delve into all this and continue to learn more about it. Right now the firewall rules I have in place are just the default ones on the 20W and I'm hoping they're good enough until I need to start learning how to make my server programs available to the Web. I'm a bit worried about people being able to access the router via the WAN but can't really wrap my head around what I'd need to do to ensure it's not accessible in this manner. I have config -> system -> www -> service control set to accept http and https connections only via tunnel, lan1 and lan2. I assume these settings will keep connections via WAN (except in the case of VPN) at bay as they always have with IPv4, regardless of firewall rules?
Any helpful thoughts? I was pretty excited to finally get just this far. Comcast gave me a /64 and so far I'm reading that's not the best thing for people who are running things like web servers because it's difficult to subnet in order to keep internal server computers apart from other computers on the LAN which shouldn't be accessible from the Web. But I know SO LITTLE about such things. There's also a setting under my WAN1 IPv6 interface called "request address" that I can't figure out a meaning for. It seems to assign an IPv6 subnet to the WAN interface itself, maybe? But whether I apply the setting or not I am still able to access IPv6 Web pages through the router.
↧