ViciBox 3.0.8 no eth0, was present before 'os-install'

[marmu]

Hi my beloved support community,

I finally wanted to update my whole system with the current ViciBox 3.0.8 ISO. Booting the live-CD wasn't a problem, got network working, all fine. But after I installed the OS via "os-install" eth0 wasn't present. Can't use "ifconfig" or "yast lan". Yast says:
"unable to configure the network card because the kernel device (eth0, wlan0) is not present."

Before "os-install" I was able to use ssh and network worked well. I don't know why that is. I tried "os-install" two times, no luck

Help!

Cheers,
Marcus

[williamconley]

1) Post your motherboard model # please (helps us to find which ones work, and not, in case it's a compatibility issue with the install .iso drivers)

2) As a test, you could try installing opensuse from a standard opensuse install cd.

3) As a test, you could try to install GoAutoDial also

4) During the os-install, did you modify your networking parameters? (or leave the system using DHCP?)

[Kumba]

I've seen this happen during a warm-reboot. Usually rebooting the machine fixes it. Otherwise, I'm not sure what is going on. The kernel present during live-CD boot is the same as what is present on reboot.

[williamconley]

i think i've had technicians experience it when putting in wrong networking information, which causes eth0 to fail, thus the "keep dhcp" suggestion (if dhcp works, but manual network doesn't ... reserve the dhcp assigned address and work out whatever you are doing wrong some other day ... AFTER the system is online, since most are in a big hurry to get it UP to prove they can make money with Vicidial to their funding source)

[marmu]

@william:
Its kind of aN office PC "HP Compaq dc5100 Business PC"
hmm motherboard, good question. The chipset is
Intel 915GV Express chipset with Integrated Intel Graphics Media Accelerator 900. I know that the network chip is a broadcom netxtreme 5751.

Will try opensuse install cd after my current test install.

tried both ways, manual and DHCP configuration of the network cards. didn't work either way.

I now try to install it with all the hardware removed except the onboard ones and again using DHCP. But that shouldn't be helpful, since I really know my network config.

"os-install" just finished:
And again while booting "waiting for mandatory network devices: eth0 __NSC__"
Some counter running from 30-0 seconds and another error
FATAL: Module ip_tables not found.
iptables v1.4.8: can't initialize iptables table 'filter': iptables who? (do you need to insmod?)
Perhas iptables or your kernel need to be upgraded.

"ifconfig" only shows me "lo"
"lspci -vk" displays the broadcom netxtreme BCM5751 (my NIC)
"yast lan" displays the broadcom NIC 2 times
1x IP Address not configured
1x IP Address DHCP

I could only delete the DHCP one. I can't configure the other one. As I said before in my first post...
Yast says:
"unable to configure the network card because the kernel device (eth0, wlan0) is not present."

Any hints?

I will now try to install OpenSuse 11.3 (standalone) and see if the network works.

Thanks again guys. Hopefully this post isn't too long and keeps you of reading it
...strange things going on here in frosty Berlin

[williamconley]

Code: Select all

FATAL: Module ip_tables not found.

What did you answer for "turn off firewall"?

Try changing your answer (ip_tables is the firewall).

[marmu]

I know that ip_tables is the firewall. It was turned off, I didn't go to the general section of the network config. my bad. Ok, then I will now try again installing vicibox308 and activate the firewall. hopefully that helps.

For your info, installing opensuse 11.3 (not vicibox) worked well. NIC functioning as expected.

[williamconley]

actually, what i meant was that there is a question during the vicibox installation regarding the firewall, but if you are saying that this problem occurs before the vicibox-install ... perhaps you should try an earlier vicibox (3.01->3.07) to see if there is a piece missing from the os-install that causes your ip_tables to Not Load. (Heck try 2.0!)

[marmu]

ok, just tried it again. this is no fun anymore... I was running vicibox 2.0 and wanted to update. I could try vicibox 3.0.7, but where do I get it... I will find it somehow.

And I could try to get vicidial working with my fresh opensuse 11.3. But last time I tried (over 6 months ago), it was a pain in the ass and didn't go well. That is why I was so greatful for vicibox.

Further the installation of vicibox 3.0.8 messes with my grub installation.

EDIT: can't get vicibox 307
http://download.vicihost.com/iso/vicibo ... -3.0.7.iso - is down

though I got 3.0.6 on my hard disk

[williamconley]

http://download.vicidial.com/iso/vicibox/server/

[marmu]

ah ok, in the archive folder all version can be found. thanks a lot. but I think since I got vicibox 3.0.6 installed right now and it seems to work an update to 3.0.7 isn't worth a try, am I right?

