How to make a dhcp server using busybox udhcpd for multiple ports











up vote
0
down vote

favorite












I have a Beaglebone Black that needs to be configured as a DHCP SERVER:



I want BOTH [eth0 and usb0] to act as a DHCP SERVER once clients connect to them via a standard cable, crossover (no router/hub) and usb.



Ex: 3 Beaglebones. Beaglebone#1 is the DHCP SERVER, Beaglebone#2 & #3 are the clients - 1 of them will connect to #1 using USB0 & the other ETH0, both are waiting for an IP to be issued to them.



Is this possible?
eth0 = 169.254.y.z; no dmesg-log errors; 0.0.0.0udp-68 but no udp-67 & no dhcp service loaded.



System Setup:
Linux Debian Jessie 4.4(ti-variant)










share|improve this question
























  • What challenges are you having setting up the DHCP server that way? Is the DHCP server running? Are there any errors in the log? Is anything listening on port 67, and on appropriate addresses?
    – Eric Renouf
    Jun 7 '16 at 13:47










  • eth0 = 169.254.y.z; no dmesg-log errors; 0.0.0.0udp-68 but no udp-67 & no dhcp loaded!
    – Beagleboy
    Jun 7 '16 at 14:10










  • Instead of using comments, could you please edit your question to include the extra information?
    – Eric Renouf
    Jun 7 '16 at 14:17















up vote
0
down vote

favorite












I have a Beaglebone Black that needs to be configured as a DHCP SERVER:



I want BOTH [eth0 and usb0] to act as a DHCP SERVER once clients connect to them via a standard cable, crossover (no router/hub) and usb.



Ex: 3 Beaglebones. Beaglebone#1 is the DHCP SERVER, Beaglebone#2 & #3 are the clients - 1 of them will connect to #1 using USB0 & the other ETH0, both are waiting for an IP to be issued to them.



Is this possible?
eth0 = 169.254.y.z; no dmesg-log errors; 0.0.0.0udp-68 but no udp-67 & no dhcp service loaded.



System Setup:
Linux Debian Jessie 4.4(ti-variant)










share|improve this question
























  • What challenges are you having setting up the DHCP server that way? Is the DHCP server running? Are there any errors in the log? Is anything listening on port 67, and on appropriate addresses?
    – Eric Renouf
    Jun 7 '16 at 13:47










  • eth0 = 169.254.y.z; no dmesg-log errors; 0.0.0.0udp-68 but no udp-67 & no dhcp loaded!
    – Beagleboy
    Jun 7 '16 at 14:10










  • Instead of using comments, could you please edit your question to include the extra information?
    – Eric Renouf
    Jun 7 '16 at 14:17













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I have a Beaglebone Black that needs to be configured as a DHCP SERVER:



I want BOTH [eth0 and usb0] to act as a DHCP SERVER once clients connect to them via a standard cable, crossover (no router/hub) and usb.



Ex: 3 Beaglebones. Beaglebone#1 is the DHCP SERVER, Beaglebone#2 & #3 are the clients - 1 of them will connect to #1 using USB0 & the other ETH0, both are waiting for an IP to be issued to them.



Is this possible?
eth0 = 169.254.y.z; no dmesg-log errors; 0.0.0.0udp-68 but no udp-67 & no dhcp service loaded.



System Setup:
Linux Debian Jessie 4.4(ti-variant)










share|improve this question















I have a Beaglebone Black that needs to be configured as a DHCP SERVER:



I want BOTH [eth0 and usb0] to act as a DHCP SERVER once clients connect to them via a standard cable, crossover (no router/hub) and usb.



Ex: 3 Beaglebones. Beaglebone#1 is the DHCP SERVER, Beaglebone#2 & #3 are the clients - 1 of them will connect to #1 using USB0 & the other ETH0, both are waiting for an IP to be issued to them.



Is this possible?
eth0 = 169.254.y.z; no dmesg-log errors; 0.0.0.0udp-68 but no udp-67 & no dhcp service loaded.



System Setup:
Linux Debian Jessie 4.4(ti-variant)







debian






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 7 '16 at 14:50

























asked Jun 7 '16 at 13:36









Beagleboy

12




12












  • What challenges are you having setting up the DHCP server that way? Is the DHCP server running? Are there any errors in the log? Is anything listening on port 67, and on appropriate addresses?
    – Eric Renouf
    Jun 7 '16 at 13:47










  • eth0 = 169.254.y.z; no dmesg-log errors; 0.0.0.0udp-68 but no udp-67 & no dhcp loaded!
    – Beagleboy
    Jun 7 '16 at 14:10










  • Instead of using comments, could you please edit your question to include the extra information?
    – Eric Renouf
    Jun 7 '16 at 14:17


















  • What challenges are you having setting up the DHCP server that way? Is the DHCP server running? Are there any errors in the log? Is anything listening on port 67, and on appropriate addresses?
    – Eric Renouf
    Jun 7 '16 at 13:47










  • eth0 = 169.254.y.z; no dmesg-log errors; 0.0.0.0udp-68 but no udp-67 & no dhcp loaded!
    – Beagleboy
    Jun 7 '16 at 14:10










  • Instead of using comments, could you please edit your question to include the extra information?
    – Eric Renouf
    Jun 7 '16 at 14:17
















