similar to: Polycom SSIP 7000 : how to boot with DHCP (instead of BOOTP) ?

Using PXELINUX and MEMDISK I started a MS-DOS-Diskimage. How can I get the DHCP-Options or BOOTP-Tags from within MS-DOS?? (Like bppatch from 3com.) Thanks! _______________________________________________________________________ Jetzt neu! Sch?tzen Sie Ihren PC mit McAfee und WEB.DE. 3 Monate kostenlos testen. http://www.pc-sicherheit.web.de/startseite/?mc=022220

Hi All, Has anyone gotten the polycoms or the linksys phones to accept oprtion 66 on the dhcp request for the address of the tftp config server? We have the dhcp server issuing the proper IP of the tftp server, but the phones just sit there and never try to contact the tftp server for their configs. We can see the proper option going from the dhcp to the phones with ethereal trace. Thanks JR

On Sun, Sep 13, 2015 at 3:46 PM, Geert Stappers via Syslinux <syslinux at zytor.com> wrote: > On Sat, Sep 12, 2015 at 06:56:04PM -0400, Gene Cumm via Syslinux wrote: >> On Sat, Sep 12, 2015 at 6:37 PM, Gene Cumm wrote: >> > On Sat, Sep 12, 2015 at 10:23 AM, Geert Stappers wrote: >> >> diff --git a/core/fs/pxe/dhcp_option.c b/core/fs/pxe/dhcp_option.c >>

Is there any way to prevent the BOOTP client from injecting a default route? When I originally set things up our DHCP server would not send a default route because there was no gateway, local only. If you leave out the default route, the server will try proxy-arp when ends up putting a default route to itself in the routing table. The problem is that on startup the servers actually

On Sat, Sep 12, 2015 at 7:37 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sat, Sep 12, 2015 at 7:08 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On Sat, Sep 12, 2015 at 5:54 AM, Teun Docter >> <teun.docter at brightcomputing.com> wrote: >>> On 2015-09-12 04:58, Gene Cumm wrote: >>>>> >>>>> I've captured the

On Sat, Sep 12, 2015 at 10:23 AM, Geert Stappers <stappers at stappers.nl> wrote: > On Sat, Sep 12, 2015 at 08:42:15AM -0400, Gene Cumm via Syslinux wrote: >> On Sat, Sep 12, 2015 at 7:37 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> > On Sat, Sep 12, 2015 at 7:08 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >> On Sat, Sep 12, 2015 at 5:54 AM,

>On Sat, Sep 12, 2015 at 6:37 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> >... > >> Something like this would be preferable except it's not quite so >> simple. We'd need to not store BOOTP siaddr before parsing. Store a >> pointer to the string during parsing if serverip is unset. After all >> parsing, if the pointer is set, attempt to

