ifcheck not picking up IP

Help
2013-07-25
2013-08-05
  • hipsterdoofus

    hipsterdoofus - 2013-07-25

    I know I'm way behind here but I am running I think 0.42 and have noticed that compared to prior versions, I don't seem to get an IP correctly at first. Most times I seem to need to manually run ifcheck2.sh again once I am loaded up, and that always takes care of it.

    It appears that there are some differences between the ifcheck2.sh files between these two versions, but I'm not sure if that is where the problem is or not. I didn't know if you had heard of these issues and if I should just upgrade to the latest (I know, a pain to remember back to 0.42 I'm sure).

     
    • Michael Setzer II

      On 25 Jul 2013 at 21:07, hipsterdoofus wrote:

      To: "[g4l:discussion] " 408763@discussion.g4l.p.re.sf.net
      From: "hipsterdoofus" hipsterdoofus@users.sf.net
      Send reply to: "[g4l:discussion] " 408763@discussion.g4l.p.re.sf.net
      Subject: [g4l:discussion] ifcheck not picking up IP
      Date sent: Thu, 25 Jul 2013 21:07:28 +0000

      I know I'm way behind here but I am running I think 0.42 and have
      noticed that compared to prior versions, I don't seem to get an IP
      correctly at first. Most times I seem to need to manually run
      ifcheck2.sh again once I am loaded up, and that always takes care of
      it. It appears that there are some differences between the ifcheck2.sh
      files between these two versions, but I'm not sure if that is where
      the problem is or not. I didn't know if you had heard of these issues
      and if I should just upgrade to the latest (I know, a pain to remember
      back to 0.42 I'm sure).

      ifcheck not picking up IP

      I have not heard of any issues on it. As I recall, the original issue
      was that some dhcp servers were not responding quickly enough,
      so the process was not getting an ip. A 5 second sleep was put in
      and that seemed to resolve it for the user that provided the
      problem. It may be that something in your environment is causing
      it to fail. Could look at calling the ifcheck2.sh and then after it runs
      check to see if it got an ip, and if not try a second call to the script.

      Don't recall making any changes to ifcheck2.sh script, but there
      could have been. Would have to extract an old archived file to
      compare the script.

      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/g4l/discussion/408763/
      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

      +----------------------------------------------------------+
      Michael D. Setzer II - Computer Science Instructor
      Guam Community College Computer Center
      mailto:mikes@kuentos.guam.net
      mailto:msetzerii@gmail.com
      http://www.guam.net/home/mikes
      Guam - Where America's Day Begins
      G4L Disk Imaging Project maintainer
      http://sourceforge.net/projects/g4l/
      +----------------------------------------------------------+

      http://setiathome.berkeley.edu (Original)
      Number of Seti Units Returned: 19,471
      Processing time: 32 years, 290 days, 12 hours, 58 minutes
      (Total Hours: 287,489)

      BOINC@HOME CREDITS
      SETI 15529662.180023 | EINSTEIN 12486687.479852
      ROSETTA 8040175.416911 | ABC 16195541.802089

       
  • Michael Setzer II

    Could you run ipaddr after it fails to get an IP and report what it shows.
    The ifcheck2.sh is run as part of the /etc/init.d/rcS file, and am think a check of the ipaddr output might show something that can be tested to have it try again. It maybe that the nic isn't in a state that it can be brought up at that time, and might require a later call of ifcheck2.sh since it seems to work when you run it again, but don't want to call it again if it has already gotten an ip address.

     
  • hipsterdoofus

    hipsterdoofus - 2013-08-01

    Sure. It actually doesn't show an IP on eth0. Essentially the eth0 line looks about like the dummy0 line - no inet. Just has the first two lines. But yes, when I run ifcheck2.sh it gets one with no issue.

     
    • Michael Setzer II

      On 1 Aug 2013 at 16:01, hipsterdoofus wrote:

      To: "[g4l:discussion] " 408763@discussion.g4l.p.re.sf.net
      From: "hipsterdoofus" hipsterdoofus@users.sf.net
      Send reply to: "[g4l:discussion] " 408763@discussion.g4l.p.re.sf.net
      Subject: [g4l:discussion] ifcheck not picking up IP
      Date sent: Thu, 01 Aug 2013 16:01:36 +0000

      Sure. It actually doesn't show an IP on eth0. Essentially the eth0
      line looks about like the dummy0 line - no inet. Just has the first
      two lines. But yes, when I run ifcheck2.sh it gets one with no issue.

      Just wondering if we can figure out why it is not getting the IP
      address during the call to ifcheck2.sh in the rcS script during the
      init.d process?

      Could you see what dmesg | grep eth0 reports?
      It could be easy to have it just call ifcheck2.sh a second time if it
      doesn't get an ip in the rcS script, but if whatever is the issue still
      fails at that point it would not solve anything, and would further
      delay the boot.

      Could also add a call to ifcheck2.sh in the g4lmenu script that
      happens at the end of the booting process, but if one has a
      system that is not connected to a network with a dhcpd server it
      will just take time and fail again.

      During the initial boot, what message does the ifcheck2.sh should.
      Does it see the nic, and then fail on the finding a link, or fail on
      getting an IP?

      Thanks again for taking the time to do testing?
      What type of nic is it?

      ifcheck not picking up IP

      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/g4l/discussion/408763/
      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

      +----------------------------------------------------------+
      Michael D. Setzer II - Computer Science Instructor
      Guam Community College Computer Center
      mailto:mikes@kuentos.guam.net
      mailto:msetzerii@gmail.com
      http://www.guam.net/home/mikes
      Guam - Where America's Day Begins
      G4L Disk Imaging Project maintainer
      http://sourceforge.net/projects/g4l/
      +----------------------------------------------------------+

      http://setiathome.berkeley.edu (Original)
      Number of Seti Units Returned: 19,471
      Processing time: 32 years, 290 days, 12 hours, 58 minutes
      (Total Hours: 287,489)

      BOINC@HOME CREDITS
      SETI 15593891.978307 | EINSTEIN 12582183.199852
      ROSETTA 8106529.032928 | ABC 16203970.426818

       
  • hipsterdoofus

    hipsterdoofus - 2013-08-01

    Not sure if this helps or not. When I start, it does the initial check and SAYS that it has found eth0 with Active link and running DHCP client. I believe it then says it couldn't acquire an IP via dhcp, so perhaps the issue is on my end, and seems to be wholly contained within the ifcheck2 script. Just odd that if I run it manually right after that it seems to get the IP.

     
    • Michael Setzer II

      On 1 Aug 2013 at 16:41, hipsterdoofus wrote:

      To: "[g4l:discussion] " 408763@discussion.g4l.p.re.sf.net
      From: "hipsterdoofus" hipsterdoofus@users.sf.net
      Send reply to: "[g4l:discussion] " 408763@discussion.g4l.p.re.sf.net
      Subject: [g4l:discussion] ifcheck not picking up IP
      Date sent: Thu, 01 Aug 2013 16:41:16 +0000

      Not sure if this helps or not. When I start, it does the initial check
      and SAYS that it has found eth0 with Active link and running DHCP
      client. I believe it then says it couldn't acquire an IP via dhcp, so
      perhaps the issue is on my end, and seems to be wholly contained
      within the ifcheck2 script. Just odd that if I run it manually right
      after that it seems to get the IP.

      OK, that rules out that the nic isn't being detected. Long ago, the
      check process only had a 3 second delay, and that caused some
      issues with getting a response it time, so it was changed to 5 and
      that resolved that users issue. Maybe that your dhcpd server for
      some reason is taking longer than 5 seconds to resolve the ip
      address to give.

      Was just looking at dhcpc options, and currently it uses -n that is
      set to exit if lease is not obtained, but there is also a -t option to
      set retries. Will have to look at the options.

      ifcheck not picking up IP

      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/g4l/discussion/408763/
      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

      +----------------------------------------------------------+
      Michael D. Setzer II - Computer Science Instructor
      Guam Community College Computer Center
      mailto:mikes@kuentos.guam.net
      mailto:msetzerii@gmail.com
      http://www.guam.net/home/mikes
      Guam - Where America's Day Begins
      G4L Disk Imaging Project maintainer
      http://sourceforge.net/projects/g4l/
      +----------------------------------------------------------+

      http://setiathome.berkeley.edu (Original)
      Number of Seti Units Returned: 19,471
      Processing time: 32 years, 290 days, 12 hours, 58 minutes
      (Total Hours: 287,489)

      BOINC@HOME CREDITS
      SETI 15593891.978307 | EINSTEIN 12582183.199852
      ROSETTA 8106529.032928 | ABC 16203970.426818

       
  • Michael Setzer II

    Did some testing, and have come up with a possible solution?

    Added the options to the ifcheck2.sh with the udhcpc command to include -t 8 -T 5.

    By default the udhcpc would send 3 dhcpd request, so the -t 8 changes that to 8.
    The -T 5 changes the pause from 3 seconds to 5 seconds.

    ftp://amd64gcc.dyndns.org/g4l0.46alpha/g4l-v0.46alpha24.iso

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks