I've spent the last few house struggling with WANem in VMplayer, using bridged networking.
The installation boots up and asks the right questions and I answer yes to the DHCP question. But nine times out of ten, it ends up without eth0 configured correctly and without anything in the routing table.
If I "exit2shell" then do ifdown eth0 followed by ifup eth0, I get connectivity, inet address and routing table entries.
However, if I then set up routes on the two external machines (one of which is the VM host) to route through WANem, routing fails. Once - just once - I did "nat add eth0" in the console and routing started working, for about a minutes. Then it stopped, and I haven't been able to get it working since.
In desperation, I tried using a static IP at WANem boot, but all that did was give me the message "unable to set IP address".
Surely it shouldn't be this difficult/unreliable….nobody else seems to have these problems. Why would eth0 fail to configure but very occasionally succeed, given it's a boot from the same iso every time? And presumably failure to nat is just a consequence of the failure to get eth0 up.
Often, apache also fails to work when eth0 fails, even after an ifup. "reset" in the console usually gets this working.
My setup is Windows 7 64 bit, running VM player, with the latest WANem VM.
Simon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thats something interesting. It is difficult to point out the issue as WANem seems to be working at times. So, this does not seem to be a WANem problem.
Can you try downgrading the version of VMPlayer? Or alternatively, try using the WANem version 2.3 iso with VMWare Server or Virtualbox.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the reply. I tried it in Virtualbox, and this time eth0 sets up OK, I get the WANem web page up OK, but clicking on the links (e.g. Basic Mode) just times out. Tried it three times.
Whatever is causing this, it's taken up two days and got nowhere. Guess I'll have to use something else.
Simon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I've spent the last few house struggling with WANem in VMplayer, using bridged networking.
The installation boots up and asks the right questions and I answer yes to the DHCP question. But nine times out of ten, it ends up without eth0 configured correctly and without anything in the routing table.
If I "exit2shell" then do ifdown eth0 followed by ifup eth0, I get connectivity, inet address and routing table entries.
However, if I then set up routes on the two external machines (one of which is the VM host) to route through WANem, routing fails. Once - just once - I did "nat add eth0" in the console and routing started working, for about a minutes. Then it stopped, and I haven't been able to get it working since.
In desperation, I tried using a static IP at WANem boot, but all that did was give me the message "unable to set IP address".
Surely it shouldn't be this difficult/unreliable….nobody else seems to have these problems. Why would eth0 fail to configure but very occasionally succeed, given it's a boot from the same iso every time? And presumably failure to nat is just a consequence of the failure to get eth0 up.
Often, apache also fails to work when eth0 fails, even after an ifup. "reset" in the console usually gets this working.
My setup is Windows 7 64 bit, running VM player, with the latest WANem VM.
Simon
Thats something interesting. It is difficult to point out the issue as WANem seems to be working at times. So, this does not seem to be a WANem problem.
Can you try downgrading the version of VMPlayer? Or alternatively, try using the WANem version 2.3 iso with VMWare Server or Virtualbox.
Hi
Thanks for the reply. I tried it in Virtualbox, and this time eth0 sets up OK, I get the WANem web page up OK, but clicking on the links (e.g. Basic Mode) just times out. Tried it three times.
Whatever is causing this, it's taken up two days and got nowhere. Guess I'll have to use something else.
Simon
Try restarting the Apache by using the reset command from the wanem console. It should help.