Re: ipv6

 

That might be fine for home uses... But try that approach if you run
public facing servers, that all load up well before rc.local, if the
daemons start at all, they will end up not listening on ipv6, I think
Nick has a valid point (I gave him a quick reference on another mailing
list last year on how I do it, as below, no idea if he still uses this
way or has made it more efficient, Nick ??). 

if this was 2004 I'd say "pffft" but like he says, it aint, its 2014,
dunno bout you guys but in Australia you can not get any more ipv4
addresses from APNIC, and if you cant barter with those wasting them to
buy a few ranges off them, you are left with only ipv6, whats the point
of a hosting company for example, having a /32, if none of their
slackware boxes bring up ipv6 accepting web mail and dns services?
jesus, even RedHat has been doing this for *years* 

I know I get sick of having to remember to modify rc.inet1 and have it
call my 6 file as well, its only a simple script... 

ipv6_up() {
echo "Bringing up IPv6... " 

/usr/sbin/ip -6 addr add 2001:...... 

/usr/sbin/ip -6 addr add 2001:.. 

/usr/sbin/ip -6 route add default via 2001 

} 

but having to remember to add into rc.inet1 

# Function to start the network:
start() {
 lo_up
 for i in ${IFNAME[@]} ; do
 if_up $i
 done
 if [ -x /etc/rc.d/rc.ipv6 ]; then
 /etc/rc.d/rc.ipv6 start
 fi
 gateway_up
 } 

(and reverses for takedown) 

 is a PITA every time you build a server 

Hell, I even sent this (crappy and likely inefficient 2 minute written)
patch to Pat a couple of years ago, its crude but it works, but seems he
either did not get it, or CBF'd either :) 

On 01/03/2014 06:16, Gil André wrote: 

> Er… 
> On 28 Feb 2014, at 02:56, Nick Edwards <[email protected]> wrote:
> 
>> So, anyone know if when slackware's network setup will include provisions for IPv6? running them from rc.local is not efficient, given its needed much earlier, like when IPv4 is brought up, I would have thought the rc.inet's would cater for this in 2014, since most the world has already exhausted IPv4.
> 
> How is this not efficient?
> 
> 99.9% of the time, rc.local is executed just a few seconds after the
> rest of the /etc/rc.d/ scripts. Unless you have very specific needs,
> this should be good enough.
> 
> If you have already written your own ipv6 scripts, maybe you should 
> share them with the rest of the world?
> 
> And I share ''x y'' opinion: the vast majority of ISPs and web sites
> out there do not offer IPv6 connections yet. Whether that is good or
> bad is another discussion entirely… 
> 
> Cheers,
> 
> -- Gil.
> 
> _______________________________________________
> slackware mailing list
> [email protected]
> https://mailman.lug.org.uk/mailman/listinfo/slackware [1]

 

Links:
------
[1] https://mailman.lug.org.uk/mailman/listinfo/slackware

_______________________________________________
slackware mailing list
[email protected]
https://mailman.lug.org.uk/mailman/listinfo/slackware