From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] IP aliasing problem
Date: Thu, 7 Oct 2010 09:32:27 -0700 [thread overview]
Message-ID: <AANLkTingSzBTDKbFr29YoQ1nmLwhwe6aB7L3Noz+PPJC@mail.gmail.com> (raw)
In-Reply-To: <3F408658-08E1-4D30-A7DA-4663CFEEC9B3@stellar.eclipse.co.uk>
>>>> ...I have 5 usable IPs from my host and I've defined 2 of them in /etc/conf.d/net like this:
>>>>
>>>> config_eth0=(
>>>> "1.2.3.1 netmask 255.255.255.0"
>>>> "1.2.3.2 netmask 255.255.255.0"
>>>> )
>>>>
>>>> My apache2 config is not working as expected and I think its due to a
>>>> networking problem because eth0:1 reports no RX or TX stats:
>>>>
>>>> # ifconfig
>>>> eth0 Link encap:Ethernet HWaddr [removed]
>>>> inet addr:1.2.3.1 Bcast:[removed] Mask:255.255.255.0
>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>>> RX packets:46047 errors:0 dropped:0 overruns:0 frame:0
>>>> TX packets:65703 errors:0 dropped:0 overruns:0 carrier:0
>>>> collisions:0 txqueuelen:1000
>>>> RX bytes:6131194 (5.8 MiB) TX bytes:82568335 (78.7 MiB)
>>>> Interrupt:40
>>>>
>>>> eth0:1 Link encap:Ethernet HWaddr [removed]
>>>> inet addr:1.2.3.2 Bcast:[removed] Mask:255.255.255.0
>>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>>> Interrupt:40
>>>
>> ...
>> Thank you for taking the time to write Stroller. This has really got
>> my head spinning. First of all, you're right about the netmask. It
>> is 255.255.255.248. I didn't have a good understanding of what a
>> netmask is so I thought it would be smart to change it for a public
>> message.
>>
>> The server is remote and hosted so I don't have any control over the
>> router or network. I've gone back and forth with the host but they
>> insist that everything is fine on their end.
>>
>> I'm confused because I have in apache2 config:
>>
>> <VirtualHost 1.2.3.1:443>
>> ...
>> SSLCertificateFile /etc/apache2/ssl/www.example1.com.crt
>> SSLCertificateKeyFile /etc/apache2/ssl/www.example1.com.key
>> ...
>
> Suggest you first establish you can ping *both* IPs.
Thanks Stroller. It's working now. I needed to define apache2's
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
- Grant
next prev parent reply other threads:[~2010-10-07 16:33 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 [this message]
2010-10-07 17:51 ` BRM
2010-10-07 19:53 ` Stroller
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=AANLkTingSzBTDKbFr29YoQ1nmLwhwe6aB7L3Noz+PPJC@mail.gmail.com \
--to=emailgrant@gmail.com \
--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