similar to: /etc/gai.conf fails to prefer IPv4 over IPv6 for NFS

Displaying 20 results from an estimated 800 matches similar to: "/etc/gai.conf fails to prefer IPv4 over IPv6 for NFS"

2018 Jun 08
2
/etc/gai.conf fails to prefer IPv4 over IPv6 for NFS
In article <669037eb-029c-eb3b-0c60-6a5121142bb8 at gmail.com>, Gordon Messmer <centos at centos.org> wrote: >On 06/08/2018 10:42 AM, Steve Rikli wrote: > >> I found posts from others in a similar situation, and proposed solutions >> included modifying /etc/gai.conf to use: >> >> precedence ::ffff:0:0/96 100 > > From my reading of that file,
2018 Jun 09
2
/etc/gai.conf fails to prefer IPv4 over IPv6 for NFS
In article <bc751efa-07f1-91de-9248-5f90f961bcb4 at gmail.com>, Gordon Messmer <centos at centos.org> wrote: >On 06/08/2018 03:23 PM, Steve Rikli wrote: >> >> This seems the most likely explanation, I'd just like to know for certain >> before I give up on gai.conf and restort to disabling IPv6 or other >> workarounds (e.g. /etc/nfsmount.conf). >
2018 Jun 08
0
/etc/gai.conf fails to prefer IPv4 over IPv6 for NFS
On 06/08/2018 10:42 AM, Steve Rikli wrote: > I found posts from others in a similar situation, and proposed solutions > included modifying /etc/gai.conf to use: > > precedence ::ffff:0:0/96 100 > From my reading of that file, you'd need to uncomment all of the default precedence lines, and modify the last one.? You couldn't use that one line, alone.? It's hard
2018 Jun 09
0
/etc/gai.conf fails to prefer IPv4 over IPv6 for NFS
On 06/09/2018 07:51 AM, Steve Rikli wrote: > > I had hopes for gai.conf as the more universal solution, but apparently > it's not useable here. gai.conf works as intended for most applications, here.? For example, if I uncomment the block of "precedence" lines, and swap between "10" and "100" for the last line, then "telnet www.google.com 80"
2018 Jun 09
0
/etc/gai.conf fails to prefer IPv4 over IPv6 for NFS
On 06/08/2018 03:23 PM, Steve Rikli wrote: > > This seems the most likely explanation, I'd just like to know for certain > before I give up on gai.conf and restort to disabling IPv6 or other > workarounds (e.g. /etc/nfsmount.conf). Have you tried specifying "proto=tcp" as a mount option?? That *should* limit the client to IPv4.
2008 May 14
4
Default PXE boot timeout
Hello all, I have a NFSroot'ed a couple of OS platforms so that servers can have the option (web access) to: a. boot off a CentOS NFS root over the network b. or LOCAL hardrive (FreeBSD). A Simple script controls this so that if user selects NFS root - - /etc/dhcpd.conf will be updated to include the filename "pxelinux.0" parameter and it will find its configuration file based
2001 Dec 01
4
Control Panels
Me again... Is it possible to run a control panel in wine? ta. -- ********************************************** Warning: Anti-spam e-mail addy in force. Bring back MST3K!
2014 Jan 17
2
[LLVMdev] Do all user-written passes have to be run through a PassManager object (called from outside the LLVM infrastructure)?
Thanks John. Out of curiosity, I wonder if it's possible to summarize the LLVMpass-specific design patterns. I.e., the software engineering techniques that were used to design/implement the LLVM Pass Infrastructure. Equivalently, this may also answer the question "Why is the code this way". This visibility can improve understanding and that is likely to improve quality as more
2023 Apr 03
1
pxelinux takes too long trying all the config file options
On Mon, Apr 03, 2023 at 12:52:41PM -0400, Rob Roschewsk via Syslinux wrote: > Hi All, > > I have a situation where I want to netboot and ONLY use pxelinux.cfg/default. > > It seems to take FOREVER for pxelinux to try all of the config file > file options before falling through to default .... trying each > possible combination multiple times ... increasing the wait time >
2015 Jun 13
1
Testin new installation
On 06/13/2015 01:41 PM, Steve Matzura wrote: > On Sat, 13 Jun 2015 10:36:21 -0600, you wrote: > >> Look at /etc/hosts ::1 is the ipv6 version of localhost. > Right. I actually knew that. So why does that take precedence for the > definition of localhost even though it's not the first line in the > file? IPv6 is preferred when available. See man 5 gai.conf
2023 Nov 20
1
tftp problems
I've used TFTP server on CentOS/RHEL 7 and 8 but not 9, so take my notes with the appropriate grain of salt... JIC, confirm on the TFTP server you have a process socket for it, e.g. $ netstat -a | grep tftp udp 0 0 0.0.0.0:tftp 0.0.0.0:* Your 'systemctl status' output implies things are OK, but worth a check. I don't see a "tftpboot" symlink
2020 Aug 11
3
ipv6 NAT; accept_ra errors and about network choice
Hello, Firstly THANK YOU for the IPv6 NAT support merged in 6.5. It has been almost impossible to get IPv6 into a VM on a laptop that switches between wifi and wired (dock) connections, because you can not add a wifi interface to a bridge. I know NAT is against the IPv6 end-to-end xen but it makes this "just work" for the vast majority of people like me who need to ssh/curl/talk to
2005 Oct 24
7
More than 1 gcc version?
Hi CentOS4.2 - Is it possible to have an older version of gcc as well as the one that ships with this OS? I need to compile aspseek to run on this distro but it seems to only like older gcc's any ideas?
2014 Jan 16
3
[LLVMdev] Do all user-written passes have to be run through a PassManager object (called from outside the LLVM infrastructure)?
I have written several passes that have no pre-requisites for any previous LLVM native passes prior to my own. For those passes, I have verified that at least the following two approaches are equivalent in terms of executing those self-written passes and getting the correct results: #if METHOD_1 PassManager PM;
2002 Nov 05
2
2.5.6 release
On Tue, Nov 05, 2002 at 08:37:00AM -0800, Martin Pool wrote: > On 10 Oct 2002, "Green, Paul" <Paul.Green@stratus.com> wrote: > > No new CVS messages have appeared on the rsync-cvs archives since August > > 30th. This seems rather odd-- perhaps a daemon stopped working? If there > > has truly been no activity since that date, I apologize for > >
2005 Nov 14
3
Minimal installation How-to?
Hi all I would like to install the minimal level of Centos, with yum & selinux on my servers during the basic install from CD with Anaconda and then use yum to install whatever application is major on that server, so that yum installs its dependencies only, thus keeping to the target of installing only what is needed on a server. Please advise pros/cons of this approach and how to do it. I
2005 Nov 16
12
SELinux threads, cynicism, one-upmanship, etc.
After reading through the various SELinux threads, I really became quite perturbed. I mean, really quite perturbed. As an IT Director (and the entire IT department, currently), if I were hiring a sysadmin I know for a fact that someone whose first response to a question on why something doesn't work is 'turn it off' would not get a job here. Neither would a sysadmin with as much
2003 Jul 05
2
Unhelpful error message when matching hosts in access list [PATCH]
Greetings, As previously reported by me to the Debian bug tracking system: ---------------------------------------------------------------------- An access list in rsyncd.conf may contain hostnames as well as addresses. It may contain several patterns to match against. address_match (in access.c) does this by trying to match hostname and address against each of the patterns until a match is
2005 Sep 19
8
upgrade problem
Currently we have RH7.3 with compiler gcc 2.96.x My mission, should I choose to accept it, involves moving our embedded application to CentOS 4.1 with gcc 3.x Problem is that about 1/2 million lines of code that gcc 2.96 accepts gives fatal fits to the gcc 3.x compiler from CentOS 4.1 I don't know how many fatal fits, as some disguise others etc. "Can't find register to
2015 Mar 02
3
Update
Hi Sandy, Thanks! Curious. Do you have any other interfaces? ifconfig -a should show them all including loopback. What is puzzling me is that it should not even attempt to use IPv6 to reach a global address when it only has a link-local address. It should gracefully fall back to IPv4 (as per RFC 6724 or RFC 3484 depending on the kernel version). Since you have an IPv4 address and I assume an