In Firefox the proxy settings are under Edit/Preferences/Advanced/Network/Settings <=that's on Linux, the Windows version goes Tools/preferences, etc (never used FF on MacOS)
There are several quick proxy switching extensions for FF, my favorite is "Switch Proxy Tool" (in button mode, not the whole toolbar: hide the toolbar and use the rightclick/customize shortcut, or View/Toolbars/Customize toolbars; once you install Switch Proxy Tool and restart, you'll be able to draw and drop a button to one of your toolbars, that button will add an item for each proxy you set up to a drop-down menu) I have my browser set to use Tor and I browse freesites using the line http://127.0.0.1:8888/ before the key, which is equivalent of setting the proxy to 127.0.0.1 port 8888 and only pasting the key in the address field, but using the whole proxy:port line (which overrides your proxy settings) and having the browser set to use a fairly reliable anonymizing proxy, you have the "double protection" provided by that proxy setting that will route your communications thru the Tor network if you click on a non-Freenet link (i2p can also be used that way). Freenet will warn you and ask if you are sure before going to a non-Freenet location. As for the NAT thing, I'm behind a NAT where I can't do port forwarding (evil ISP) and my 0.7 node works perfectly... well, almost perfectly: I can't peer to nodes that are also behind a NAT and with no forwarded ports, but that's not much of a limitation, I can connect to almost all nodes, as not many of them are NAT'ed and with no forwarded ports, Ben Dougall wrote: > Thanks very much for the reply. > > On Monday, June 4, 2007, at 10:28 pm, Matthew Toseland wrote: > >> Check your browser proxy settings. You want to set no proxy for >> 127.0.0.1. > > I can't see any proxy setting in either Firefox nor Safari's > preferences. I've certainly never turned any on before. There is a > Proxy settings tab in the Network panel in the System preferences, but > no setting are on here apart from one box is checked: "Use Passive FTP > Mode (PASV)" which I guess is nothing to do with this. > >> BTW your airport is almost certainly a NAT, but that shouldn't prevent >> you >> from accessing your node's local interface. > > I think it does allow NAT but NAT is not turned on. > > _______________________________________________ > Support mailing list > Support at freenetproject.org > http://news.gmane.org/gmane.network.freenet.support > Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support > Or mailto:support-request at freenetproject.org?subject=unsubscribe >
