From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] IP aliasing problem
Date: Thu, 7 Oct 2010 20:53:39 +0100 [thread overview]
Message-ID: <6618B87A-60A7-493B-BD8D-83C45B9305BA@stellar.eclipse.co.uk> (raw)
In-Reply-To: <810692.43662.qm@web51906.mail.re2.yahoo.com>
On 7 Oct 2010, at 18:51, BRM wrote:
>> ServerName differently for each VirtualHost. Strangely though, I
>> still don't get stats for RX/TX from ifconfig:
>>
>> eth0 Link encap:Ethernet HWaddr [removed]
>> inet addr:1.2.3.1 Bcast:[removed] Mask:255.255.255.248
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> RX packets:923677 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:1444212 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:1000
>> RX bytes:124904402 (119.1 MiB) TX bytes:1880087116 (1.7 GiB)
>> Interrupt:40
>>
>> eth0:1 Link encap:Ethernet HWaddr [removed]
>> inet addr:1.2.3.2 Bcast:[removed] Mask:255.255.255.248
>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>> Interrupt:40
>
> Remember eth0:1 is an alias for eth0.
>
> Your above info is slightly wrong in that eth0 should be listed as eth0:0; where
> instead ifconfig is showing eth0 generic information and eth0:0 information
> combined.
> That's probably the source of your confusion.
On a system running 2.4.25 here I have:
$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:02:A5:1B:01:59
inet addr:213.x.y.91 Bcast:213.x.y.95 Mask:255.255.255.248
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:211366804 errors:0 dropped:0 overruns:0 frame:0
TX packets:306200382 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1542358934 (1470.9 Mb) TX bytes:1547826181 (1476.1 Mb)
Interrupt:20 Base address:0xd000
eth0:1 Link encap:Ethernet HWaddr 00:02:A5:1B:01:59
inet addr:192.168.1.43 Bcast:192.168.255.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:211366804 errors:0 dropped:0 overruns:0 frame:0
TX packets:306200384 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1542358934 (1470.9 Mb) TX bytes:1547826521 (1476.1 Mb)
Interrupt:20 Base address:0xd000
lo Link encap:Local Loopback
...
The same TX & RX are shown for both interfaces.
I don't know whether the tools have changed much since those I'm using on this box, but the difference *might* be that Grant's IPs are on the same subnet. I *think* it's possible for the route (as in: `man route`) to configure packets that come in on 1.2.3.2 to be replied to via 1.2.3.1.
You might set up a spare test box to see how current ifconfig displays packets, comparing aliased addresses on the same and separate subnets.
Stroller.
next prev parent reply other threads:[~2010-10-07 19:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 18:02 [gentoo-user] IP aliasing problem Grant
2010-10-06 21:52 ` Stroller
2010-10-06 22:17 ` Grant
2010-10-06 23:12 ` BRM
2010-10-06 23:34 ` [gentoo-user] " walt
2010-10-07 1:48 ` [gentoo-user] " Michael Orlitzky
2010-10-07 3:02 ` Grant
2010-10-07 7:32 ` Stroller
2010-10-07 16:32 ` Grant
2010-10-07 17:51 ` BRM
2010-10-07 19:53 ` Stroller [this message]
2010-10-08 17:13 ` Grant
2010-10-09 8:50 ` Adam Carter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6618B87A-60A7-493B-BD8D-83C45B9305BA@stellar.eclipse.co.uk \
--to=stroller@stellar.eclipse.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox