Steve Graegert wrote:

On 11/16/05, Yogich wrote:

...

Where the devil did the thread concerning ipv6 go? Should have disabled it immediately, I guess, but was busy figuring out touchpad. :-\

In modprobe.conf uncomment the following line

# install ipv6 /bin/true

This will disable IPv6 support permanently.

That's neither wise nor sufficient. Don't change modprobe.conf, write your local changes in modprobe.conf.local, as is mentioned at the start of modprobe.conf. In addition to the line above, also add install sit0 /bin/true install net-pf-10 /bin/true Cheers, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany

On 11/17/05, Yogich wrote:

On Thursday 17 November 2005 08:40, Joachim Schrod wrote:

...

Steve Graegert wrote:

...

On 11/16/05, Yogich wrote:

...

Where the devil did the thread concerning ipv6 go? Should have disabled it immediately, I guess, but was busy figuring out touchpad. :-\

In modprobe.conf uncomment the following line

# install ipv6 /bin/true

This will disable IPv6 support permanently.

That's neither wise nor sufficient.

Don't change modprobe.conf, write your local changes in modprobe.conf.local, as is mentioned at the start of modprobe.conf.

In addition to the line above, also add install sit0 /bin/true install net-pf-10 /bin/true

Cheers, Joachim

-- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany

One might go into an explanation to buttress the point... ;-)

sit0 and net-pf-10 are aliases to ipv6.ko, the IPv6 kernel module. By disabling ipv6 as mentioned in my previous post sit0 is "disabled" as well. Editing modprobe.conf or modprobe.conf.local is a matter of taste. The latter file is a SuSE extension and the "recommended" place to add modifications. In either case effect is the same. \Steve -- Steve Graegert Software Consultant {C/C++ && Java && .NET} Office: +49 9131 7123988 Mobile: +49 1520 9289212

On 11/17/05, Joachim Schrod wrote:

Steve Graegert wrote:

...

sit0 and net-pf-10 are aliases to ipv6.ko, the IPv6 kernel module. By disabling ipv6 as mentioned in my previous post sit0 is "disabled" as well.

I stand corrected -- almost. :-)

Just 7 days ago, Micheal James reported that disabling ipv6 is not always sufficient. See news://news.gmane.org:119/200511101517.53776.Michael.James@csiro.au

I actually had no idea what the intention of the OP was, since I was not aware of some similar thread. What I read from these lines was that IPv6 should be disabled, somehow.

I don't know if my advice actually helped in his solution, or if it was turning off the IPV6 handling in SUSE's firewall. Since you're completely right that these modules are aliases anyhow, I start to think it's the latter. Thanks for pointing that out, every day to learn something new. :-) :-)

...

Editing modprobe.conf or modprobe.conf.local is a matter of taste. The latter file is a SuSE extension and the "recommended" place to add modifications. In either case effect is the same.

The recommendation is there because modprobe.conf might have to updated by a SUSE package and won't be able to do it if you change it.

This could indeed be true. Since I am used to the "old way" of editing modprobe.conf (f.k.a modules.conf), I prefer editing modprobe.conf directly. (I am quite sure, this will change when something goes wrong with some package action :-)

Concerning that this is a SUSE extension -- well, it's done different for many Linux distributions anyhow. My Debian systems rely on update_modules, for example. And since one has to *add* the line anyhow (there is no ipv6 line in /etc/modprobe.conf, at least not in 9.0, 9.2, and 10.0), one can do so in modprobe.conf.local from the start. Just MHO, of course.

Ah, thanks. Didn't know that. Anyway. diverging approaches among Linux distributions to solve basically the same task is something that I still consider to be a drawback. Makes me think of the not so old promising United Linux / LSB days. *sigh* \Steve -- Steve Graegert Software Consultant {C/C++ && Java && .NET} Office: +49 9131 7123988 Mobile: +49 1520 9289212

On 11/18/05, Joachim Schrod wrote:

Steve Graegert wrote:

...

Anyway. diverging approaches among Linux distributions to solve basically the same task is something that I still consider to be a drawback. Makes me think of the not so old promising United Linux / LSB days. *sigh*

We're in full agreement here. E.g., my pet peeve: it gets a hassle to even write a simple init.d-script that can be properly integrated into several major distributions, there's something clearly wrong in Linux-land. And looking over the fence, to other Unix systems like Solaris 10 or AIX with its src system, it gets even worse.

Exactly. The same is true for their APIs. Although most UNIX systems adhere to POSIX today, their are millions of lines of legacy code that aren't easily ported to POSIX due to the lack of standardized semantics for certain techniques between SysV- and BSD-based systems (e.g. the famous SIGCLD and SIGCHLD or IPC). Still one writes lots of #ifdefs to deal with their specialties. Hope that history does not repeat here. \Steve -- Steve Graegert Software Consultant {C/C++ && Java && .NET} Office: +49 9131 7123988 Mobile: +49 1520 9289212

