Re: [ts-7000] Re: Default IP when dhcp fails (dhclient or pump) on TS7800

[Larry <>]

I know you can make this work. I've done it, but it's been so long I don't remember the details.
However, I do remember that one of the issues was making the timeout reasonable for dhcp discover.
Some networks are really slow. I had to make it something like 30 seconds so the static configuration didn't jump the gun.

fulatoro wrote:

Jim,

That is an awesome idea, it might actually work, I have to see where
exactly to call that script, but I anticipate that it should work, I
will try and let you know.

Moussa

--- In .com, Jim Jackson m("...","jj");"><> wrote:
>
>
>
>
> On Fri, 3 Oct 2008, fulatoro wrote:
>
> > Jim, I am perfectly aware of the fact that pump is a dhcp client. You
> > jump to conclusions without truly understanding the problem.
> >
> > My customers only have access to the unit via a web interface. This
> > unit is installed in many facilities. Some facilities will have DHCP,
> > others will not. I have a web a interface that allows the
> > configuration to be set to either DHCP or Static IP. The problem,
> > I repeat is that if the unit is left on DHCP and connected to a
> > network that does not have a DHCP server, it will not obtain an IP
> > address and become unreachable.
> >
> > The consequence is that the customer will not be able to connect to
> > the box to reconfigure as IT DOES NOT HAVE an IP.
> >
> > Configuration is done via a cross over cable with a laptop where the
> > laptop is configured to be on the same network as the unit. Hence if
> > my dhcp client defaults to 192.168.0.50, it will always be accessible
> > via a cross over cable.
> >
> > Does it make sense now?
>
> A suggestion which _MAY_ work, put in an ifconfig for the interface
just
> before the dhcp client is started in the relevant start up script.
If dhcp
> works it will override this, if not it will be configured anyway?
>
> > --- In .com, Jim Jackson <jj@> wrote:
> >>
> >>
> >>
> >>
> >> On Thu, 25 Sep 2008, fulatoro wrote:
> >>
> >>> I am trying to default to 192.168.0.50 if my board is setup for dhcp
> >>> and fails to obtain an IP from the server or is not connected to the
> >>> network. Currently, if the dhcp request fails, I end up not
having an
> >>> IP address on eth0 and the board is inaccessible except via the
> >>> console. I would like to ensure that when dhcp fails that at least
> >>> the IP is configured.
> >>
> >> This is only meaningful if you know which network you are on,
> >> and if you know that, you can stop using dhcp and permanently
> > configure an
> >> address, subnet, and default router.
> >>
> >>> ..... If the unit is not on a network with a
> >>> similar subnet, then it would fail.
> >>
> >> If the device is going to be portable and be on several networks then
> >> configuring a fixed address and default router is a waste of time,
> > as you
> >> noted.
> >>
> >>> I have looked at pump briefly but failed to find an appropriate
> > solution.
> >>
> >> pump is a dhcp client!!!!!!
> >>
> >> Jim
> >>
> >
> >
> >
>

No virus found in this incoming message.
Checked by AVG. 
Version: 7.5.524 / Virus Database: 270.7.5/1706 - Release Date: 10/3/2008 6:17 PM
  

__._,_.___

Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: =Email Delivery: Digest | m("yahoogroups.com?subject","ts-7000-fullfeatured");=Change Delivery Format: Fully Featured">Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | =Unsubscribe

__,_._,___