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

    OLSR mesh GUI $400 {awarded}

    Completed Bounties
    7
    95
    74.8k
    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.
    • P
      pcatiprodotnet
      last edited by

      17.  Setting the DHCP Netmask caused DHCP not to start.  After selecting a Netmask and clicking [Save], the next page showed two Netmask fields:

      On the GUI…

      Subnet  10.128.0.0
      Subnet mask 255.248.0.0
      Available range 10.128.0.0 - 10.135.255.255
      Subnet Mask [24]
      Range  [10.130.1.10]  to  [10.130.1.254]

      From the logs…

      May 17 06:16:13 dhcpd: /var/dhcpd/etc/dhcpd.conf line 9: too few numbers.
      May 17 06:16:13 dhcpd: /var/dhcpd/etc/dhcpd.conf line 9: too few numbers.
      May 17 06:16:13 dhcpd: subnet 10.128.0.0 netmask 24 {
      May 17 06:16:13 dhcpd: subnet 10.128.0.0 netmask 24 {
      May 17 06:16:13 dhcpd: ^
      May 17 06:16:13 dhcpd: ^
      May 17 06:16:13 dhcpd: Configuration file errors encountered -- exiting
      May 17 06:16:13 dhcpd: Configuration file errors encountered -- exiting

      16.  I tried setting "Announce Dynamic Local Route" to both "10.130.1.0 255.255.255.0" and "10.130.1.0/255.255.255.0", but OLSR failed to start with either setting.  I tried looking in /var/etc/olsr.conf but I didn't see the values anywhere.

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

        @pcatiprodotnet:

        17.  Setting the DHCP Netmask caused DHCP not to start.  After selecting a Netmask and clicking [Save], the next page showed two Netmask fields:

        On the GUI…

        Subnet  10.128.0.0
        Subnet mask 255.248.0.0
        Available range 10.128.0.0 - 10.135.255.255
        Subnet Mask [24]
        Range  [10.130.1.10]  to  [10.130.1.254]

        From the logs…

        May 17 06:16:13 dhcpd: /var/dhcpd/etc/dhcpd.conf line 9: too few numbers.
        May 17 06:16:13 dhcpd: /var/dhcpd/etc/dhcpd.conf line 9: too few numbers.
        May 17 06:16:13 dhcpd: subnet 10.128.0.0 netmask 24 {
        May 17 06:16:13 dhcpd: subnet 10.128.0.0 netmask 24 {
        May 17 06:16:13 dhcpd: ^
        May 17 06:16:13 dhcpd: ^
        May 17 06:16:13 dhcpd: Configuration file errors encountered -- exiting
        May 17 06:16:13 dhcpd: Configuration file errors encountered -- exiting

        Ok, that should be fixed.

        @pcatiprodotnet:

        16.  I tried setting "Announce Dynamic Local Route" to both "10.130.1.0 255.255.255.0" and "10.130.1.0/255.255.255.0", but OLSR failed to start with either setting.  I tried looking in /var/etc/olsr.conf but I didn't see the values anywhere.

        Are you sure?  It should be in there if it suddenly doesn't start.

        1 Reply Last reply Reply Quote 0
        • P
          pcatiprodotnet
          last edited by

          Very sure.  I've tried it and looked in /var/etc/olsr.conf more than five times now just to be sure.  I tried these combinations "10.130.1.0/255.255.255.0", "10.130.1.0 255.255.255.0", "10.130.1.0 / 255.255.255.0", "10.130.1.0/24" many times each with no start.  One odd thing, I tried setting it to just "10.130.1.0" and also "10.130.1.0 / 24" and the service started, however there is still no sign of "10.130.1.0" in /var/etc/olsr.conf … perhaps this file isn't getting updated?  As a side note, I did notice that the "Announce [self as] Dynamic Gateway" (from issue#10) is properly adding and removing the "0.0.0.0 0.0.0.0" entry from olsr.conf. (other than sometimes leaving Hna4 {} empty, see post below)

          1 Reply Last reply Reply Quote 0
          • P
            pcatiprodotnet
            last edited by

            olsr doesn't start when "Announce self as Dynamic Gateway" is Unchecked; perhaps it doesn't like the empty Hna4 { } section as below, so I guess this Hna4{ } section should be absent from the config (or auto-commented out) when ( "Announce [self as] Dynamic Gateway" unchecked AND "Announce Dynamic Local Route" is empty ):
            Hna4
            {

            }

            It may be more consistant with other forms to change this entry field to two fields with drop-down on the second like:
            "Announce Dynamic Local Route IP: [10.130.1.0] / [24]"
            Thank you,
            -Pete

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

              @pcatiprodotnet:

              olsr doesn't start when "Announce self as Dynamic Gateway" is Unchecked; perhaps it doesn't like the empty Hna4 { } section as below, so I guess this Hna4{ } section should be absent from the config (or auto-commented out) when ( "Announce [self as] Dynamic Gateway" unchecked AND "Announce Dynamic Local Route" is empty ):
              Hna4
              {

              }

              Done.

              @pcatiprodotnet:

              It may be more consistant with other forms to change this entry field to two fields with drop-down on the second like:
              "Announce Dynamic Local Route IP: [10.130.1.0] / [24]"
              Thank you,
              -Pete

              Hrm.  I'll look into it.

              1 Reply Last reply Reply Quote 0
              • P
                pcatiprodotnet
                last edited by

                17.  DHCP is Not functioning when I choose smaller subnet mask in the drop-down box; Right now, it only works when I chose a large enough subnet to encompass both the interface subnet AND my chosen dhcp range:

                My Interface IP address & netmask:  10.130.1.1 / 13

                DHCP GUI:

                Subnet  10.128.0.0
                Subnet mask 255.248.0.0
                Available range 10.128.0.0 - 10.135.255.255
                Subnet Mask [24]  <–  I entered this.
                Range [10.130.1.10]  to  [10.130.1.254]  <–  I entered these.

                I tried to change the subnet mask drop down box to "24" but it failed to serve dhcp and I got the following error lines in the system log {below}.  10.130.1/24 is within the "Available Range" of 10.128/13 (10.128.0.0 - 10.135.255.255), but the logs indicate that DHCP server's validation routine thinks it's available address range to serve should be limited to 10.128/24 when the Netmask is set to [24] … It appears that the DHCP server's validation checking is incorrectly applying the custom Netmask (/24) to the "Available Range" (10.128) instead of correctly validating against either the entered "Range" (10.130) OR interface IP/netmask.

                System Logs...

                May 18 06:44:15 dhcpd: Address range 10.130.1.10 to 10.130.1.254 not on net 10.128.0.0/255.255.255.0!
                May 18 06:44:15 dhcpd: Address range 10.130.1.10 to 10.130.1.254 not on net 10.128.0.0/255.255.255.0!

                Since I want to set up each olsr node to serve different class-c (/24) range within the common interface range of 10.128/13, I can't be limited to only the first class-c 10.128.0.0/255.255.255.0 within the 10.128/13 range.  I've never configured a DHCP server so I'm unsure what setting changes to suggest; perhaps "Subnet" field could be made changable from the default of "10.128.0.0" to either the first "Range" value "10.130.1.10" OR the interface IP/netmask OR allow me to manually enter it?  If you run out of ideas, I wonder if there is there a way to simply tell the dhcp server Not to do it's Netmask validation checking, and just push my desired settings out "as is" to the dhcp client.

                update:  In another forum discussion, it was determined that it may not be possible to change the first two dhcp values "Subnet: 10.128.0.0" & "Subnet mask: 255.248.0.0" (which are also the actual interface subnet & subnet mask) in dhcp.conf, not even to subset values such as: "10.130.1.0/255.255.255.0".  If you verify this as true, perhaps I could get around this problem by turning on pfSense DHCP Forwarding and serving the DHCP from another more flexible system; and also if true, could you verify that pfSense gui permits me to enable dhcp forwarding to the WAN interface?  Thanks, -Pete

                1 Reply Last reply Reply Quote 0
                • P
                  pcatiprodotnet
                  last edited by

                  10.  When I enable "Announce self as Dynamic Gateway" it adds the "0.0.0.0  0.0.0.0" to the olsr.conf file but it fails to put Hna4 and braces around it as below:
                  Hna4
                  {
                  0.0.0.0  0.0.0.0
                  }

                  Basically, here's how the olsr.conf Hna4{} entrys should look based on all possible combinations of settings:

                  IF ("Announce self as Dynamic Gateway"=TRUE)  AND  ("Announce Dynamic local route"=EMPTY)
                  THEN the following Hna4{} entry in olsr.conf should look like this :
                  Hna4
                  {
                  0.0.0.0  0.0.0.0
                  }

                  IF ("Announce self as Dynamic Gateway"=TRUE)  AND  ("Announce Dynamic local route"=NOT-EMPTY: user enters "10.130.1.0 255.255.255.0")
                  THEN the following Hna4{} entry in olsr.conf should look like this :
                  Hna4
                  {
                  0.0.0.0  0.0.0.0
                  10.130.1.0 255.255.255.0
                  }

                  IF ("Announce self as Dynamic Gateway"=FALSE)  AND  ("Announce Dynamic local route"=NOT-EMPTY: user enters "10.130.1.0 255.255.255.0")
                  THEN the following Hna4{} entry in olsr.conf should look like this :
                  Hna4
                  {
                  10.130.1.0 255.255.255.0
                  }

                  IF ("Announce self as Dynamic Gateway"=FALSE)  AND  ("Announce Dynamic local route"=EMPTY)
                  THEN remove or comment out all mention of Hna4 { … } and anything existing between the braces in olsrd.conf :
                  #Hna4
                  #{

                  #}

                  As for not leaving an empty Hna4{} entry in the file, I'm only guessing it was causing olsr not to start; so it could have been some other undiscovered change made by the gui that actually caused the start failure.

                  1 Reply Last reply Reply Quote 0
                  • P
                    pcatiprodotnet
                    last edited by

                    It may be more consistant with other forms to change this entry field to two fields with drop-down on the second like:
                    "Announce Dynamic Local Route IP: [10.130.1.0] / [24]"
                    [then translate the /24 into #.#.#.# before inserting into the config]

                    " Hrm.  I'll look into it. "

                    Thank you for considering it, althought I know what to enter in that field, i'm sure this would be somewhat less confusing for first time users.
                    -Pete

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

                      Ill get this stuff fixed up later today or this weekend.

                      1 Reply Last reply Reply Quote 0
                      • P
                        pcatiprodotnet
                        last edited by

                        " Ill get this stuff fixed up later today or this weekend. "

                        Thank you.  I'll check back for updates periodically then download and test. Thanks, -Pete

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

                          Sorry I havent created an image for this yet.  We've been working on some stuff all weekend.  I'll get you one as soon as possible, most likely in the next 5 hours.

                          1 Reply Last reply Reply Quote 0
                          • P
                            pcatiprodotnet
                            last edited by

                            " I'll get you one as soon as possible, most likely in the next 5 hours. "
                            Thanks Scott. Please email me when you're done.

                            1 Reply Last reply Reply Quote 0
                            • P
                              pcatiprodotnet
                              last edited by

                              It seems that the DHCP server on WAN isn't functioning, even with the correct interface ip/subnet/mask setting.  However, when I have LAN set up to do wireless the DHCP functions.  I'm using pfsense-pc; I am fairly certain that dhcp on Wan was functioning in beta4, although I don't think you had the code in yet allowing me to (attempt to) modify the subnet.

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

                                @pcatiprodotnet:

                                It seems that the DHCP server on WAN isn't functioning, even with the correct interface ip/subnet/mask setting.  However, when I have LAN set up to do wireless the DHCP functions.  I'm using pfsense-pc; I am fairly certain that dhcp on Wan was functioning in beta4, although I don't think you had the code in yet allowing me to (attempt to) modify the subnet.

                                Try running from a shell:

                                /usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /var/dhcpd/etc/dhcpd.conf $WANINTERFACE

                                1 Reply Last reply Reply Quote 0
                                • P
                                  pcatiprodotnet
                                  last edited by

                                  Thanks, I'll give that a try tomorrow at work.

                                  We just finished installing a fair number of pfsense olsr nodes today; they're functioning quite well, DHCP & HNA4 aside.  I had no trouble on the laptop when I either hardcoded ip/gateway/netmask(custom narrow) of nearest olsr node OR run olsr for windows thus making the laptop another node on the mesh.

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

                                    @pcatiprodotnet:

                                    Thanks, I'll give that a try tomorrow at work.

                                    We just finished installing a fair number of pfsense olsr nodes today; they're functioning quite well, DHCP & HNA4 aside.  I had no trouble on the laptop when I either hardcoded ip/gateway/netmask(custom narrow) of nearest olsr node OR run olsr for windows thus making the laptop another node on the mesh.

                                    Awesome!!!

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

                                      Image updated.  Please let me know how it works.

                                      1 Reply Last reply Reply Quote 0
                                      • P
                                        pcatiprodotnet
                                        last edited by

                                        I'll try this today at work.  I noticed that the pfsense-pc.img.gz file now contains a pfsense.ISO whereas it used to contain pfsense.IMG; will that work ok on imbedded CF?
                                        Thanks you, -Pete

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

                                          @pcatiprodotnet:

                                          I'll try this today at work.  I noticed that the pfsense-pc.img.gz file now contains a pfsense.ISO whereas it used to contain pfsense.IMG; will that work ok on imbedded CF?
                                          Thanks you, -Pete

                                          Not sure but I just rebuilt and copied the image back up.

                                          1 Reply Last reply Reply Quote 0
                                          • P
                                            pcatiprodotnet
                                            last edited by

                                            6. This issue has crept back in.

                                            6. I have noticed that every other I click [Save] on the OLSR configuration page it fails to start OLSR, such as:  [save] starts, [save] not-started, [save] starts, [save] not-started, etc…
                                                I would check the logs and there would be No listing for "olsrd[4494]: olsr.org - 0.4.10 successfully started".

                                            Also, one time I tried UnChecking OLSR and Saving but it wouldn't shut down.

                                            10.  I set "Announce Dynamic local route" to "10.130.1.0/255.255.255.0" and "Announce self as Dynamic Gateway"=UnChecked.  However, it didn't work.  It added an empty "Hna4{}" entry to the olsrd.conf file, but the values I entered were Not in oslrd.conf.
                                            It should have added:

                                            IF ("Announce self as Dynamic Gateway"=FALSE)  AND  ("Announce Dynamic local route"=NOT-EMPTY: user enters "10.130.1.0 255.255.255.0")
                                            THEN the following Hna4{} entry in olsr.conf should look like this :
                                            Hna4
                                            {
                                            10.130.1.0 255.255.255.0
                                            }

                                            I did not get a chance to check the other three possibilities yet in the following Hna4{} config logic:

                                            Basically, here's how the olsr.conf Hna4{} entrys should look based on all possible combinations of settings:

                                            IF ("Announce self as Dynamic Gateway"=TRUE)  AND  ("Announce Dynamic local route"=EMPTY)
                                            THEN the following Hna4{} entry in olsr.conf should look like this :
                                            Hna4
                                            {
                                            0.0.0.0  0.0.0.0
                                            }

                                            IF ("Announce self as Dynamic Gateway"=TRUE)  AND  ("Announce Dynamic local route"=NOT-EMPTY: user enters "10.130.1.0 255.255.255.0")
                                            THEN the following Hna4{} entry in olsr.conf should look like this :
                                            Hna4
                                            {
                                            0.0.0.0  0.0.0.0
                                            10.130.1.0 255.255.255.0
                                            }

                                            IF ("Announce self as Dynamic Gateway"=FALSE)  AND  ("Announce Dynamic local route"=NOT-EMPTY: user enters "10.130.1.0 255.255.255.0")
                                            THEN the following Hna4{} entry in olsr.conf should look like this :
                                            Hna4
                                            {
                                            10.130.1.0 255.255.255.0
                                            }

                                            IF ("Announce self as Dynamic Gateway"=FALSE)  AND  ("Announce Dynamic local route"=EMPTY)
                                            THEN remove or comment anything existing between the braces in olsrd.conf (not sure if empty Hna4 is legal syntax) :
                                            Hna4
                                            {

                                            }

                                            17.  I was unable to get DHCP to work on the Wan wireless interface.

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