Ticket #90 (closed bug: invalid)

Opened 1 year ago

Last modified 1 year ago

Verifying the Firewall VM

Reported by: devinbhullar@gmail.com Assigned to: kindlund
Priority: low Milestone: 0.9
Component: Documentation Version: 0.99
Severity: none Keywords: firewall, honeywall, verifying
Cc:

Description (Last modified by kindlund)

Hi Darien

I managed to chown the firewall-2 directory to be devinder:admin.

The Firewall VM starts and I had logged in as "roo" using password "password", but I cant see anything when I type: 

$ ps ax | grep startFW | grep -v grep

—Devinder

Attachments

Screenshot-1.png (243.5 kB) - added by Devinder <devinbhullar@gmail.com> on 09/02/07 21:59:25.
Screenshot.png (226.2 kB) - added by Devinder <devinbhullar@gmail.com> on 09/02/07 22:00:03.

Change History

08/30/07 09:39:30 changed by kindlund

  • status changed from new to assigned.
  • description changed.
  • reporter changed from Devinder <devinbhullar@gmail.com> to devinbhullar@gmail.com.
  • component changed from HoneyClient::Manager::FW to Documentation.
  • summary changed from Firewall to Verifying the Firewall VM.
  • priority changed from normal to low.
  • version changed from none to 0.99.
  • milestone set to 0.9.
  • keywords set to firewall, honeywall, verifying.

Hi Devinder,

That is odd.

Okay, can you post your output of just "ps ax" ? Once I have that, I can try to figure out why it's not there.

Keep in mind that it may take a little time for the firewall to fully start up. Once you power this VM on, it may take about 3 minutes for the perl script to run. However, if it still is not running, then something may be wrong when it booted up.

Regards,

— Darien

09/02/07 21:59:25 changed by Devinder <devinbhullar@gmail.com>

  • attachment Screenshot-1.png added.

09/02/07 22:00:03 changed by Devinder <devinbhullar@gmail.com>

  • attachment Screenshot.png added.

09/02/07 22:07:59 changed by Devinder <devinbhullar@gmail.com>

Hi Darien

I has uploaded the screen captures from the firewall-2 VM

$ps ax

Regards, Devinder

09/03/07 12:55:58 changed by kindlund

Hi Devinder,

Okay, I think I understand the problem. It seems that the perl code inside the Firewall VM did not automatically start. This is usually the result of some service significantly failing at startup.

As you requested, we can try to troubleshoot this specific problem over IM. I'll be sure to get online when I can. In the meantime, you can reboot the Firewall VM and see if you notice any specific failures upon startup. When the VM is fully booted up, you can use SHIFT+PageUp and SHIFT+PageDn keys to scroll through the screen buffer, to take screenshots of any failed services.

Hope this helps,

— Darien

09/04/07 00:10:33 changed by kindlund

  • status changed from assigned to closed.
  • resolution set to invalid.

Okay, after chatting directly with Devinder, we narrowed down the problems to be:

1) Devinder did not follow Step 8 in this section of the UserGuide: http://www.honeyclient.org/trac/wiki/UserGuide#ConfigureVMwareServer

As such, the dhcpd server running on vmnet1 was not properly configured.

2) Additionally, there was another VM running in additional to the "Firewall VM" that had already claimed the IP address of 10.0.0.254. Had the dhcpd server been configured properly, this IP address would have never been issued.

Closing this ticket.

Add/Change #90 (Verifying the Firewall VM)




Change Properties
Action