Re: IPV6INIT=no, but does anyway on local network
--- On Tue, 10/7/08, Gene Heskett <[EMAIL PROTECTED]> wrote: > From: Gene Heskett <[EMAIL PROTECTED]> > Subject: Re: IPV6INIT=no, but does anyway on local network > To: "Community assistance, encouragement, and advice for using Fedora." > > Date: Tuesday, October 7, 2008, 7:44 AM > On Monday 06 October 2008, Phil Savoie wrote: > >Thomas Cameron wrote: > >> Gene Heskett wrote: > >>> Greetings; > >>> > >>> In /etc/sysconfig/ifcfg-eth0 I have the line > as in the subject, but I > >>> note that bringing up eth0, at a fixed ipv4 > address in the 192.168 > >>> block, there is about a 5 second pause doing > it, and ifconfig does > >>> report what looks like valid ipv6 addresses > for both eth0 and lo. > >>> > >>> eth0 Link encap:Ethernet HWaddr > 00:1F:C6:62:FC:BB > >>> inet addr:192.168.71.3 > Bcast:192.168.71.255 > >>> Mask:255.255.255.0 > >>> inet6 addr: > fe80::21f:c6ff:fe62:fcbb/64 Scope:Link > >>> UP BROADCAST RUNNING MULTICAST > MTU:1500 Metric:1 > >>> RX packets:52899 errors:0 dropped:0 > overruns:0 frame:0 > >>> TX packets:45100 errors:0 dropped:0 > overruns:0 carrier:0 > >>> collisions:0 txqueuelen:1000 > >>> RX bytes:34184438 (32.6 MiB) TX > bytes:26737247 (25.4 MiB) > >>> Interrupt:22 Base address:0xa000 > >>> > >>> loLink encap:Local Loopback > >>> inet addr:127.0.0.1 Mask:255.0.0.0 > >>> inet6 addr: ::1/128 Scope:Host > >>> UP LOOPBACK RUNNING MTU:16436 > Metric:1 > >>> RX packets:6888 errors:0 dropped:0 > overruns:0 frame:0 > >>> TX packets:6888 errors:0 dropped:0 > overruns:0 carrier:0 > >>> collisions:0 txqueuelen:0 > >>> RX bytes:16987249 (16.2 MiB) TX > bytes:16987249 (16.2 MiB) > >>> > >>> > >>> How does one go about disabling that? > >> > >> What happens if you add: > >> > >> install ipv6 /bin/true > >> > >> to /etc/modprobe.conf? Forgive me if that > doesn't work, I don't have a > >> Fedora box to play with at the moment, only RHEL > 5. > >> > >> TC > > > >I think a reboot may be necessary for this change to > work. > > > >Phil > > Expected. And I also expect that the proper newer syntax > in the ifcfg-eth0 > file would also fix it, and require only a "service > network restart" to > adjust the setting. > > -- > Cheers, Gene > "There are four boxes to be used in defense of > liberty: > soap, ballot, jury, and ammo. Please use in that > order." > -Ed Howdershelt (Author) > Don't try to outweird me, three-eyes. I get stranger > things than you free > with my breakfast cereal. > -- Zaphod Beeblebrox > WHY make a career of it! I solved the same problem with: http://blog.taragana.com/index.php/archive/how-to-disable-ipv6-on-fedora-linux-why/ > -- > fedora-list mailing list > fedora-list@redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: > http://fedoraproject.org/wiki/Communicate/MailingListGuidelines -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
On Monday 06 October 2008, Phil Savoie wrote: >Thomas Cameron wrote: >> Gene Heskett wrote: >>> Greetings; >>> >>> In /etc/sysconfig/ifcfg-eth0 I have the line as in the subject, but I >>> note that bringing up eth0, at a fixed ipv4 address in the 192.168 >>> block, there is about a 5 second pause doing it, and ifconfig does >>> report what looks like valid ipv6 addresses for both eth0 and lo. >>> >>> eth0 Link encap:Ethernet HWaddr 00:1F:C6:62:FC:BB >>> inet addr:192.168.71.3 Bcast:192.168.71.255 >>> Mask:255.255.255.0 >>> inet6 addr: fe80::21f:c6ff:fe62:fcbb/64 Scope:Link >>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >>> RX packets:52899 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:45100 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:1000 >>> RX bytes:34184438 (32.6 MiB) TX bytes:26737247 (25.4 MiB) >>> Interrupt:22 Base address:0xa000 >>> >>> loLink encap:Local Loopback >>> inet addr:127.0.0.1 Mask:255.0.0.0 >>> inet6 addr: ::1/128 Scope:Host >>> UP LOOPBACK RUNNING MTU:16436 Metric:1 >>> RX packets:6888 errors:0 dropped:0 overruns:0 frame:0 >>> TX packets:6888 errors:0 dropped:0 overruns:0 carrier:0 >>> collisions:0 txqueuelen:0 >>> RX bytes:16987249 (16.2 MiB) TX bytes:16987249 (16.2 MiB) >>> >>> >>> How does one go about disabling that? >> >> What happens if you add: >> >> install ipv6 /bin/true >> >> to /etc/modprobe.conf? Forgive me if that doesn't work, I don't have a >> Fedora box to play with at the moment, only RHEL 5. >> >> TC > >I think a reboot may be necessary for this change to work. > >Phil Expected. And I also expect that the proper newer syntax in the ifcfg-eth0 file would also fix it, and require only a "service network restart" to adjust the setting. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Don't try to outweird me, three-eyes. I get stranger things than you free with my breakfast cereal. -- Zaphod Beeblebrox -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
On Monday 06 October 2008, Craig White wrote: >On Mon, 2008-10-06 at 20:35 -0500, Thomas Cameron wrote: >> Gene Heskett wrote: >> > Greetings; >> > >> > In /etc/sysconfig/ifcfg-eth0 I have the line as in the subject, but I >> > note that bringing up eth0, at a fixed ipv4 address in the 192.168 >> > block, there is about a 5 second pause doing it, and ifconfig does >> > report what looks like valid ipv6 addresses for both eth0 and lo. >> > >> > >> > How does one go about disabling that? >> >> What happens if you add: >> >> install ipv6 /bin/true This worked, and eth0 comes up in half the former time. Thanks. >> to /etc/modprobe.conf? Forgive me if that doesn't work, I don't have a >> Fedora box to play with at the moment, only RHEL 5. > > >I've read that works > >other methods that should work... > >adding >NETWORKING_IPV6=no >to /etc/sysconfig/network and reboot Humm, that is a syntax change, I have had a simple IPV6INIT=no in there for some years. It only stopped working to disable ipv6 when I changed motherboards, trading the 2.1Ghz xp-2800 for a 4 core 2.2Ghz phenom. I've adjusted that also, thanks. >or > >adding >alias net-pf-10 off >alias ipv6 off > >to /etc/modprobe.conf should also work > >Craig -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) It's great to be smart 'cause then you know stuff. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
On Monday 06 October 2008, Thomas Cameron wrote: >Gene Heskett wrote: >> Greetings; >> >> In /etc/sysconfig/ifcfg-eth0 I have the line as in the subject, but I note >> that bringing up eth0, at a fixed ipv4 address in the 192.168 block, there >> is about a 5 second pause doing it, and ifconfig does report what looks >> like valid ipv6 addresses for both eth0 and lo. >> >> eth0 Link encap:Ethernet HWaddr 00:1F:C6:62:FC:BB >> inet addr:192.168.71.3 Bcast:192.168.71.255 Mask:255.255.255.0 >> inet6 addr: fe80::21f:c6ff:fe62:fcbb/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:52899 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:45100 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:34184438 (32.6 MiB) TX bytes:26737247 (25.4 MiB) >> Interrupt:22 Base address:0xa000 >> >> loLink encap:Local Loopback >> inet addr:127.0.0.1 Mask:255.0.0.0 >> inet6 addr: ::1/128 Scope:Host >> UP LOOPBACK RUNNING MTU:16436 Metric:1 >> RX packets:6888 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:6888 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:16987249 (16.2 MiB) TX bytes:16987249 (16.2 MiB) >> >> >> How does one go about disabling that? > >What happens if you add: > >install ipv6 /bin/true > >to /etc/modprobe.conf? Forgive me if that doesn't work, I don't have a >Fedora box to play with at the moment, only RHEL 5. > >TC Thanks. I put that in, and re-assigned the index numbers to re-order the hd stuff too. Rebooted, the ipv6 is gone and bringing up eth0 is faster, but the drives are still out of order. Labels make it work anyway, so I suppose its a shrug. Thank you. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Remember: Silly is a state of Mind, Stupid is a way of Life. -- Dave Butler -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
Thomas Cameron wrote: > Gene Heskett wrote: >> Greetings; >> >> In /etc/sysconfig/ifcfg-eth0 I have the line as in the subject, but I >> note that bringing up eth0, at a fixed ipv4 address in the 192.168 >> block, there is about a 5 second pause doing it, and ifconfig does >> report what looks like valid ipv6 addresses for both eth0 and lo. >> >> eth0 Link encap:Ethernet HWaddr 00:1F:C6:62:FC:BB >> inet addr:192.168.71.3 Bcast:192.168.71.255 >> Mask:255.255.255.0 >> inet6 addr: fe80::21f:c6ff:fe62:fcbb/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:52899 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:45100 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:34184438 (32.6 MiB) TX bytes:26737247 (25.4 MiB) >> Interrupt:22 Base address:0xa000 >> >> loLink encap:Local Loopback >> inet addr:127.0.0.1 Mask:255.0.0.0 >> inet6 addr: ::1/128 Scope:Host >> UP LOOPBACK RUNNING MTU:16436 Metric:1 >> RX packets:6888 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:6888 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:16987249 (16.2 MiB) TX bytes:16987249 (16.2 MiB) >> >> >> How does one go about disabling that? >> > > What happens if you add: > > install ipv6 /bin/true > > to /etc/modprobe.conf? Forgive me if that doesn't work, I don't have a > Fedora box to play with at the moment, only RHEL 5. > > TC > I think a reboot may be necessary for this change to work. Phil -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
On Mon, 2008-10-06 at 20:35 -0500, Thomas Cameron wrote: > Gene Heskett wrote: > > Greetings; > > > > In /etc/sysconfig/ifcfg-eth0 I have the line as in the subject, but I note > > that bringing up eth0, at a fixed ipv4 address in the 192.168 block, there > > is > > about a 5 second pause doing it, and ifconfig does report what looks like > > valid ipv6 addresses for both eth0 and lo. > > > > > > How does one go about disabling that? > > > > What happens if you add: > > install ipv6 /bin/true > > to /etc/modprobe.conf? Forgive me if that doesn't work, I don't have a > Fedora box to play with at the moment, only RHEL 5. I've read that works other methods that should work... adding NETWORKING_IPV6=no to /etc/sysconfig/network and reboot or adding alias net-pf-10 off alias ipv6 off to /etc/modprobe.conf should also work Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
Gene Heskett wrote: Greetings; In /etc/sysconfig/ifcfg-eth0 I have the line as in the subject, but I note that bringing up eth0, at a fixed ipv4 address in the 192.168 block, there is about a 5 second pause doing it, and ifconfig does report what looks like valid ipv6 addresses for both eth0 and lo. eth0 Link encap:Ethernet HWaddr 00:1F:C6:62:FC:BB inet addr:192.168.71.3 Bcast:192.168.71.255 Mask:255.255.255.0 inet6 addr: fe80::21f:c6ff:fe62:fcbb/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:52899 errors:0 dropped:0 overruns:0 frame:0 TX packets:45100 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:34184438 (32.6 MiB) TX bytes:26737247 (25.4 MiB) Interrupt:22 Base address:0xa000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:6888 errors:0 dropped:0 overruns:0 frame:0 TX packets:6888 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:16987249 (16.2 MiB) TX bytes:16987249 (16.2 MiB) How does one go about disabling that? What happens if you add: install ipv6 /bin/true to /etc/modprobe.conf? Forgive me if that doesn't work, I don't have a Fedora box to play with at the moment, only RHEL 5. TC signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
On Sunday 05 October 2008, Wolfgang S. Rupprecht wrote:
>Gene Heskett <[EMAIL PROTECTED]> writes:
>> Because here, everything is on a 192.168.x.x address, fixed using host
>> files for dns resolution.
>
>I've got both local IPv4 addresses and IPv6 addresses in my /etc/hosts
>file. Works just fine. As for added complexity, it isn't really any
>more complex than adding a few config lines. The rest is automatic.
>In a lot of ways it is much simpler than IPv4 because folks learned
>from their IPv4 mistakes and realized how important it was for IPv6 to
>automatically configure itself.
>
>> Anything that doesn't resolve locally gets sent to 192.168.X.1,
>> which is a dd-wrt install which handles all the PPPoE stuffs to
>> connect me to my adsl account. A max of 4 live machines here
>> certainly doesn't need the complexity of ipv6.
>>
>> That is all I get from vz, and I have doubts they have anything setup that
>> would forward an ipv6 query to my ipv4 address their quasi-dhcp issues.
>
>I run openwrt here, but assume dd-wrt is similar. I bet it possible
>to have dd-wrt router automatically forward all ipv6 addresses to the
>global tun6to4 gateways. One wouldn't even need to have one's linux
>box (or boxes) establish a tunnel. That way everything on your
>ethernet gets a working IPv6 address. I believe this is also what
>Apple's WIFI hocky-puck ("airport") routers do.
>
dd-wrt has an enable-disable for ipv6, but nothing else of note.
>-wolfgang
>--
>Wolfgang S. Rupprecht http://www.full-steam.org/ (ipv6-only)
> You may need to config 6to4 to see the above pages.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
All new:
Parts not interchangeable with previous model.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
Gene Heskett <[EMAIL PROTECTED]> writes:
> Because here, everything is on a 192.168.x.x address, fixed using host files
> for dns resolution.
I've got both local IPv4 addresses and IPv6 addresses in my /etc/hosts
file. Works just fine. As for added complexity, it isn't really any
more complex than adding a few config lines. The rest is automatic.
In a lot of ways it is much simpler than IPv4 because folks learned
from their IPv4 mistakes and realized how important it was for IPv6 to
automatically configure itself.
> Anything that doesn't resolve locally gets sent to 192.168.X.1,
> which is a dd-wrt install which handles all the PPPoE stuffs to
> connect me to my adsl account. A max of 4 live machines here
> certainly doesn't need the complexity of ipv6.
>
> That is all I get from vz, and I have doubts they have anything setup that
> would forward an ipv6 query to my ipv4 address their quasi-dhcp issues.
I run openwrt here, but assume dd-wrt is similar. I bet it possible
to have dd-wrt router automatically forward all ipv6 addresses to the
global tun6to4 gateways. One wouldn't even need to have one's linux
box (or boxes) establish a tunnel. That way everything on your
ethernet gets a working IPv6 address. I believe this is also what
Apple's WIFI hocky-puck ("airport") routers do.
-wolfgang
--
Wolfgang S. Rupprecht http://www.full-steam.org/ (ipv6-only)
You may need to config 6to4 to see the above pages.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
On Saturday 04 October 2008, Wolfgang S. Rupprecht wrote: >Gene Heskett <[EMAIL PROTECTED]> writes: >> How does one go about disabling that? > >Why, pray tell? > Because here, everything is on a 192.168.x.x address, fixed using host files for dns resolution. Anything that doesn't resolve locally gets sent to 192.168.X.1, which is a dd-wrt install which handles all the PPPoE stuffs to connect me to my adsl account. A max of 4 live machines here certainly doesn't need the complexity of ipv6. >IPv6 is just about the only way one can reach one's internal machines >from the outside world when has a cheap ISP that hands out a single >IPv4 address. That is all I get from vz, and I have doubts they have anything setup that would forward an ipv6 query to my ipv4 address their quasi-dhcp issues. >The 6to4 tunnel makes it trivial to set up IPv6. >(I run a static tunnel, but from my notes, I believe this is what I >had to do to get the simple 6to4 tunnel working.) > >echo "IPV6_DEFAULTDEV=tun6to4">> /etc/sysconfig/network >echo "NETWORKING_IPV6=yes">> /etc/sysconfig/network >echo "IPV6INIT=yes">> /etc/sysconfig/network-scripts/ifcfg-eth0 >echo "IPV6TO4INIT=yes" >> /etc/sysconfig/network-scripts/ifcfg-eth0 > >-wolfgang >-- >Wolfgang S. Rupprecht http://www.full-steam.org/ (ipv6-only) > You may need to config 6to4 to see the above pages. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Zoe: "You know what the definition of a hero is? It's someone who gets other people killed. You can look it up later." --"Serenity" -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
Gene Heskett <[EMAIL PROTECTED]> writes: > How does one go about disabling that? Why, pray tell? IPv6 is just about the only way one can reach one's internal machines from the outside world when has a cheap ISP that hands out a single IPv4 address. The 6to4 tunnel makes it trivial to set up IPv6. (I run a static tunnel, but from my notes, I believe this is what I had to do to get the simple 6to4 tunnel working.) echo "IPV6_DEFAULTDEV=tun6to4">> /etc/sysconfig/network echo "NETWORKING_IPV6=yes">> /etc/sysconfig/network echo "IPV6INIT=yes">> /etc/sysconfig/network-scripts/ifcfg-eth0 echo "IPV6TO4INIT=yes" >> /etc/sysconfig/network-scripts/ifcfg-eth0 -wolfgang -- Wolfgang S. Rupprecht http://www.full-steam.org/ (ipv6-only) You may need to config 6to4 to see the above pages. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
On Saturday 04 October 2008, [EMAIL PROTECTED] wrote: >Hello, > >After FC8, there is a system tool of "udev", it will help you to handle >the adapter config for the system... > >Edward. Ahh, that is better. All I have to do is wrap my aged (it is 74 today) wet ram around a new tool when I get to that point. :-) Thanks Edward. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Smell from unhygenic janitorial staff wrecked the tape heads -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
On Sat, 2008-10-04 at 23:26 +0800, [EMAIL PROTECTED] wrote: > Hello, > > After FC8 System, there is no /etc/modprobe.conf ( default hand by > system ), the user may use the GUI ( NOT text mode ) tool or modify > ifcfg-eth* file for it... > > Edward. > Edward, You may want to actually "try" the advice before summarily dismissing it. True, that in F9 there is no "default" /etc/modprobe.conf, but if you simply place the following two lines in that newly created file, it will prevent the ipv6 kernel module from loading: alias ipv6 off alias net-pf-10 off Again, I am not sure about the current need for the second line. I have not tried it, but placing the module names in the /etc/modprobe.d/blacklist file may also achieve the same results. Understand that the entry in the ifcfg-* files which you are so fond of only prevents the use of the "other" forms of autoconfiguration like dhcpv6 and router advertisements. You will still get a "Link-Local" address that while not routable will still leave you exposed to connections from other IPv6 machines on the local LAN, which is part of the "discussion" currently going on fedora-devel about the need for ip6tables to be started automatically on a default install. You must prevent the kernel module from loading into memory if you want to stop the creation of Link-Local addresses. --Rob -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
Hello, After FC8, there is a system tool of "udev", it will help you to handle the adapter config for the system... Edward. Gene Heskett wrote: >On Saturday 04 October 2008, [EMAIL PROTECTED] wrote: > > >>Hello, >> >>After FC8 System, there is no /etc/modprobe.conf ( default hand by >>system ), the user may use the GUI ( NOT text mode ) tool or modify >>ifcfg-eth* file for it... >> >> > >What the Says he incredulously. Howinhell am I supposed to be able to >use 2 sound cards, in the reverse order from discovery? > >I normally assign the mobo audio to private use, like skype, and have an >Audigy2 Value (SB0400) card that does all the main audio here. To do that, >here is my F8 modprobe.conf: > >alias scsi_hostadapter libata >alias scsi_hostadapter1 sata_sil >alias scsi_hostadapter2 pata_amd > >Humm, I could reverse that and put my drives back in the same order as they >were before... But that wouldn't fix grub. :( LABEL's make it work anyway. > >The audio stuff: > >alias snd-card-0 snd-emu10k1 >alias snd-card-1 snd-hda-intel >options snd-hda-intel index=1 >options snd-emu10k1 index=0 >options snd-intel8x0 index=2 >options snd-mpu401 index=3 > >alias eth0 forcedeth > >How am I to effect this same setup for F10 when it is out? That would be a >total show stopper for me if I cannot. > > > >>Edward. >> >>Ian Pilcher wrote: >> >> >>>Gene Heskett wrote: >>> >>> How does one go about disabling that? >>>It's not easy. The Linux kernel automatically assigns a link-local IPv6 >>>address to any interface that's brought up. If you don't want to use >>>IPv6 at all, you can use /etc/modprobe.conf to prevent the appropriate >>>module from being loaded. (ISTR that it used to be called net-pf-10, >>>but that module doesn't seem to exist anymore; I'd try disabling the >>>ipv6 module.) >>> >>>To get rid of the IPv6 address on a particular interface, you should be >>>able to use some variation of 'ip addr ...'. >>> >>>The only way I know of to prevent the kernel from assigning an address >>>when an interface is brought up is to set the MTU to a ridiculously low >>>value before bringing the interface up. If the MTU is too low for IPv6 >>>to work, the kernel won't assign the address. Once the interface is up, >>>you can set the MTU back to what you want and assign an IPv4 address (if >>>desired). Needless to say, this is an ugly hack, and it's not supported >>>by the networking scripts. >>> >>>HTH >>> >>> > > > > > -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
On Saturday 04 October 2008, [EMAIL PROTECTED] wrote: >Hello, > >After FC8 System, there is no /etc/modprobe.conf ( default hand by >system ), the user may use the GUI ( NOT text mode ) tool or modify >ifcfg-eth* file for it... What the Says he incredulously. Howinhell am I supposed to be able to use 2 sound cards, in the reverse order from discovery? I normally assign the mobo audio to private use, like skype, and have an Audigy2 Value (SB0400) card that does all the main audio here. To do that, here is my F8 modprobe.conf: alias scsi_hostadapter libata alias scsi_hostadapter1 sata_sil alias scsi_hostadapter2 pata_amd Humm, I could reverse that and put my drives back in the same order as they were before... But that wouldn't fix grub. :( LABEL's make it work anyway. The audio stuff: alias snd-card-0 snd-emu10k1 alias snd-card-1 snd-hda-intel options snd-hda-intel index=1 options snd-emu10k1 index=0 options snd-intel8x0 index=2 options snd-mpu401 index=3 alias eth0 forcedeth How am I to effect this same setup for F10 when it is out? That would be a total show stopper for me if I cannot. >Edward. > >Ian Pilcher wrote: >>Gene Heskett wrote: >>>How does one go about disabling that? >> >>It's not easy. The Linux kernel automatically assigns a link-local IPv6 >>address to any interface that's brought up. If you don't want to use >>IPv6 at all, you can use /etc/modprobe.conf to prevent the appropriate >>module from being loaded. (ISTR that it used to be called net-pf-10, >>but that module doesn't seem to exist anymore; I'd try disabling the >>ipv6 module.) >> >>To get rid of the IPv6 address on a particular interface, you should be >>able to use some variation of 'ip addr ...'. >> >>The only way I know of to prevent the kernel from assigning an address >>when an interface is brought up is to set the MTU to a ridiculously low >>value before bringing the interface up. If the MTU is too low for IPv6 >>to work, the kernel won't assign the address. Once the interface is up, >>you can set the MTU back to what you want and assign an IPv4 address (if >>desired). Needless to say, this is an ugly hack, and it's not supported >>by the networking scripts. >> >>HTH -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Bad men live that they may eat and drink, whereas good men eat and drink that they may live. -- Socrates -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
On Saturday 04 October 2008, Ian Pilcher wrote: >Gene Heskett wrote: >> How does one go about disabling that? > >It's not easy. The Linux kernel automatically assigns a link-local IPv6 >address to any interface that's brought up. If you don't want to use >IPv6 at all, you can use /etc/modprobe.conf to prevent the appropriate >module from being loaded. (ISTR that it used to be called net-pf-10, >but that module doesn't seem to exist anymore; I'd try disabling the >ipv6 module.) > >To get rid of the IPv6 address on a particular interface, you should be >able to use some variation of 'ip addr ...'. > >The only way I know of to prevent the kernel from assigning an address >when an interface is brought up is to set the MTU to a ridiculously low >value before bringing the interface up. If the MTU is too low for IPv6 >to work, the kernel won't assign the address. Once the interface is up, >you can set the MTU back to what you want and assign an IPv4 address (if >desired). Needless to say, this is an ugly hack, and it's not supported >by the networking scripts. > >HTH No, it doesn't help, but it does explain it somewhat. In the end, I guess I'm stuck with it. But I did not have this problem on the previous motherboard, so while the reasoning is good, it seemed to me to have been a software problem. Both boards are running a 32 bit 2.6.27-rc8 kernel. One thing I did find yesterday was that my port forwarded web page access was dead, and in running that down I noted I was on eth1 with the new mobo. It seems something in the network scripts edited /etc/sysconfig/network-scripts/ifcfg-eth1 to enable it and set it for DHCP. I use fixed addressing here at the old farts ranchette, and that address diff meant the Port Forwarding I do in dd-wrt was wrong. So I killed the onboot=yes in eth1, and reset the mac address in ifcfg-eth0 to correspond to the new hardware, did a network restart and that's back to normal, but still with the 5 second lag at bringing it up. Why does the line IPV6INIT=no in ifcfg-eth0 not work? This strikes me as a bugzilla item. Or a just ignore it. :) Now, if I could figure out why grub takes an extra 30 seconds to load and run at bootup. Thanks Ian. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) QOTD: On a scale of 1 to 10 I'd say... oh, somewhere in there. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
Hello, After FC8 System, there is no /etc/modprobe.conf ( default hand by system ), the user may use the GUI ( NOT text mode ) tool or modify ifcfg-eth* file for it... Edward. Ian Pilcher wrote: >Gene Heskett wrote: > > >>How does one go about disabling that? >> >> > >It's not easy. The Linux kernel automatically assigns a link-local IPv6 >address to any interface that's brought up. If you don't want to use >IPv6 at all, you can use /etc/modprobe.conf to prevent the appropriate >module from being loaded. (ISTR that it used to be called net-pf-10, >but that module doesn't seem to exist anymore; I'd try disabling the >ipv6 module.) > >To get rid of the IPv6 address on a particular interface, you should be >able to use some variation of 'ip addr ...'. > >The only way I know of to prevent the kernel from assigning an address >when an interface is brought up is to set the MTU to a ridiculously low >value before bringing the interface up. If the MTU is too low for IPv6 >to work, the kernel won't assign the address. Once the interface is up, >you can set the MTU back to what you want and assign an IPv4 address (if >desired). Needless to say, this is an ugly hack, and it's not supported >by the networking scripts. > >HTH > > > -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
Gene Heskett wrote: > How does one go about disabling that? It's not easy. The Linux kernel automatically assigns a link-local IPv6 address to any interface that's brought up. If you don't want to use IPv6 at all, you can use /etc/modprobe.conf to prevent the appropriate module from being loaded. (ISTR that it used to be called net-pf-10, but that module doesn't seem to exist anymore; I'd try disabling the ipv6 module.) To get rid of the IPv6 address on a particular interface, you should be able to use some variation of 'ip addr ...'. The only way I know of to prevent the kernel from assigning an address when an interface is brought up is to set the MTU to a ridiculously low value before bringing the interface up. If the MTU is too low for IPv6 to work, the kernel won't assign the address. Once the interface is up, you can set the MTU back to what you want and assign an IPv4 address (if desired). Needless to say, this is an ugly hack, and it's not supported by the networking scripts. HTH -- Ian Pilcher [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
On Sat, 2008-10-04 at 02:54 -0400, Gene Heskett wrote: > On Saturday 04 October 2008, [EMAIL PROTECTED] wrote: > >Hello, > > > >You are using IPv4 ( If IPv6 disabled )... > > > >Edward. > > > Agreed Edward, but when it doesn't show the ipv6 addresses at all, the > interface is brought up in milliseconds, as opposed to the 5 second lag it > has now. That is the lag I would like to remove. > > Thank you. > Gene and Edward, All IPV6INIT does in the ifcfg-* file is prevent the network script from using IPv6. Fortunately/unfortunately, you are, in fact, still loading the kernel module, ipv6.ko. If that module is loaded, you will get a locally scoped IPv6 address which is seen in the output that Gene supplied. > >Gene Heskett wrote: > >>Greetings; > >> > >>In /etc/sysconfig/ifcfg-eth0 I have the line as in the subject, but I note > >>that bringing up eth0, at a fixed ipv4 address in the 192.168 block, there > >> is about a 5 second pause doing it, and ifconfig does report what looks > >> like valid ipv6 addresses for both eth0 and lo. > >> > >>eth0 Link encap:Ethernet HWaddr 00:1F:C6:62:FC:BB > >> inet addr:192.168.71.3 Bcast:192.168.71.255 Mask:255.255.255.0 > >> inet6 addr: fe80::21f:c6ff:fe62:fcbb/64 Scope:Link > >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > >> RX packets:52899 errors:0 dropped:0 overruns:0 frame:0 > >> TX packets:45100 errors:0 dropped:0 overruns:0 carrier:0 > >> collisions:0 txqueuelen:1000 > >> RX bytes:34184438 (32.6 MiB) TX bytes:26737247 (25.4 MiB) > >> Interrupt:22 Base address:0xa000 > >> > >>loLink encap:Local Loopback > >> inet addr:127.0.0.1 Mask:255.0.0.0 > >> inet6 addr: ::1/128 Scope:Host > >> UP LOOPBACK RUNNING MTU:16436 Metric:1 > >> RX packets:6888 errors:0 dropped:0 overruns:0 frame:0 > >> TX packets:6888 errors:0 dropped:0 overruns:0 carrier:0 > >> collisions:0 txqueuelen:0 > >> RX bytes:16987249 (16.2 MiB) TX bytes:16987249 (16.2 MiB) > >> > >> > >>How does one go about disabling that? > To entirely stop any form of IPv6 addressing from appearing, you need to block the module. Traditionally that is done in /etc/modprobe.conf by placing a line or lines of the form: alias ipv6 off alias net_pf_10 off The second line may or may not be needed anymore. I do not know if IPv6 is the "true cause" of your 5-second delay, but the line(s) in modprobe.conf are a more complete way to stop IPv6 addressing from appearing. HTH, --Rob -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
On Saturday 04 October 2008, [EMAIL PROTECTED] wrote: >Hello, > >You are using IPv4 ( If IPv6 disabled )... > >Edward. > Agreed Edward, but when it doesn't show the ipv6 addresses at all, the interface is brought up in milliseconds, as opposed to the 5 second lag it has now. That is the lag I would like to remove. Thank you. >Gene Heskett wrote: >>Greetings; >> >>In /etc/sysconfig/ifcfg-eth0 I have the line as in the subject, but I note >>that bringing up eth0, at a fixed ipv4 address in the 192.168 block, there >> is about a 5 second pause doing it, and ifconfig does report what looks >> like valid ipv6 addresses for both eth0 and lo. >> >>eth0 Link encap:Ethernet HWaddr 00:1F:C6:62:FC:BB >> inet addr:192.168.71.3 Bcast:192.168.71.255 Mask:255.255.255.0 >> inet6 addr: fe80::21f:c6ff:fe62:fcbb/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:52899 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:45100 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:34184438 (32.6 MiB) TX bytes:26737247 (25.4 MiB) >> Interrupt:22 Base address:0xa000 >> >>loLink encap:Local Loopback >> inet addr:127.0.0.1 Mask:255.0.0.0 >> inet6 addr: ::1/128 Scope:Host >> UP LOOPBACK RUNNING MTU:16436 Metric:1 >> RX packets:6888 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:6888 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:16987249 (16.2 MiB) TX bytes:16987249 (16.2 MiB) >> >> >>How does one go about disabling that? -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) "And do you think (fop that I am) that I could be the Scarlet Pumpernickel?" -- Looney Tunes, The Scarlet Pumpernickel (1950, Chuck Jones) -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: IPV6INIT=no, but does anyway on local network
Hello, You are using IPv4 ( If IPv6 disabled )... Edward. Gene Heskett wrote: >Greetings; > >In /etc/sysconfig/ifcfg-eth0 I have the line as in the subject, but I note >that bringing up eth0, at a fixed ipv4 address in the 192.168 block, there is >about a 5 second pause doing it, and ifconfig does report what looks like >valid ipv6 addresses for both eth0 and lo. > >eth0 Link encap:Ethernet HWaddr 00:1F:C6:62:FC:BB > inet addr:192.168.71.3 Bcast:192.168.71.255 Mask:255.255.255.0 > inet6 addr: fe80::21f:c6ff:fe62:fcbb/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:52899 errors:0 dropped:0 overruns:0 frame:0 > TX packets:45100 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:34184438 (32.6 MiB) TX bytes:26737247 (25.4 MiB) > Interrupt:22 Base address:0xa000 > >loLink encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:6888 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6888 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:16987249 (16.2 MiB) TX bytes:16987249 (16.2 MiB) > > >How does one go about disabling that? > > > -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
