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

    Noia IP120

    Scheduled Pinned Locked Moved Hardware
    14 Posts 10 Posters 6.8k 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.
    • jahonixJ
      jahonix
      last edited by

      Well, recently I tried this with an otherwise unused IP120 on my own.

      Comparing the logs it shows that BSD 5.x/6.y panics when trying to detect the NICs.
      Makes sense since the MAC addresses are not reported properly with these devices.

      From booting pfSense:
      pcib0: <host to="" pci="" bridge="">pcibus 0 on motherboard
      pir0: <pci 3="" interrupt="" routing="" table:="" entries="">on motherboard
      pci0: <pci bus="">on pcib0

      Fatal trap 12: page fault while in kernel mode

      From booting m0n0wall (on the same machine):
      pcib0: <host to="" pci="" bridge="">on motherboard
      pci0: <pci bus="">on pcib0
      fxp0: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0x8000-0x803f mem 0x80100000
      -0x8011ffff,0x80000000-0x80000fff irq 11 at device 14.0 on pci0
      fxp0: Ethernet address 4d:4d:00:00:00:00
      inphy0: <i82555 10="" 100="" media="" interface="">on miibus0
      inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
      fxp1: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0x8400-0x843f mem 0x80300000
      -0x8031ffff,0x80200000-0x80200fff irq 10 at device 15.0 on pci0
      fxp1: Ethernet address 4d:4d:00:00:00:00

      If anyone could come up with an idea where to look for a fix that would be wonderful!
      I would even offer my box for testing (it has a soldered in CF-Card reader, no HD anymore!)

      This could give those devices a new and useful life again…

      jahonix</intel></i82555></intel></pci></host></pci></pci></host>

      1 Reply Last reply Reply Quote 0
      • G
        g9
        last edited by

        @jahonix:

        Well, recently I tried this with an otherwise unused IP120 on my own.

        Comparing the logs it shows that BSD 5.x/6.y panics when trying to detect the NICs.
        Makes sense since the MAC addresses are not reported properly with these devices.

        From booting pfSense:
        pcib0: <host to="" pci="" bridge="">pcibus 0 on motherboard
        pir0: <pci 3="" interrupt="" routing="" table:="" entries="">on motherboard
        pci0: <pci bus="">on pcib0

        Fatal trap 12: page fault while in kernel mode

        From booting m0n0wall (on the same machine):
        pcib0: <host to="" pci="" bridge="">on motherboard
        pci0: <pci bus="">on pcib0
        fxp0: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0x8000-0x803f mem 0x80100000
        -0x8011ffff,0x80000000-0x80000fff irq 11 at device 14.0 on pci0
        fxp0: Ethernet address 4d:4d:00:00:00:00
        inphy0: <i82555 10="" 100="" media="" interface="">on miibus0
        inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
        fxp1: <intel 10="" 100="" 82559er="" embedded="" ethernet="">port 0x8400-0x843f mem 0x80300000
        -0x8031ffff,0x80200000-0x80200fff irq 10 at device 15.0 on pci0
        fxp1: Ethernet address 4d:4d:00:00:00:00

        If anyone could come up with an idea where to look for a fix that would be wonderful!
        I would even offer my box for testing (it has a soldered in CF-Card reader, no HD anymore!)

        This could give those devices a new and useful life again…

        jahonix</intel></i82555></intel></pci></host></pci></pci></host>

        Yeah cut be nice, I have 6 of thus boxes !

        M0n0wall 1.22 works fine, but I will like to have pfsense on thous boxes  ;) ;D

        1 Reply Last reply Reply Quote 0
        • J
          jeroen234
          last edited by

          try disabeling fxp0 or fxp1 sins that 2 have the same mac

          and monowall is switching soon from freebsd 4.11 to 6.x

          1 Reply Last reply Reply Quote 0
          • jahonixJ
            jahonix
            last edited by

            Well, actually you cannot disable an interface on these boxes (to my knowledge at least).

            These are embedded devices with only 2 serial console ports. Have a look at it here:
            http://chrisbuechler.com/m0n0wall/nokia/ip110.html

            I was hoping that Chris B. would jump in here but he owns/owned an IP110 with 64MB Ram which is too small for pfSense now.
            And I haven't seen him around here for awhile.

            It is a known issue that these damned devices do not show the correct MACs.
            When mine was booting IPSO I could at least see (and write down) the original MACs from the console menu at boot. But since it was a "used" install noone could give me the passwords and the HD was old and loud as hell anyway. I tore it out and soldered a CF reader on the given tabs which is working fine. At least with m0n0wall in its current FreeBSD flavour - I haven't tested the FreeBSD 6 beta of m0n0wall. This could be interesting to see if the problem is in FreeBSD 6 or its implementation in pfSense…

            1 Reply Last reply Reply Quote 0
            • R
              rsw686
              last edited by

              I have an IP330. It would show FF:FF:FF:FF:FF:FF for the mac address. This does not affect the boot whatsoever. Once booted pfSense will assign it a mac address so you can view the webgui. Then you can download the config and change it to whatever you would like.

              1 Reply Last reply Reply Quote 0
              • D
                deanlester
                last edited by

                Anyone have any update or progress on these Nokia's?

                I have an IP120, and am getting the same kernel panic as observed by others.

                The previous post by rsw686, with an IP330 (different box, but may be using the same NICs and drivers) seems to indicate he can change the IP spoofing by config file.

                Does anyone know if the config file is loaded as part of the kernel, which would allow the MAC spoofing to work; or if the config file changes are only made after the kernel and kernel drivers are loaded? If the latter, we'd need someone knowledgeable in hacking the BSD kernel drivers to ignore the duplicate MACs.

                I can confirm that my IP120 does run m0n0wall 1.231, but pfSense panics. I have loaded pfSense on both an internal 2.5" hard drive, as well as my CF adapter. Have yet to try the m0n0wall 1.3b.

                I'm willing to spend time on this, if anyone is able to help. I am new to BSD, but have spent some relatively low level time on other *NIX.

                Thanks,
                dean

                1 Reply Last reply Reply Quote 0
                • C
                  cmb
                  last edited by

                  Kernel panics are FreeBSD problems. We aren't FreeBSD developers. If you want to get the issue fixed, load a stock FreeBSD on one, and see the FreeBSD handbook on kernel debugging and send the appropriate info to the appropriate FreeBSD list.

                  1 Reply Last reply Reply Quote 0
                  • S
                    sullrich
                    last edited by

                    Or try to install the pfSense developers iso and make it panic.  Then send the backtrace accordingly to the handbook.  pfSense developers ISO has GDB and such built in.

                    1 Reply Last reply Reply Quote 0
                    • C
                      cmb
                      last edited by

                      Or if someone wants a m0n0wall 1.3 beta img with debugging tools, let me know. it'll panic the same way.

                      I have a IP110 that I'll eventually get around to doing this on, but it'll probably be a while as my IP110 has been collecting dust for quite some time.

                      1 Reply Last reply Reply Quote 0
                      • D
                        deanlester
                        last edited by

                        Thanks guys for the suggestions. Will see if I can get the developers load or a standard BSD loaded.

                        Chris, what's the best way to get ahold of that 1.3 beta image with debugger tools? I'll pm you with my email addy.

                        thanks,
                        dean

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