What challenges are you having setting up the DHCP server that way? Is the DHCP server running? Are there any errors in the log? Is anything listening on port 67, and on appropriate addresses?
– Eric Renouf
Jun 7 '16 at 13:47




What challenges are you having setting up the DHCP server that way? Is the DHCP server running? Are there any errors in the log? Is anything listening on port 67, and on appropriate addresses?
– Eric Renouf
Jun 7 '16 at 13:47












eth0 = 169.254.y.z; no dmesg-log errors; 0.0.0.0udp-68 but no udp-67 & no dhcp loaded!
– Beagleboy
Jun 7 '16 at 14:10




eth0 = 169.254.y.z; no dmesg-log errors; 0.0.0.0udp-68 but no udp-67 & no dhcp loaded!
– Beagleboy
Jun 7 '16 at 14:10












Instead of using comments, could you please edit your question to include the extra information?
– Eric Renouf
Jun 7 '16 at 14:17




Instead of using comments, could you please edit your question to include the extra information?
– Eric Renouf
Jun 7 '16 at 14:17










1 Answer
1






active

oldest

votes

















up vote
0
down vote













finally I got my answer: The service wasn't running because the interfaces were down.
1st. to fix interface:



ifconfig eth0 up

ifconfig usb0 up


2nd. uninstall ANY other DHCPDaemons except uDHCPD to free up udp port 67. Use:



netstat -tulnp |grep :67


if nothing comes up, its uDHCPD is not running; you'll have to start it:



http://xmodulo.com/raspberry-pi-wifi-access-point.html



if you want to bridge them together after you're done:



https://wiki.archlinux.org/index.php/Network_bridge



the BEST I can do for those hurting as I was. ~ Eric Renouf and Beagleboy
(thanks Eric)






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "106"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f288167%2fhow-to-make-a-dhcp-server-using-busybox-udhcpd-for-multiple-ports%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote













    finally I got my answer: The service wasn't running because the interfaces were down.
    1st. to fix interface:



    ifconfig eth0 up

    ifconfig usb0 up


    2nd. uninstall ANY other DHCPDaemons except uDHCPD to free up udp port 67. Use:



    netstat -tulnp |grep :67


    if nothing comes up, its uDHCPD is not running; you'll have to start it:



    http://xmodulo.com/raspberry-pi-wifi-access-point.html



    if you want to bridge them together after you're done:



    https://wiki.archlinux.org/index.php/Network_bridge



    the BEST I can do for those hurting as I was. ~ Eric Renouf and Beagleboy
    (thanks Eric)






    share|improve this answer

























      up vote
      0
      down vote













      finally I got my answer: The service wasn't running because the interfaces were down.
      1st. to fix interface:



      ifconfig eth0 up

      ifconfig usb0 up


      2nd. uninstall ANY other DHCPDaemons except uDHCPD to free up udp port 67. Use:



      netstat -tulnp |grep :67


      if nothing comes up, its uDHCPD is not running; you'll have to start it:



      http://xmodulo.com/raspberry-pi-wifi-access-point.html



      if you want to bridge them together after you're done:



      https://wiki.archlinux.org/index.php/Network_bridge



      the BEST I can do for those hurting as I was. ~ Eric Renouf and Beagleboy
      (thanks Eric)






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        finally I got my answer: The service wasn't running because the interfaces were down.
        1st. to fix interface:



        ifconfig eth0 up

        ifconfig usb0 up


        2nd. uninstall ANY other DHCPDaemons except uDHCPD to free up udp port 67. Use:



        netstat -tulnp |grep :67


        if nothing comes up, its uDHCPD is not running; you'll have to start it:



        http://xmodulo.com/raspberry-pi-wifi-access-point.html



        if you want to bridge them together after you're done:



        https://wiki.archlinux.org/index.php/Network_bridge



        the BEST I can do for those hurting as I was. ~ Eric Renouf and Beagleboy
        (thanks Eric)






        share|improve this answer












        finally I got my answer: The service wasn't running because the interfaces were down.
        1st. to fix interface:



        ifconfig eth0 up

        ifconfig usb0 up


        2nd. uninstall ANY other DHCPDaemons except uDHCPD to free up udp port 67. Use:



        netstat -tulnp |grep :67


        if nothing comes up, its uDHCPD is not running; you'll have to start it:



        http://xmodulo.com/raspberry-pi-wifi-access-point.html



        if you want to bridge them together after you're done:



        https://wiki.archlinux.org/index.php/Network_bridge



        the BEST I can do for those hurting as I was. ~ Eric Renouf and Beagleboy
        (thanks Eric)







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jun 7 '16 at 15:36









        Beagleboy

        12




        12






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f288167%2fhow-to-make-a-dhcp-server-using-busybox-udhcpd-for-multiple-ports%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Accessing regular linux commands in Huawei's Dopra Linux

            Can't connect RFCOMM socket: Host is down

            Kernel panic - not syncing: Fatal Exception in Interrupt