In order of making it easier to differentiate between existing clients and clients that I bring up only for installation and configuration I tried the following configuration. subnet 192.168.1.0 netmask 255.255.255.0 { pool { range 192.168.1.101 192.168.1.150; default-lease-time 86400; max-lease-time 604800; } pool { range dynamic-bootp 192.168.1.151

On Sat, Sep 12, 2015 at 6:37 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sat, Sep 12, 2015 at 10:23 AM, Geert Stappers <stappers at stappers.nl> wrote: >> Euh, could this be reviewed: >> >> diff --git a/core/fs/pxe/dhcp_option.c b/core/fs/pxe/dhcp_option.c >> index 8d93a6a..b82e944 100644 >> --- a/core/fs/pxe/dhcp_option.c >> +++

On Sat, Sep 12, 2015 at 06:56:04PM -0400, Gene Cumm via Syslinux wrote: > On Sat, Sep 12, 2015 at 6:37 PM, Gene Cumm wrote: > > On Sat, Sep 12, 2015 at 10:23 AM, Geert Stappers wrote: > >> diff --git a/core/fs/pxe/dhcp_option.c b/core/fs/pxe/dhcp_option.c > >> index 8d93a6a..b82e944 100644 > >> --- a/core/fs/pxe/dhcp_option.c > >> +++

On Sat, Sep 12, 2015 at 7:08 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sat, Sep 12, 2015 at 5:54 AM, Teun Docter > <teun.docter at brightcomputing.com> wrote: >> On 2015-09-12 04:58, Gene Cumm wrote: >>>> >>>> I've captured the following DHCP ACK: >>>> >>>> 10.141.20.1.bootps > 10.141.20.2.bootpc: [udp sum ok]

On Sat, Sep 12, 2015 at 08:42:15AM -0400, Gene Cumm via Syslinux wrote: > On Sat, Sep 12, 2015 at 7:37 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > > On Sat, Sep 12, 2015 at 7:08 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > >> On Sat, Sep 12, 2015 at 5:54 AM, Teun Docter > >> <teun.docter at brightcomputing.com> wrote: > >>> On

On 2015-09-12 04:58, Gene Cumm wrote: >> I've captured the following DHCP ACK: >> >> 10.141.20.1.bootps > 10.141.20.2.bootpc: [udp sum ok] BOOTP/DHCP, Reply, >> length 399, xid 0xf0eb955a, secs 14, Flags [none] (0x0000) >> Your-IP 10.141.20.2 >> Server-IP 10.141.255.254 >> Client-Ethernet-Address fa:16:3e:08:31:b9

On Sat, Sep 12, 2015 at 5:54 AM, Teun Docter <teun.docter at brightcomputing.com> wrote: > On 2015-09-12 04:58, Gene Cumm wrote: >>> >>> I've captured the following DHCP ACK: >>> >>> 10.141.20.1.bootps > 10.141.20.2.bootpc: [udp sum ok] BOOTP/DHCP, Reply, >>> length 399, xid 0xf0eb955a, secs 14, Flags [none] (0x0000) >>>

On Fri, Sep 11, 2015 at 5:24 PM, Teun Docter via Syslinux <syslinux at zytor.com> wrote: > Hello list, > > We have a scenario where our TFTP server is not the same IP as our DHCP > server. While testing with 6.03, our setup works just fine. > > However with the master branch, for some reason pxelinux.0 is fetched from > the TFTP servers IP, but then it tries to load

Hello list, We have a scenario where our TFTP server is not the same IP as our DHCP server. While testing with 6.03, our setup works just fine. However with the master branch, for some reason pxelinux.0 is fetched from the TFTP servers IP, but then it tries to load ldlinux.c32 from the DHCP servers IP. I've tracked down this problem to the following commit:

Hi guys ipconfig performs not well conformed DHCP client transactions. This bug does not affect 100% of the DHCP servers as some of them are more forgiving than others when considering client side protocol mistakes; i.e When PXE installing on a VMware Workstation using the VMware DHCP server plus a proxyDHCP the bug is not present. When PXE installing on a real PC with a Netgear ISP

kinit/nfsmount.c:mount_nfs_root() should use the bootpath specified by bootp/dhcp. If the "nfsroot" option is specified then it overrides the boot server bootpath and a message indicating the override is printed. --- klibc-0.194/kinit/nfsroot.c.orig 2005-01-05 04:13:47.043897880 -0700 +++ klibc-0.194/kinit/nfsroot.c 2005-01-05 04:13:09.316633296 -0700 @@ -66,34 +66,21 @@ const int

I'd like to start configuring my Avaya 9608G phones for use on Asterisk / FreePBX / PBX-In-a-Flash. I'm using a variety of other phones on my system without major issues. I've read the discussion back in March, May and August of 2016, but unfortunately, my difficulty is much more basic. I think it has to do with DHCP, specifically, what options I'm offering the phone via DHCP.

If a hostname is requested, for example -d ::::foo::dhcp, then include the hostname in the DHCP discover/request. This patch also allows the vendor class identifier to be omitted from the DHCP discover/request by specifying -i "" Signed-off-by: Aron Griffis <agriffis at n01se.net> --- usr/kinit/ipconfig/dhcp_proto.c | 49 ++++++++++++++++++++++++++++++--------