|
i thought about that. ifconfig doesn't have an option for full
(or non-truncated) listings so i thought that was a dead end.
here's something that is really weird.
when i startup pulse and let all the virtual interfaces come up, then run:
ifconfig eth0:13
i get output, but no address. if i type
ifconfig eth0:13 up
it tells me it can't allocate the requested ip address.
that was starting to look like a config problem, as you suggested. then i
went in with a fine toothed comb and looked at all my ip's, grepped the
config files by the last octet (in this case 238, in X.X.X.238) and found
nothing. for grins i typed:
ifconfig eth0:13 X.X.X.239 up
and it came up fine.
so i went thru the config files with a fine toothed comb _again_ and found
no conflicts on either ip.
i shut down pulse, changed the config file to put eth0:13 up on the next
ip, X.X.X.239, and now everything works as expected. eth0:13 comes up,
ifconfig reports it, etc. etc. too weird. an ip black hole.
any thoughts?
<drew>
On Sun, 24 Feb 2002, Horms wrote:
> On Fri, Feb 22, 2002 at 01:13:46PM -0600, lvs-list-spam@xxxxxxxxx wrote:
> >
> > i just tried to add a 13th mapping across the lvs machine and an odd thing
> > happened.
> >
> > ifconfig only reports the first 12 eth0:N
> >
> > ifconfig eth0:13 shows the correct output, as if the interface was up.
> >
> > that 13th virtual interface doens't respond to ping and doesn't work
> > correctly wrt to hitting the servers behind the lvs box.
> >
> > i looked on google for a linux virtual interface limitation but couldn't
> > find anything.
> >
> > any ideas on possible problems and workarounds?
>
> What you are trying to do should work. I am suspecting that
> either you have made a slight error in your configuration, or
> have a kernel issue.
>
> ifconfig will often truncate the output of ip-aliases, but they
> should still work regardless.
>
>
|
