Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Loadbalancer

    Scheduled Pinned Locked Moved Routing and Multi WAN
    25 Posts 5 Posters 7.2k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Z
      zetar
      last edited by

      Thanks, I removed the previous post, if I understand it was not necessary to enter.
      I can not understand how to make the registration of firewall log.
      Would you give me a hint on how to do things I have not yet understood well
      Thanks.

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Ok.
        Go to Firewall>>Rules>>Lan edit your rule for webmail access from your IP. (click the 'e')
        You need to enable logging on that rule.

        Now 'save' and 'apply settings'. You rules should look something like this:

        Note: The blue 'i' shows that logging is enabled. Your IP address will be different.

        Now everything that uses that rule will be logged in the firewall log: status>>system logs>>firewall.

        So log into your webmail and then check the log to see what connections were made.

        Disable logging again afterwards.

        Steve

        1 Reply Last reply Reply Quote 0
        • Z
          zetar
          last edited by

          Thanks for the advice.
          This is the place to be when I put user name and password and open the folder "inbox".

          May 25 19:11:02 LAN 172.25.14.6:53793 212.48.8.171:443 TCP:S
          pass
          May 25 19:11:02 LAN 172.25.14.6:53794 212.48.8.171:80 TCP:S
          pass
          May 25 19:11:02 LAN 172.25.14.6:53795 212.48.8.171:80 TCP:S
          pass
          May 25 19:11:02 LAN 172.25.14.6:53796 62.211.72.133:80 TCP:S
          pass
          May 25 19:11:03 LAN 172.25.14.6:53797 62.211.72.133:80 TCP:S
          pass
          May 25 19:11:05 LAN 172.25.14.6:53798 212.239.41.101:80 TCP:S
          pass
          May 25 19:11:05 LAN 172.25.14.6:53799 66.235.156.132:80 TCP:S
          pass
          May 25 19:11:05 LAN 172.25.14.6:53800 62.211.72.133:80 TCP:S
          pass
          May 25 19:11:05 LAN 172.25.14.6:53801 62.211.72.133:80 TCP:S
          pass
          May 25 19:11:05 LAN 172.25.14.6:53802 62.211.72.133:80 TCP:S
          pass
          May 25 19:11:05 LAN 172.25.14.6:53803 212.48.11.161:80 TCP:S
          pass
          May 25 19:11:05 LAN 172.25.14.6:53804 212.48.11.161:80 TCP:S
          pass
          May 25 19:11:06 LAN 172.25.14.6:53805 62.211.72.133:80 TCP:S
          pass
          May 25 19:11:06 LAN 172.25.14.6:53806 212.48.1.154:80 TCP:S
          pass
          May 25 19:11:06 LAN 172.25.14.6:53807 212.48.1.154:80 TCP:S
          pass
          May 25 19:11:06 LAN 172.25.14.6:53808 80.252.91.41:80 TCP:S
          pass
          May 25 19:11:06 LAN 172.25.14.6:53809 80.252.91.41:80 TCP:S
          pass
          May 25 19:11:06 LAN 172.25.14.6:53810 212.48.1.156:80 TCP:S
          pass
          May 25 19:11:21 LAN 172.25.14.6:53816 195.128.234.84:80 TCP:S
          pass
          May 25 19:12:01 LAN 172.25.14.6:53835 209.85.229.100:80 TCP:S
          pass
          May 25 19:12:21 LAN 172.25.14.6:53842 195.128.234.84:80 TCP:S
          pass
          May 25 19:12:40 LAN 172.25.14.6:53856 62.211.72.133:80 TCP:S
          pass
          May 25 19:13:11 LAN 172.25.14.6:53862 62.211.72.133:80 TCP:S
          pass
          May 25 19:13:21 LAN 172.25.14.6:53867 195.128.234.84:80 TCP:S
          pass
          May 25 19:13:42 LAN 172.25.14.6:53885 62.211.72.133:80 TCP:S
          pass
          May 25 19:14:13 LAN 172.25.14.6:53895 62.211.72.133:80 TCP:S
          pass
          May 25 19:14:21 LAN 172.25.14.6:53897 195.128.234.84:80 TCP:S
          pass
          May 25 19:14:44 LAN 172.25.14.6:53912 62.211.72.133:80 TCP:S
          pass
          May 25 19:15:05 LAN 172.25.14.6:53916 62.211.72.133:80 TCP:S
          pass
          May 25 19:15:06 LAN 172.25.14.6:53917 62.211.72.133:80 TCP:S
          pass
          May 25 19:15:08 LAN 172.25.14.6:53918 62.211.72.133:80 TCP:S
          pass
          May 25 19:15:08 LAN 172.25.14.6:53920 212.239.41.101:80 TCP:S
          pass
          May 25 19:15:09 LAN 172.25.14.6:53921 66.235.156.132:80 TCP:S
          pass
          May 25 19:15:09 LAN 172.25.14.6:53922 212.48.1.154:80 TCP:S
          pass
          May 25 19:15:09 LAN 172.25.14.6:53923 212.48.1.154:80 TCP:S
          pass
          May 25 19:15:09 LAN 172.25.14.6:53924 80.252.91.41:80 TCP:S
          pass
          May 25 19:15:09 LAN 172.25.14.6:53925 80.252.91.41:80 TCP:S
          pass
          May 25 19:15:10 LAN 172.25.14.6:53926 212.48.1.156:80 TCP:S
          pass
          May 25 19:15:21 LAN 172.25.14.6:53931 195.128.234.84:80 TCP:S

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Hmm, OK.
            So it looks like:
            212.48.8.171
            62.211.72.133
            At least are involved. But also 212.48.10.165 is mail.virgilio.it. so maybe we should include 212.48.0.0/16.

            So change your lan rules to:

            Try that.

            Steve

            1 Reply Last reply Reply Quote 0
            • Z
              zetar
              last edited by

              You're a really great, now works without problems.
              I replaced the single IP subnet with all the LAN and I think that works by any location.
              Thanks, but thank you very much for your cooperation.
              Known, but those of Virgil can not do like the others …
              hei hei ..

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.