Applications quit working across network?



  • Just started using pfSense the last couple of days.  I have the lan on 192.168.0.x and a static route to 192.168.1.x.  Applications (Openfire IM Server, rdp sessions) that go to the 192.168.1.x network will go away and come back. A consistent ping to the .1 network never shows a failure.  Where do I look to start troubleshooting the problem?

    Thanks
    Marty



  • Does the 192.168.1.x network also have a route to the 192.168.0.x network?

    Do all these applications "go away and come back" at the same time?



  • Yes it does seem so.

    Marty



  • Which of the 2 questions was that vaguely attempting to answer?



  • Sorry, I didn't see the first question.  Yes the .1 network has a route back to the .0 network.  And the applications go away at the same time.

    Thanks
    Marty



  • I take it you're not pinging the interface of the pfSense host on the .1 network, but one of the hosts who's services go away?



  • Yes, I can start a continuous ping to the im server and the server I am remote desktop-ed into and it will not drop a packet.  But the im and rdp session will go away for a few seconds and then re-establish connection.

    Any Ideas?
    Marty



  • The only few things I can think of are:

    • You've got another 192.168.1.x LAN

    • You're not using /24 netmasks

    • You're running out of states

    What version (number) of pfSense are you running?



  • Marty,

    Post a couple screen shots of your static route page and your LAN firewall rules for a starting point.
    From what you explain the .0/LAN interface and the .1 static routed network are on two different physical switchs??They are not vlan setups through a  switch?  Do you have both of these subnets running off of one physical nic on the pfSense box? Which of the two subnets are the actual servers residing in?
    Sounds like you are getting 'one way communication' (randomly.?) If you enable logging on your lan firewall rules after lots of eye squinting you will probably being able to see what ports are not talking both directions. This would make sense why pings are A-OK.

    Barry


Locked