firewall

Sort of what I'm asking is "how to make a software firewall for Windows," but something not so complex. I'm surprised I can find so little when searching for this, only the occasional mention of hooks. So it'd be much appreciated if someone could point me in the right direction. I expect to do this with C (though if there's another language you think would work better, I'm all ears). I want to make an application that watches network traffic, can extract the IP address (source for incoming, destination for outgoing), and can block said network activity. This seems like something that would be

I've got some questions regarding hole punching with UDP. Based on the wiki http://en.wikipedia.org/wiki/UDP_hole_punching 1) To set up a UDP session between two parties (the client which is behind NAT, server which is non-NAT) does the client simply have to send a packet to the server and then the session is allowed both ways (send & receieve) through the firewall? Meaning the client can receive too from the server. 2) UDP Hole punching: Two clients first conenct to the server, then the server gives a client port / ip on to other clients, so the clients send packets to each other on those

I have written a simple Java application that interacts with multiple instances of itself using sockets. The first instance automatically takes on the role of the server, listening on a specific port, and all subsequent instances connect to it. The problem I'm faced with is that Windows Firewall pops up asking me if I want to unblock the program from "accepting incoming network connections". The thing is: it doesn't matter if you leave the application blocked , because the instances of the application are always on the same machine, so it will always work. Can I inform Windows somehow that I

I have a considerably large application that uses MSDTC. How many ports should I open? Is there any way to determine it? EDIT: I know what ports I need to open, I don't know how many I need. I think Migol wants to know how big the range of the RPC dynamic port allocation should be. In the KB they mention a minimum of 100 ports Furthermore, previous experience shows that a minimum of 100 ports should be opened, because several system services rely on these RPC ports to communicate with each other. So I would design a benchmark application to test different values of your dynamic range. When we

I've got an SSH tunnel setup on my macbook, like this... $ ssh -o ServerAliveInterval=3 -N -L 22222:gitosis-server:22 user@firewall.domain.com So I can ssh to localhost:22222 and will end up on the gitosis-server behind the firewall. I've created a local id_rsa.pub file, copied it into the gitosis server(running Centos5), and imported it into gitosis using... # sudo -H -u gitosis gitosis-init It was successful as I can see the public key in /var/lib/gitosis/.ssh/authorized_keys. Back on my macbook I setup a ~/.ssh/config file with the following... Host gitosis-server Hostname localhost

When I turn off the firewall, I can access my XAMPP website through other LAN computers. When I turn on firewall then I cannot connect to the machine anymore. Could someone tell me what's happening? my os is windows xp. thanks. Go to Control panel - > go to Windows Firewall -> then Advance Settings -> Click Inbound Rules right Click the inbound rules and select "New Rule..." select option port and click next select all local ports or your port number for apache server. and click next select option allow the connection and click next next Give name Allow All Local Port For Xampp Try This, I