OpenVZ Forum: Users » Would a hardware change break LAN configuration?

Home » Mailing lists » Users » Would a hardware change break LAN configuration?

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Would a hardware change break LAN configuration? [message #11851]

Tue, 10 April 2007 04:11

jarcher
Messages: 91
Registered: August 2006
Location: Smithfield, Rhode Island

Member

Hi All…

I have a SuperMicro system running OpenVZ on Debian Etch AMD64. It has 2
ethernet ports on the system board. Recently, I added a PCI-X dual port
Ethernet card. I was unable to make these two ports talk to the network
and also, this addition caused the VPSes to be unable to talk to the LAN.
I deconfigured the new ports in /etc/network/interfaces and fixed it after
a reboot.

Is there any reason OpenVZ would have caused this? I can’t seem to find
an alternative cause but I can’t see why OpenVZ would do it either.

Thanks…

Report message to a moderator

Re: Would a hardware change break LAN configuration? [message #11854 is a reply to message #11851]

Tue, 10 April 2007 06:41

dev
Messages: 1693
Registered: September 2005
Location: Moscow

Senior Member

Jim,

No OpenVZ doesn't affect networking directly
Most likely you have misconfigured something.
it can be different situations:
- e.g. devices were renamed after the addition. i.e. eth0 become eth2 etc.
and settings are applied to wrong devices.
- VPSs can stop talking to LAN if default routing is via these unworking devices.
- etc. etc. etc.
to be able to resolve it we need dmesg from both boots (with and w/o PCI-X),
and 2 outputs of:
# ip a l
# ip r l
# iptables -L
# iptables -L -t mangle

Thanks,
Kirill

Jim Archer wrote:
> Hi All…
>
> I have a SuperMicro system running OpenVZ on Debian Etch AMD64. It has 2
> ethernet ports on the system board. Recently, I added a PCI-X dual port
> Ethernet card. I was unable to make these two ports talk to the network
> and also, this addition caused the VPSes to be unable to talk to the LAN.
> I deconfigured the new ports in /etc/network/interfaces and fixed it after
> a reboot.
>
> Is there any reason OpenVZ would have caused this? I can’t seem to find
> an alternative cause but I can’t see why OpenVZ would do it either.
>
> Thanks…
>
>

Report message to a moderator

Re: Would a hardware change break LAN configuration? [message #11886 is a reply to message #11854]

Tue, 10 April 2007 21:41

jarcher
Messages: 91
Registered: August 2006
Location: Smithfield, Rhode Island

Member

Thanks Kirill, I'll investigate further before disturbing the list again.

Jim

--On Tuesday, April 10, 2007 10:54 AM +0400 Kirill Korotaev <dev@sw.ru>
wrote:

> Jim,
>
> No OpenVZ doesn't affect networking directly
> Most likely you have misconfigured something.
> it can be different situations:
> - e.g. devices were renamed after the addition. i.e. eth0 become eth2 etc.
> and settings are applied to wrong devices.
> - VPSs can stop talking to LAN if default routing is via these unworking
> devices. - etc. etc. etc.
> to be able to resolve it we need dmesg from both boots (with and w/o
> PCI-X), and 2 outputs of:
># ip a l
># ip r l
># iptables -L
># iptables -L -t mangle
>
> Thanks,
> Kirill
>
> Jim Archer wrote:
>> Hi All…
>>
>> I have a SuperMicro system running OpenVZ on Debian Etch AMD64. It has
>> 2 ethernet ports on the system board. Recently, I added a PCI-X dual
>> port Ethernet card. I was unable to make these two ports talk to the
>> network and also, this addition caused the VPSes to be unable to talk
>> to the LAN. I deconfigured the new ports in /etc/network/interfaces and
>> fixed it after a reboot.
>>
>> Is there any reason OpenVZ would have caused this? I can’t seem to
>> find an alternative cause but I can’t see why OpenVZ would do it
>> either.
>>
>> Thanks…
>>
>>

Report message to a moderator

Previous Topic:	Wrong links for downloads
Next Topic:	Need help understanding kernel version numbers

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Apr 27 06:23:41 GMT 2024

Total time taken to generate the page: 0.02595 seconds