Tuesday, March 15, 2011

Summary for Iteration 3

we focused on the webserver , port forward and firewall entry on the iteration 3 of firewall project .On webserver part ,we had a webserver installed ,created a web page ,and we also created upload section for our customer. port forward is a difficult part ,it took some time to fix it .we also monitored the firewall entry.
Next we are going to test NAT and something the end part of this project.

Webserver port forward

The webserver can now be successfully accessed from the outside world. Here's the right configuration we used.

The right adapters for the WAN and LAN interfaces.
Adapter card type: Intel PRO/1000 MT Desktop

DHCP server gives IPs in the range 192.168.1.100/199 .

Currently there are two machines connected, our webserver and a machine representing a client.

Now let's take a look at the actual port forwarding part.
So far just a simle rule was added that enables ouside access of the webserver.

Ofcourse we also need a rule that forwards the HTTP port 80 on the VirtualBox router. We do that in the Settings of our pfSense machine (Network -> Advanced -> Port Forwarding)

And here's the actual result. The webserver is reached on a machine on the external network (a.k.a. the Internet).

update tasklist for iteration 3

update tasklist done
make summery of iteration 3
decide in security level
define subnet for client and server working
configure NAT working
configure proxy filtering
test network
set rules for firewall
confiigure network inc privat network and NAT done
test network from inside and outside
allow upload section on webpage done
allow easy editing of the web page done
configure port forwarding working
correct requirements stake holders block diagram done
make database of members done
loging to logserver done
do customer meeting done

Editing Webpage

The customer wanted to have the ability to edit pages easily, without going through editing the HTML coding, so in order to do that a open source program Kompozer was used. Before choosing it, there was the plan to create such a program, but it turned out that it will take a lot of time, so the group sticked to the usage of Kompozer. Kompozer is simple program which integrates with the webpages and edits them directly, it doesn't have a database. The user is able to do a lot of changes to the webpages like adding likns, backround, editing text, adding pictures and a lot more things. The interface of the program is pretty simple, there is a print screen below which shows it:




Source: http://kompozer.net/

Monday, March 14, 2011

Port forward problems follow up

I'm gonna try to describe the tiny issues that bugged us so much and took so much time to fix as an attempt to help someone who does not have the expirience of working with pfSense and port forwarding, because even the simplest things need a lot of time when you don't know how they work.

I want to start with the adapter types.
KNOW WHAT TYPE ARE YOU USING AND BE SURE IT IS THE RIGHT ONE!
Otherwise a full load of cr*p may go wrong. Unfortunately we found out the hard way. Here are the problems we encountered when using an unsuitable adapter card:


DHCP does not give IP.


The adapter types not detected.


Now the port forwarding part. When you enter your rules choose the right network interface that ought to be used.

Otherwise the result may be painful. It is possible that the pfSense stops functioning, because, let's face it, you are playing with it's IP.


For other port forward troubleshooting problems see the link below.
http://doc.pfsense.org/index.php/Port_Forward_Troubleshooting

Friday, March 11, 2011

Stuck on port forwarding

Every attempt on making the webserver reachable from the outside world (the world outside our internal network) using port forwarding in the pfSense simply failed so far. There was a moment it actually worked for a couple of seconds, when bridged interface on a cabled connection was used, but then we switched to wireless and it crashed again.

For the setting up part we used the information found on Group 1 (Group V.O.J.E.V.) 's blog. Here's a link to the certain entry:
http://vojev.wordpress.com/2011/02/28/enable-port-forwarding-virtualbox/

This is the simple rule that was added to enable the connection to the webserver through our router (pfSense):

How to forward ports and add rules see here: http://doc.pfsense.org/index.php/How_can_I_forward_ports_
with_pfSense%3F

There were help attempts from people who already managed to do this but unfortunately they failed too. Is it the system unstable, I don't know, but were working on fixing this nasty issue with all we've got and looking for other help if possible.

Monitor / logging firewall entry

For logging the entry's going through the firewall we are going to use Snort.
Snort is a program that can perform protocol analysis and content searching/matching. It can be used to detect a variety of attacks and probes, such as buffer overflows, stealth port scans, CGI attacks, SMB probes, OS fingerprinting attempts, and much more.

Snort can operate in three modes; it can operate as a packet sniffer, a packet logger, and an IDS.



http://www.snort.org/

More info How to set Snort in PFsense can be found :
http://doc.pfsense.org/index.php/Setup_Snort_Package#Setting_up_snort_package_for_the_first_time

More files, logs and settings will be add'et later