Hi Ralph. Wow! You know, I'm not sure what to do for you.
My modem/router acts like it is UPnP, because I didn't have to do any port forwarding mumbo-jumbo to get it to work with iChat -- iChat just worked "out of the box" with that modem, just as it did with
the one I had before it. And I never found anything on any router configuration pages in either one of those modems to turn on UPnP or turn off UPnP. And I never had to do anything with the Mac's firewall with regards to iChat, and I can port forward ssh into the house, which allows me to securely tunnel my netcams, vnc screen sharing, afp file sharing, even my own 5-account smtp/imap mail server for family members (me, wife, and the three adult children that have gone out on their own over the past several years). So what can I say but maybe God doesn't hate me after all?
But if we know what ports are being used, or could be used for iChat, PlayStation, XBox, etc., couldn't a separate unique port be forwarded to a single computer in the presence of UPnP? I'm thinking that those X Boxes and so forth already have reserved ports on that IANA well-known port list, or be using dynamic ports higher than 49151 (which is the last port number on that list). Might have to
tcpdump -i {interface name} host {Xbox/PS's "192.168" IPA} | awk '{print $3 $5}' | sort | uniq for a little while and see what port ranges those X-boxes and Play Stations are actually using.
Or you're saying that when you try to UPnP with port forwarding, that hoses everything up in the router? I always kinda thought that the issue was trying to port forward
iChat ports then turn on UPnP then iChat went "tango uniform," not the router, and that that wasn't an issue with port forwarding a non-iChat port to peacefully coexist with UPnP. But I just don't know. All I can say is that hopefully, blufishjd's home network is way less complex than yours is!
I will have to remark WRT bluefishjd, now that I have reread this thread, that it wasn't clear to me whether he had a second ibook on his WLAN to view the webcam locally or not. I would be concerned that if he is just viewing from the evocam application, or is viewing via Safari specifying localhost or 127.0.0.1 as the target URL, that that is not a good test to see whether he does indeed have the evocam webserver part set up correctly, or, more importantly, the hosting computer's sharing preferences set up correctly. I don't really know what happens if you try to view a webserver by connecting to 192.168.x.x (or 10.x.x.x), when that webserver is on the same computer with that 192.168.x.x address (or 10.x.x.x) coz' I don't run a webserver
per se, not on a computer anyways. I know that I can't connect via afp or vnc to myself.
My two
netcams have the webserver in them themselves. Don't need an evocam. Would have been nice, though, coz' Evocam did provide enhanced capabilities that the netcams otherwise require Windoze ActiveX to set up, but evocam doesn't work with my model number of camera. Works with some TrendNets, but not mine.
I could port forward three ports, one to my ssh/vnc/afp/imap/smtp server, and one each to the cameras. I have done that, but I prefer to just port forward using ssh only to the ssh server computer and tunnel afp, vnc, smtp, and imap to the proper ports on the ssh server's localhost interface, and in the ssh portforward switch commands for the netcams, I deliver them to their "computer name" (that new router of mine has a rudimentary DNS of its own for locally connected stuff). That way, it's only me who has access to the imagery from the outside world.
As a little test for you, why not try to ssh into one of your computers with only UPnP enabled (and remote login on the computer itself, of course) and see if you can login to it from the outside? Are you familiar, at least a little bit, with ssh command line in Terminal.app? Then, if you cannot login via UPnP in the router alone, then try port forwarding ssh (port 22) to that same computer, again with remote login enabled on it, of course, while leaving UPnP enabled. You wouldn't be simultaneously trying to reserve iChat ports via UPnP and port forwarding that way. Then see if you can log in via ssh from the outside, then see if you can do an iChat session with one of your buds. I would find it very interesting to hear about whether that worked for you or not. I can't try it myself, coz' like I said, I never have had to ever deal with that issue in the first place.
So with all that, I think I have just about filled up one of Apple's servers' hard drives....and I'm hijacking the thread, too! Sorry, Apple!