Re: [ipxe-devel] ipxe.org OSCP server check

On 03/09/2023 11:11, Geert Stappers via ipxe-devel wrote: When I do wget http://ca.ipxe.org/cross-ca.crt && \ wget https://ca.ipxe.org/ca.crt && \ openssl x509 -in cross-ca.crt -ocsp_uri -noout && \ openssl ocsp -issuer ca.crt -cert cross-ca.crt -text -url

Re: [ipxe-devel] ipxe.org OSCP server issues?

On 21/08/2023 18:57, Geert Stappers via ipxe-devel wrote: On Mon, Nov 26, 2018 at 03:26:20PM +, Michael Brown wrote: On 15/11/2018 21:21, Stephen Soltesz wrote: Are there any known issues with the ipxe.org OSCP servers? Yesterday I was able to boot a test server but

Re: [ipxe-devel] commit 3ef4f7e2ef4a22ea1e2eccc72957d7bf3fe2f945 breaks "prompt --key" command

On 07/07/2023 14:10, Michael Brown via ipxe-devel wrote: On 07/07/2023 09:32, Sven Dreyer via ipxe-devel wrote: I just noticed that my iPXE script containing a line "prompt --key 0x197e [..]" stopped working. Pressing F12 acted like I was pressing a different key. This worked in my

Re: [ipxe-devel] commit 3ef4f7e2ef4a22ea1e2eccc72957d7bf3fe2f945 breaks "prompt --key" command

On 07/07/2023 09:32, Sven Dreyer via ipxe-devel wrote: I just noticed that my iPXE script containing a line "prompt --key 0x197e [..]" stopped working. Pressing F12 acted like I was pressing a different key. This worked in my last build from June 11. Thanks to the comprehensive documentation,

Re: [ipxe-devel] IPv6 DHCP Behavior

On 05/04/2023 08:14, Ramesh Soni -X (ramsoni - Altran ACT S.A.S at Cisco) wrote: Thanks, Michael, for your response. We have not provided the boot filename in DHCPv4 so it is picking the file from DHCPv6. Although we are seeing some inconsistent behaviour here. We are seeing sometime DHCP

Re: [ipxe-devel] REG: Query on 9K MTU Testing flow

On 14/03/2023 16:45, MohamedShah R wrote: Thanks for the quick response. I am new to the PXE source code and tried out the below changes  for the experimental testing in the netdev_close api and it works fine. Why can't we have a new api netdev_reopen() which does the same logic of

Re: [ipxe-devel] IPv6 DHCP Behavior

On 03/04/2023 09:54, Andreas Fink wrote: so which fileame or url is being used if both answers? the one which answers first (which would be unpredictable order) If your network boot servers provide conflicting responses for the boot URL, then the behaviour is undefined. Michael

Re: [ipxe-devel] IPv6 DHCP Behavior

On 03/04/2023 08:39, Ramesh Soni -X (ramsoni - Altran ACT S.A.S at Cisco) via ipxe-devel wrote: We have both DHCPv4 and DHCPv6 running on same iPXE server. Our box is running iPXE code for downloading the image from ipv6, we have made entry in ipxe server dhcpd6.conf file for this box. First

Re: [ipxe-devel] REG: Query on 9K MTU Testing flow

On 13/03/2023 21:31, Michael Brown via ipxe-devel wrote: There is what looks like a bug when using DHCP to change MTU: the change of MTU requires the interface to be closed and reopened, but closing the interface will cause the initiating DHCP transaction itself to be aborted. This probably

Re: [ipxe-devel] REG: Query on 9K MTU Testing flow

On 13/03/2023 17:48, MohamedShah R wrote: Hi Michael,  Thanks for your response. Below is the flow- I have seen in the execution- it hits the intf_close as part of netdev_close called from apply_netdev_settings,.

Re: [ipxe-devel] REG: Query on 9K MTU Testing flow

On 13/03/2023 03:16, MohamedShah R via ipxe-devel wrote: 1. If our device configures netdev->mtu as 1500  and netdev->max_pkt_len is 9128(above 9k). 2. If the DHCP server sends MTU size as 9K.    As per the code walk-through, I understand that this api "staticintapply_netdev_settings”

Re: [ipxe-devel] linux16 /ipxe.lkrn output

On 19/02/2023 21:29, Geert Stappers via ipxe-devel wrote: What output to expect from ipxe.lkrn ( downloaded from https://boot.ipxe.org ) when started from grub? You should see the same output as when ipxe.lkrn is started from any other method, e.g.: iPXE initialising devices...ok iPXE

Re: [ipxe-devel] iPXE and Secure Boot

On 13/02/2023 21:05, Alex Chernyakhovsky wrote: Where are you located geographically? Debian Developers are by-design well connected within the PGP web of trust, and there are likely folks that would be happy to meet you and sign your keys. The WoT is somewhat fickle in terms of the bars

[ipxe-devel] iPXE and Secure Boot

Dear all, I'm in the process of trying to get a UEFI shim signed so that we are able to provide iPXE binaries that can be booted on a system with UEFI Secure Boot enabled. As part of the shim submission process, I need to create a PGP key (having never previously found a need for one), and

Re: [ipxe-devel] Issues with Broadcom NICs in Dell R7625

On 20/01/2023 13:54, Thomas Walker wrote: Anyway, I can move forward here. I have no intention of ever needing to PXE off of bnxt, so I can leave it out. And the "legacy NIC wrapper" warning appears to be cosmetic. But I'm willing to debug further if that is helpful since I know you don't

Re: [ipxe-devel] Issues with Broadcom NICs in Dell R7625

On 19/01/2023 16:48, Thomas Walker via ipxe-devel wrote: First off, I want to say thank you, the work done 2 years ago (https://github.com/ipxe/ipxe/commit/988d2c13cdf0f0b4140685af35ced70ac5b3283c) to fix walking through multiple instances of EFI_PCI_ROOT_BRIDGE_IO_PROTOCOL worked like a

Re: [ipxe-devel] [ipxe/ipxe] QRcode (#102)

> @NiKiZe Thanks! I tried a few things but it seems that im unable to get the > UCS-2 or 2byte char working for the ISO10646 charset. iPXE is currently ASCII-only. I am currently working on adding Unicode support in stages. The first part (allowing the use of UTF-8 in iPXE scripts, allowing

Re: [ipxe-devel] [ipxe/ipxe] Fixed bug in intel 10M/100M/1G NIC driver. (#52)

This was cleaned up into commit https://github.com/ipxe/ipxe/commit/2d79b20f2 -- Reply to this email directly or view it on GitHub: https://github.com/ipxe/ipxe/pull/52#issuecomment-1036448623 You are receiving this because you commented. Message ID:

Re: [ipxe-devel] [ipxe/ipxe] Fixed bug in intel 10M/100M/1G NIC driver. (#52)

Closed #52. -- Reply to this email directly or view it on GitHub: https://github.com/ipxe/ipxe/pull/52#event-6052904769 You are receiving this because you commented. Message ID: ___ ipxe-devel mailing list ipxe-devel@lists.ipxe.org