Re: Starting SQUID/IPv6 tests...

[Rafael Martinez Torres]

(I'have been busy, Sorry delay )

  Does cf.data format accept #ifdef directives ? Any idea on how to
  selectively add default IPv6 address ?

 Hmm.. everything in cf.data.pre can be overridden by squid.conf. If just
 provides defaults where suitable.



Rigth, at a first time I thougth so, then I overwrote the lines to
be overriden , but these defaults provided are not
SUITABLE for IPv6 ... I mean

At generated cf_parser.h, the systen will load by default:

#if USE_SSL
/* No default for sslpassword_program */
#endif
default_line(icp_port 0);
#if USE_HTCP
default_line(htcp_port 4827);
#endif
/* No default for mcast_groups */
default_line(udp_incoming_address 0.0.0.0);
default_line(udp_outgoing_address 255.255.255.255);
/* No default for cache_peer */

And clearly, these addresses are not suitable for IPv6 ...
They must be

default_line(udp_incoming_address ::);
default_line(udp_outgoing_address 
::::::f:);

So, when booting Squid, the programm BEFORE overriding with squid.conf

fails with

Default configuration file: udp_incoming_address 0.0.0.0.

For the time beeing, I'm changing cf_parser.h by-hand, but this is
generated on compile-time ...!
So I have to make clean, I have to re-type by-hand
That's why my question...


 What requires you to provide some default IPv6 address?


udp_incoming_address , outgoing and some others else


 Some of the directives like tcp_outgoing_address etc needs to be extended
 with an IPv6 variant, but no default is really needed for either IP
 version.



 The acl all probably should be redefined to really mean all regardless
 of the IP version of the client. I am fine with having this acl
 hardcoded, or actually the all and none acls hardcoded to always true
 or false respectively.  Today there is a lot of user confusion by
 redefining the all acl wrongly causing problems in other directives
 relying on all for their default settings..


On this tip,

all 0.0.0.0/0.0.0.0

must be

all ::/::

Actually I change it by hand on squid.conf...
My opinion should be to be hardcoded as the previous

 What else do you have problems with the defaults of?

 Regards
 Henrik


Status:We are closer to make Squid3/IPv6 minimum runable...
Actually problems with ipcache.cc

Re: Starting SQUID/IPv6 tests...

[Henrik Nordstrom]

On Tue, 14 Jun 2005, Rafael Martinez Torres wrote:


/* No default for mcast_groups */
default_line(udp_incoming_address 0.0.0.0);


These (the ones using 0.0.0.0) should be abstracted using the keyword 
any or unspecified or similar.



default_line(udp_outgoing_address 255.255.255.255);
/* No default for cache_peer */


The second one is really a cludge. The 255.255.255.255 is a magic address 
meaning not specified, use the same as udp_incoming_address. This is 
confusing to a lot of people and is better expressed using a keyword 
rather than a magic address.



On this tip,

all 0.0.0.0/0.0.0.0

must be

all ::/::

Actually I change it by hand on squid.conf...
My opinion should be to be hardcoded as the previous


As I said before the all ACL should be changed to not be a src type acl, 
but a hardcoded acl which is always true. It should not be possible to 
change this from squid.conf imho.


Regards
Henrik