Teamspeak server
-
I have a teamspeak server behind my pfsense and I can't get it to work. The server has a static ip of 192.168.11.10. I have DSL with the PPPoE on the modem and the modem passes the external ip to pfsense. The modem's internal ip is 192.168.0.1. I set up a rule in nat like this..
WAN
interface adress
udp
8767
8767
192.168.11.10
8767
description
Teamspeak serverI had it auto setup a firewall rule too. I have tried everything I can think of and can't get it to work. Would it be better if I put the modem in bridge mode and PPPoE on pfsense? Any help appreciated.
-
Bridging the modem is absolutely recommended unless you want to setup everything twice (at the modem and additionally at the pfSense). Also some services like DynDNS require that the pfSense sees it's own public IP at WAN.
-
I have dyndns working ok and pfsense does see the public ip, the modem passes it. There is no configuration I can do to modem except put it in bridge mode. I do not have it in bridge mode because I was needing to see the modem logs because my DSL kept dropping. I was running a different firewall and had no trouble with my server. I really want to get pfsense working !
-
Heh, I got it working! Updated to the latest snapshot and rebooted and it works!
-
Most likely you're problem was the firewall rule reload bug, where firewall rules were not being reloaded properly until after a reboot.
-
@sdale:
Most likely you're problem was the firewall rule reload bug, where firewall rules were not being reloaded properly until after a reboot.
Do I have to reboot everytime I make a rule?
-
@sdale:
Most likely you're problem was the firewall rule reload bug, where firewall rules were not being reloaded properly until after a reboot.
Do I have to reboot everytime I make a rule?
Hell (oops), no.
I have a separate NIC named DMZ on 192.168.3.1/24 (192.168.1.0/24 our LAN & 192.168.2.0/24 our Wifi Portal).
A server with 3 TS servers is running on 192.168.3.2 (W2K version).
I openend the telnet, Web and 3 voice channels to it - works very well.
For saying : the uptime is 121 days….Be carefull - you bether have a big 'up' on on WAN - TS can really spit out a lot of bytes when you have many clienst attached.
-
@sdale:
Most likely you're problem was the firewall rule reload bug, where firewall rules were not being reloaded properly until after a reboot.
Do I have to reboot everytime I make a rule?
No, this was a bug only present in a special version but it has long been fixed. In fact you only have to reboot when restoring a complete config.xml. All other changes are applied on the fly.
