Re: [Server-devel] XS 0.5 Second Attempt at eth1

2008-12-04 Thread Jerry Vonau
Anna wrote: > On Thu, Dec 4, 2008 at 6:29 PM, Jerry Vonau <[EMAIL PROTECTED]> wrote: > >> OK, I'm out of ideas, lets see if we can configure eth1 without bonding, >> not sure if this is nic driver issue with bonding, or what... >> >> backup the ifcfg-eth1 file, copy ifcfg-landbond0, ifcfg-lanbond0

Re: [Server-devel] XS 0.5 Second Attempt at eth1

2008-12-04 Thread Anna
On Thu, Dec 4, 2008 at 6:29 PM, Jerry Vonau <[EMAIL PROTECTED]> wrote: > > OK, I'm out of ideas, lets see if we can configure eth1 without bonding, > not sure if this is nic driver issue with bonding, or what... > > backup the ifcfg-eth1 file, copy ifcfg-landbond0, ifcfg-lanbond0:1 > ifcfg-lanbond

Re: [Server-devel] XS 0.5 Second Attempt at eth1

2008-12-04 Thread Jerry Vonau
Anna wrote: > Not having done this before, and after getting syntax errors and command not > found for speed, I googled and edited > /etc/sysconfig/network-scripts/ifcfg-eth1 like so. I figured 100 might be a > good place to start. I haven't tried half duplex yet, but I can if you > think that wo

Re: [Server-devel] XS 0.5 Second Attempt at eth1

2008-12-04 Thread Anna
Not having done this before, and after getting syntax errors and command not found for speed, I googled and edited /etc/sysconfig/network-scripts/ifcfg-eth1 like so. I figured 100 might be a good place to start. I haven't tried half duplex yet, but I can if you think that would do anything. ETHT

Re: [Server-devel] XS 0.5 Second Attempt at eth1

2008-12-04 Thread Reuben K. Caron
Thanks for clarification. Still no go: Dec 4 12:12:24 schoolserver1 kernel: eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1 Dec 4 12:12:24 schoolserver1 kernel: eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1 Dec 4 12:12:24 schoolserver1 kernel: Ethernet Channel Bonding Driver: v3.3.0 (June 10,

Re: [Server-devel] XS 0.5 Second Attempt at eth1

2008-12-04 Thread Jerry Vonau
Jerry Vonau wrote: > Reuben K. Caron wrote: >> I too am having problems with DHCP (and ejabberd) on XS 0.5. >> >> Let me detail my steps >> >> Appended upgradeany- ran default install >> Restarted >> NICs were swapped. >> Ran xs-swapnics >> >> Check var/log/messages found (snipet): >> >> Dec 4 09:

Re: [Server-devel] XS 0.5 Second Attempt at eth1

2008-12-04 Thread Jerry Vonau
Reuben K. Caron wrote: > I too am having problems with DHCP (and ejabberd) on XS 0.5. > > Let me detail my steps > > Appended upgradeany- ran default install > Restarted > NICs were swapped. > Ran xs-swapnics > > Check var/log/messages found (snipet): > > Dec 4 09:36:58 schoolserver1 dhcpd: Li

Re: [Server-devel] XS 0.5 Second Attempt at eth1

2008-12-04 Thread Jerry Vonau
Anna wrote: > I tried the XS 0.5 install on another box to see if the LAN issues on my > previous attempt were a hardware problem or something. It's a different > model Dell with 2 nics. > > Here are my notes: > > Basic install from the CD, text mode, default everything. > > Boot up, then: > /e

Re: [Server-devel] XS 0.5 Second Attempt at eth1

2008-12-04 Thread Reuben K. Caron
I too am having problems with DHCP (and ejabberd) on XS 0.5. Let me detail my steps Appended upgradeany- ran default install Restarted NICs were swapped. Ran xs-swapnics Check var/log/messages found (snipet): Dec 4 09:36:58 schoolserver1 dhcpd: Listening on LPF/lanbond0/00:00:00:00:00:00/172.1

Re: [Server-devel] XS 0.5 Second Attempt at eth1

2008-12-04 Thread Martin Langhoff
2008/12/3 Anna <[EMAIL PROTECTED]>: > Has anyone gotten eth1 on XS 0.5 working? I have, at least on 4 different bits of hw, but I worked on it too much to be a good tester of it. Others have installed successfully. One thing that 0.5 has is that it almost always picks the ordering of the NICs _in

Re: [Server-devel] Networking on Version 0.5 .

2008-12-04 Thread Martin Langhoff
On Wed, Dec 3, 2008 at 3:28 PM, Jerry Vonau <[EMAIL PROTECTED]> wrote: > Ensure that you set both the role and domain name for the server while > the network is stopped, saves seeing some error messages when you > restart, then (re)start the network and restart all the web based > services. or you