The problem with doing this isn't that it breaks anything, it's just that there's a solid chance that Yast will overwrite your changes. The notion is to keep certain files that are generated by the Yast setup whenever there are changes to the config, and keep your local changes confined to separate, safe files, which are always included by default. This may not be apparent now, but probably will be in the future. Cheers, J.C. On Thursday 17 November 2005 21:39, Yogich wrote:

On Thursday 17 November 2005 11:40, Steve Graegert wrote: <SNIP>

...

This could indeed be true. Since I am used to the "old way" of editing modprobe.conf (f.k.a modules.conf), I prefer editing modprobe.conf directly. (I am quite sure, this will change when something goes wrong with some package action :-)

I edited it directly, and also commented out the 'alias sit0 ipv6' --and so far nothing br0ke.

<SNIP> -- ...Yogich

-- John Coldrick www.axyzfx.com Axyz Animation 416-504-0425 425 Adelaide St W Toronto, ON Canada jc@axyzfx.com M5V 1S4 ----------------------------------------------------------------------- The world's as ugly as sin, And almost as delightful -- Frederick Locker-Lampson

On Friday 18 November 2005 09:48, Yogich wrote:

At any rate, I am well aware of the ramifications of changing the 'wrong file' and living to regret it. Fact is, I am uncertain as to how one would disable ipv6 any other way --like in the local file. Once enabled in the modprobe.conf file, how would one undo that? I'm afraid I know not, but would very much like to know ...if there indeed is a way.

I have it in my local file and it disables it just fine. Checked with lsmod. If I ever want it back, I'll just comment out the local file and restart. Cheers, J.C. -- John Coldrick www.axyzfx.com Axyz Animation 416-504-0425 425 Adelaide St W Toronto, ON Canada jc@axyzfx.com M5V 1S4 ----------------------------------------------------------------------- The world's as ugly as sin, And almost as delightful -- Frederick Locker-Lampson

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2005-11-18 at 10:53 -0600, Peter A. Taylor wrote:

I put the following three lines in /etc/modprobe.conf.local (SuSE 10.0), and the next time I booted, I got error messages that Postfix had failed. I commented them out, dropped to runlevel 1 and then back to runlevel 3, and Postfix was back. What am I doing wrong?

install ipv6 /bin/true install sit0 /bin/true install net-pf-10 /bin/true

Nothing, but you have postfix configured to use ipv6, so you have to dissable it separately. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDfmVItTMYHG2NR9URAk1QAJ4jXNsAcxi6fWK/ShC37N228ZjV+ACfbzae HPWMMDII8/Tri/bByCl07b4= =Z8o7 -----END PGP SIGNATURE-----

pelibali wrote:

No I have postfix _not_ working, getting trinity:/etc/init.d # cat /var/log/boot.msg | grep -i postfix Starting mail service (Postfix)failed Failed services in runlevel 3: postfix

probably because this line

trinity:/etc/init.d # cat postfix | grep -i ::1 PIFACES=$($POSTCONF -h inet_interfaces|sed -e 's/\(127.0.0.1\|::1\|[[:space:]]\)//g')

This line extracts all interfaces from the Postfix configuration, except localhost. Localhost _may_ be IPv4 or IPv6. This command does not access any IPv6 interface in any way. Therefore this line is not the cause of your problems.

Any ideas please, how to get postfix started without listening on ipv6-type address?

Look at /etc/postfix/main.cf. Check if the configuration line with inet_interfaces has a ::1 in it. If yes, discard it. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany

On Friday 18 November 2005 19:24, Darryl Gregorash wrote:

On 11/16/2005 12:12 PM, Yogich wrote:

...

Where the devil did the thread concerning ipv6 go?  Should have disabled it immediately, I guess, but was busy figuring out touchpad. :-\  

In addition to the other stuff, /etc/sysconfig/network/config:

# If you don't want to use ipv6 at all, set this to 'no'. Then ifup will always # flush all ipv6 adresses. This might be usefull together with ifplugd, if link # beat detection is only possible with interface UP. # USE_IPV6="no"

and to get rid of the firewall-related modules that will get loaded anyway, in /etc/sysconfig/SuSEfirewall2:

# What to do with IPv6 Packets? # - no: do not set any IPv6 rules at all. Your Host will allow any IPv6 # - drop: drop all IPv6 packets. This is the default if stateful matching is # - reject: reject all IPv6 packets # Disallowing IPv6 packets may lead to long timeouts when connecting to IPv6 # Adresses. See FW_IPv6_REJECT_OUTGOING to avoid this. FW_IPv6="no" # Reject outgoing IPv6 Packets? # Set to yes to avoid timeouts because of dropped IPv6 Packets. This Option # does only make sense with FW_IPv6 != no FW_IPv6_REJECT_OUTGOING=""

and in /etc/sysconfig/windowmanager:

# To disable IPv6 support within KDE. It might solve large timeouts due to KDE_USE_IPV6="no" Thanks for the info. :-) -- ...Yogich