User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr; rv:188.8.131.52) Gecko/20100611 Firefox/3.6.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr; rv:184.108.40.206) Gecko/20100611 Firefox/3.6.4 In some circumstances we want to choose the source IPv6 address and possibly interface instead of letting Firefox and or the OS do the (bad) choice. That could be a modifiable preference (about:config ?) and/or menu option. Although less generally necessary, in principle that could apply to IPv4 as well. Reproducible: Always Steps to Reproduce: 1. make FF access a web site by IPv6 (or IPv4). Actual Results: The source IP address is not under user control Expected Results: There should be a means for User to select a source address and interface. For a quick check connect to anyone of several online "whatismyip" or "whatismyipv6" sites. On-line sites which can "ping" and/or "traceroute" back to you are good exmples or why source IP address selection at the application level (7) is necessary.
I don't understand why this should be necessary on the application level. The used source address is selected based on the target IP and the routing table. The routing table can be changed on the OS level and the target IP depends on the returned DNS entry (IPv4 vs IPv6)
Component: General → Networking
Product: Firefox → Core
QA Contact: general → networking
Hi Matthias. You wrote : "The used source address is selected based on the target IP and the routing table." However there doesn't seem to be any provision for source address selection at the IPv6 routing table level (maybe OS dependent...?) In any case, applications are supposed to be able to override an OS choice of source address, per relevant RFC. As for when this could be necessary I provided an example in the above request. Your proposition that users should change OS seetings, even if it could be worked out, is not practical for page-by-page changes while browsing. You'd probably have to close the browser and reopen it for the OS network setting changes to be effective in Firefox. Not to mention, some well-known OSes might require a reboot :=)
>However there doesn't seem to be any provision for source address selection at >the IPv6 routing table level (maybe OS dependent...?) There is a interface selection on win32/64. >In any case, applications are supposed to be able to override an OS choice of >source address, per relevant RFC Which RFC and which section Do you mean ? >Your proposition that users should change OS seetings, even if it could be >worked out, is not practical for page-by-page changes while browsing. Why should the used interfaces changed for different pages ? This would be only required if the routing table would be wrong. (btw: "route print" shows the windows routing table) >You'd probably have to close the browser >and reopen it for the OS network setting changes to be effective in Firefox. I don't know if you have to do that and that would also mean that you have to restart Firefox if you change the interface via config option in Firefox itself. >Not to mention, some well-known OSes might require a reboot :=) We don't support windows 95/98 anymore and every other OS doesn't require a reboot AFAIK. (maybe OS X but unlikely)
With due respect you appear to be finessing. The primary request is for a way to select *source IP address*, yet you insist on changes of *interface*. As you know, one interface can (and usually will) have several, possibly many, global IP addresses, including autoconfigured ones thru RA or DHCPv6 or even other mechanisms (PPPv6?), so-called "privacy" addresses, preferred and non-preferred, as well as any nimber of manually configured addresses. A user should be able to select /easily/ which address to use for browsing, independently of which IP is used in other applications, at the very least when launching the FF process but IMHO should be changeable at any time while FF is running. The choice of an interface (of several suitable) might follow the same principles, if possible. Admittedly fulfilling this request requires checking for the presence of suitable APIs in each supported OS, which I'm rather confident you'll find available. Sorry I can't cite the RFC numbers and sections off my head, but I'm quite sure I've read about source selection at the app level being either mandatory or recommended.
Assuming the FF application is using the sockets/winsocks model - which it almost certainly is - choosing a source address would be as simple as specifying it explicitly (rather than IPADDR_ANY) in the "connect()" call when binding to the socket. Thus, let the user specify an IP address as a preference if he so chooses and use that address when binding. What is it so difficult to make the concept understood ? I can't grasp why this simple mechanism was not implemented from the start! Regards
The relevant RFC would be RFC5014. The currently (or soon to be) relevant settings are switching between public and temporary ipv6 addresses. Especially on switching to privacy mode, source address selection should be tweaked to prefer temporary ipv6 addresses over public ones.
I think in future one even has to deal with more than one ipv6 prefix. For example, a provider could assign a dynamically provided prefix for browsing and a statically assigned prefix for network services. Browsers would have to use the dynamically assigned prefix.
I opened up a new bug: #811642
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.