Transparent firewall & DHCP

dracunciliasis

The network we have back home, I mean among us in a small village is in the following figure, all DHCP clients have a P2P DC++ (direct connect) client running, which is connected to an internal P2P DC++ (direct connect) server (not accessible from the WWW; i.e. really internal), the only P2P client connected to the WWW is a EMULE server.

At the beginning we only had PFSENSE1 and everything was working fine but the network grew and we add the two new pfsense's (PFSENSE2 and PFSENSE3). Now the problem is computers begin PFSENSE2 and PFSENSE3 cant access the emule webserver in 192.168.221.3 (we have all needded rules allowing traffic from PFSENSE2 and PFSENSE3 to 192.168.221.3), we get the following errors:

Line:47
Char:37
Code:0
Error:Carácter ')' esperado
URL:http://192.168.221.3:2000/

Line:54
Char:26
Code:0
Error:Carácter '}' esperado
URL:http://192.168.221.3:2000/

The second problem is that it is not possible to use "direct connect" (DC++) behind PFSENSE2 and PFSENSE3, althoug it can connect it is not possible to transfer files because it complains that the IP used to connect is different from the IP used to download, i.e. to connect it provides the computer's IP and to download it uses the firewall's IP.

So I though in using PFSENSE2 and PFSENSE3 has transparent firewall, I've followed the tutorial available in the PFSENSE homepage, I've got it working has transparent firewall, I though. I cant get the IP leases from the DHCP server on PFSENSE1 interface OPT2 and OPT3, neither the dns servers to be delivered to the cllients behind the PFSENSE2 and PFSENSE3 although I've configured both to work has transparent firewall.

What I want is some guidelines, some tips or even some tricks in order to accomplish this requirements.

Thankyou

Dracunciliasis

pfsense_NET.GIF_thumb

sullrich

Sounds like the errors you are getting is due to non-ascii characters.

You may want to remove all non-ascii characters.

dracunciliasis

@sullrich:

Sounds like the errors you are getting is due to non-ascii characters.

You may want to remove all non-ascii characters.

Hello
The errors I get are from emule webserver port:2000 and from azureus webserver port:1000, they only occur on the clients behind PFSENSE2 and PFSENSE3 on clients behind PFSENSE1 all the webservers works fine (all PFSENSE'S are BETA4).

@dracunciliasis:

I cant get the IP leases from the DHCP server on PFSENSE1 interface OPT2 and OPT3, neither the dns servers to be delivered to the clients behind the PFSENSE2 and PFSENSE3 although I've configured both to work has transparent firewall.

Thankyou for your help, but, concerning the second problem your answer doesnt provide solutions to it.

dracunciliasis

sullrich

1.0-RC3 is now out, you really should update.