Very Computer

I have Kernel V2.2.1 up and running just fine.  PPP, Masq and all are
working ... its just that I have a strange side effect.

My Linux machine MASQ's for my kids Win3.11 machine via a PPP dialup
connection.  In order to make it flexible I IP alias the GATEWAY IP on
the same machine as my Linux IP address ... don't know why, I just
wanted to treat the GATEWAY x.x.x.1 address special.

When I ifconfig to view the ethernet devices only the primary eth0
(and of course lo and ppp0) show up, not the eth0:0 alias device.  The
alias device works, it can be "pinged" and the MASQ setup works fine
(the Win3.11 machine points to the x.x.x.1 GATEWAY interface).

The V2.0.36 load I was running previously worked just fine as well and
was visible in a normal fashion (with ifconfig).  Has anyone an
explaination or a fix for this situation.  Its more of a nuisance than
anything else.  I've been all through the /proc file system looking
for a reference BUT I can't find eth0:0 either.

I think all my utilities are upgraded enough.  I am a minor release
behind on a couple of things and some packages I don't have installed
at all ... this is per the V2.2.1 CHANGES file.

Thanks in advance for any pointers and/or help!

------------------------------------------------
  Doug Mitton - Brockville, Ontario, Canada
                'City of the Thousand Islands'


           http://www.*tap.com/dmitton
     User Group: http://www.veryComputer.com/
  SPAM Reduction: Remove "x." from my domain.
------------------------------------------------

I have Kernel V2.2.1 up and running just fine.  PPP, Masq and all are
working ... its just that I have a strange side effect.

My Linux machine MASQ's for my kids Win3.11 machine via a PPP dialup
connection.  In order to make it flexible I IP alias the GATEWAY IP on
the same machine as my Linux IP address ... don't know why, I just
wanted to treat the GATEWAY x.x.x.1 address special.

When I ifconfig to view the ethernet devices only the primary eth0
(and of course lo and ppp0) show up, not the eth0:0 alias device.  The
alias device works, it can be "pinged" and the MASQ setup works fine
(the Win3.11 machine points to the x.x.x.1 GATEWAY interface).

The V2.0.36 load I was running previously worked just fine as well and
was visible in a normal fashion (with ifconfig).  Has anyone an
explaination or a fix for this situation.  Its more of a nuisance than
anything else.  I've been all through the /proc file system looking
for a reference BUT I can't find eth0:0 either.

I think all my utilities are upgraded enough.  I am a minor release
behind on a couple of things and some packages I don't have installed
at all ... this is per the V2.2.1 CHANGES file.

Thanks in advance for any pointers and/or help!

------------------------------------------------
  Doug Mitton - Brockville, Ontario, Canada
                'City of the Thousand Islands'


           http://www.*tap.com/dmitton
     User Group: http://www.veryComputer.com/
  SPAM Reduction: Remove "x." from my domain.
------------------------------------------------

I have Kernel V2.2.1 up and running just fine.  PPP, Masq and all are
working ... its just that I have a strange side effect.

My Linux machine MASQ's for my kids Win3.11 machine via a PPP dialup
connection.  In order to make it flexible I IP alias the GATEWAY IP on
the same machine as my Linux IP address ... don't know why, I just
wanted to treat the GATEWAY x.x.x.1 address special.

When I ifconfig to view the ethernet devices only the primary eth0
(and of course lo and ppp0) show up, not the eth0:0 alias device.  The
alias device works, it can be "pinged" and the MASQ setup works fine
(the Win3.11 machine points to the x.x.x.1 GATEWAY interface).

The V2.0.36 load I was running previously worked just fine as well and
was visible in a normal fashion (with ifconfig).  Has anyone an
explaination or a fix for this situation.  Its more of a nuisance than
anything else.  I've been all through the /proc file system looking
for a reference BUT I can't find eth0:0 either.

I think all my utilities are upgraded enough.  I am a minor release
behind on a couple of things and some packages I don't have installed
at all ... this is per the V2.2.1 CHANGES file.

Thanks in advance for any pointers and/or help!

------------------------------------------------
  Doug Mitton - Brockville, Ontario, Canada
                'City of the Thousand Islands'


           http://www.*tap.com/dmitton
     User Group: http://www.veryComputer.com/
  SPAM Reduction: Remove "x." from my domain.
------------------------------------------------

I have Kernel V2.2.1 up and running just fine.  PPP, Masq and all are
working ... its just that I have a strange side effect.

My Linux machine MASQ's for my kids Win3.11 machine via a PPP dialup
connection.  In order to make it flexible I IP alias the GATEWAY IP on
the same machine as my Linux IP address ... don't know why, I just
wanted to treat the GATEWAY x.x.x.1 address special.

When I ifconfig to view the ethernet devices only the primary eth0
(and of course lo and ppp0) show up, not the eth0:0 alias device.  The
alias device works, it can be "pinged" and the MASQ setup works fine
(the Win3.11 machine points to the x.x.x.1 GATEWAY interface).

The V2.0.36 load I was running previously worked just fine as well and
was visible in a normal fashion (with ifconfig).  Has anyone an
explaination or a fix for this situation.  Its more of a nuisance than
anything else.  I've been all through the /proc file system looking
for a reference BUT I can't find eth0:0 either.

I think all my utilities are upgraded enough.  I am a minor release
behind on a couple of things and some packages I don't have installed
at all ... this is per the V2.2.1 CHANGES file.

Thanks in advance for any pointers and/or help!

------------------------------------------------
  Doug Mitton - Brockville, Ontario, Canada
                'City of the Thousand Islands'


           http://www.*tap.com/dmitton
     User Group: http://www.veryComputer.com/
  SPAM Reduction: Remove "x." from my domain.
------------------------------------------------

You will need to get the net-tools 1.50 package.

Incidentally if anyone is listening.. there's ALSO a bug in net-tools 1.50 (or
the kernel, not sure) that makes it take down the primary interface when you
take down the aliased interface.

For instance.

ifconfig eth0:0 10.10.10.1

produces.

eth0:0    Link encap:Ethernet  HWaddr 00:A0:C9:82:CE:CA
          inet addr:10.10.10.1  Bcast:10.255.255.255 Mask:255.0.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:19 Base address:0xfcc0

But when I do.

ifconfig eth0:0 down it takes away the eth0:0 AND eth0

The only way I've found to fix it is to take down eth0:0 with this:

ifconfig eth0:0 0.0.0.0

by setting it to use 0.0.0.0 it disappears from the interfaces list.

--
---------------------------------------------------------------------

       Powered by: Linux, the choice of a GNU generation

"Gosh that takes me back... or is it forward? That's the trouble with
time travel, you never can tell."
                -- Doctor Who "Androids of Tara"
---------------------------------------------------------------------

Thank you, this solved it!  I don't normally take down a single
interface though so I haven't seen the bug.

------------------------------------------------
  Doug Mitton - Brockville, Ontario, Canada
                'City of the Thousand Islands'

           http://www.*tap.com/dmitton
     User Group: http://www.veryComputer.com/
  SPAM Reduction: Remove "x." from my domain.
------------------------------------------------