something must be "wrong" with 3.0.8, since that couldn't be installed correctly...

[williamconley]

if you have a version that WORKED. leave it alone LOL.

the point of the vicibox installer is to install vicidial. after that, you HAVE vicidial. installing again with a newer version of the installer ... will still just install vicidial, no difference. no reason to mess with it.

vicidial itself can be upgraded/updated via svn (VICIDIAL Wiki at the top of this page, then click on SVN how to) at any time, so you'll never need to install again. However: get a spare P4 and practice installation and eventually even a "bad" installer won't stop you from installing, once you "get it". (install scripts can be interrupted, re-run, etc if you can get a handle on what's going on ... a spare P4 can be very handy in this regard for practice ... even a VMWare system can be used for this).

[marmu]

Never change a running system... But I thought a system which is up to date should always be the choice for security and performance reasons.

I think in the future I will only update the OS. Perhaps I will switch back to the old vicibox 2.0.0 I had up an running. Since I altered and created (my own) agi-scripts and PHP-files, updating the OS, vicidial, asterisk etc. via installing a newer vicibox isn't such a good idea at all.
Could you please tell me if I would miss a lot by not updating?

Too bad, I already invested a lot of time...

[williamconley]

Using Vicibox 2.0.0 vs 3.0.8 gets you a later version of the OS. But Vicidial (the actual software in question) will be the same. You can update/upgrade a Vicidial system from any version to any later version without reinstalling (allowing bringing your data with you).

Security is always an issue, but if you use iptables to limit access to ONLY friendly computers (carriers agents and managers only), security becomes a non-issue. Since this is not a "Publicly accessible web server", you do not need to expose yourself to public hacking exploiters at all. Just lock it down and security becomes a non-issue.

Performance is always a debate. I have clients still using Gentoo and/or Ubuntu from prior installations who have simply updated without reinstalling ... using systems with OS's that are three years old ... no issues at all.

So "never change" may be changed to "never wipe and start over". Since upgrades ARE reversible if you have done a full backup before you begin.

[okli]

Got exactly the same issue while playing with Vicibox redux 3.0.8 32 bit in VirtualBox 3.2.10.
On the same virtual machine 3.0.7 installed just fine.

[williamconley]

cool. now tell me WHY so we can have someone (hi gardo!) fix it if it is not a specific issue with virtual

[Kumba]

I can only duplicate this issue, after the os-install, sometimes, on virtual and hardware machines.

In all instances, power-cycling the machine fixed it, and I was not able to duplicate it past the install-phase.

I do not know why this occurs sometimes from the live-CD, but I have never had it persist beyond a power cycle.

[Jif19]

I too am experiencing this issue. The same hardware works fine when I use Vicibox 3.0.6 but not with 3.0.8. Following the reboot after the os-install I loose the network card as well as my usb keyboard. I am using an old Dell Optiplex GX280 P4 2.8 Ghz. But it looks to be reproducible if that helps. I can't do much without a keyboard so I will just use 3.0.6.

Vicibox 3.0.6 from .iso
Vicibox 3.0.8 from .iso

[marmu]

rebooting din't help at all with my network problems.

I loose the network card as well as my usb keyboard

I also got a PS2 keyboard connected, before I had an USB one.

I you need more information on my system, tell me.

I will now try to get back to my "old" state under opensuse 11.3. Meaning, I will copy some PHPs, AGIs and so on. Perhaps I will have to edit the new vicidial PHPs/AGIs, since I changed some from vicibox 2.0.0. Wish me luck. I think I won't reinstall in the future, just update the OS and perhaps vicidial. Too many adaptions were made.

Thanks again for vicidial, the support and vicibox. Hopefully I can contribute more in the future.

[williamconley]

if you already have a running system, updates without reinstall are always best. i've never had a problem with an update.

if you are building a new one (or debating a fresher install for some reason) practicing on a generic workstation PC first is always a good idea. if you don't have one available, practice on a VMWare machine a few times.

And ALWAYS use the vicidial backup system AND VERIFY THAT YOUR DATABASE IS INTACT BY INSTALLING AN ANOTHER MYSQL INSTANCE AND VIEWING THE DATA. The rest can always be "recreated", but the data ...

[Kumba]

Follow the instructions in this thread, see if the problem persists:

http://www.vicidial.org/VICIDIALforum/v ... hp?t=14672

[okli]

Follow the instructions in this thread, see if the problem persists:

http://www.vicidial.org/VICIDIALforum/v ... hp?t=14672

Nice, eth0 is back in game