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

    Msn massenger not working when using the dsl router in bridge mode

    General pfSense Questions
    3
    5
    3.1k
    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.
    • H
      hadi57
      last edited by

      hi

      i was using dsl router in pppoe mode, all application were runnig good, then i changed my dsl router to bridge mode, so i can access my pfsense box from wan, i ended up with msn massenger not working on my client's pc's, it is happening on 6 pfsense boxes.

      help really appreciated

      1 Reply Last reply Reply Quote 0
      • Cry HavokC
        Cry Havok
        last edited by

        Only MSN?  What version of pfSense are you running?

        1 Reply Last reply Reply Quote 0
        • H
          hadi57
          last edited by

          hi and thanks for the reply

          i am using 1.2-beta-2

          yes only msn is the complaint from my clients on 3 different pfsense boxes with speed touch dsl router in bridge mode

          i checked the diagnosting: system logs: firwall, i found the followings:
          act: x, time: Jul 31:23:36:41, if: wan, Source: (tos 0x0, ttl 1, id 38426, offset 0, falgs [DF], proto: IGMP (2), lengh: 28) 192.168.5.1

          and this message apear every time a client try to access msn massenger, with error

          1 Reply Last reply Reply Quote 0
          • K
            KiaN
            last edited by

            Same probleme here :(

            pfSense must be the issue, I tried with two modems (a Netopia and a Linksys)

            When I change the modems to routeur mode and use pfSense in the middle with DHCP, MSN works fine.

            But it does not work while pfSense is the one connecting using PPPoE

            1 Reply Last reply Reply Quote 0
            • K
              KiaN
              last edited by

              WEIRD  ??? ???

              Changing the MTU to 1400 solved the problem.

              See there : http://m0n0.ch/wall/list-dev/showmsg.php?id=17/46

              Now I must find a more standard way to solve this problem.

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