search for: pxenv_udp_writ

Displaying 8 results from an estimated 8 matches for "pxenv_udp_writ".

Did you mean: pxenv_udp_write
2005 Mar 06
2
etherboot 5.3.14 and pxelinux keyboard problem
Hello PXE folk, I mentioned in another thread that I had problems finding an etherboot that actually works with a 486 and Realtek 8019/NE2000 card. Etherboot worked up until v 5.3.5-mc1 with the ne driver but then stopped working between 5.3.7 to 5.3.13 (anoying since 5.3.7 started supporting PXELINUX. But then I downloaded 5.3.14 and it seems to work again with the ne driver (finally
2005 Mar 08
2
[Fwd: Re: etherboot 5.3.14 and pxelinux keyboard problem]
...asn't changed since July last year. You can debug this by defining -DTRACE_PXE when compiling Etherboot. This will show you a call trace such as Loading 10.254.254.2:pxelinux.0 ...(PXE).........done [PXENV_GET_CACHED_INFO 2 to 00000800][PXENV_GET_CACHED_INFO 3 to 00000800][PXENV_UDP_OPEN][PXENV_UDP_WRITE 40705->10.254.254.2:69 (63)][PXENV_UDP_READ 10.254.254.2:32833->10.254.254.1:40705 (19)][PXENV_UDP_WRITE 40706->10.254.254.2:69 (51)][PXENV_UDP_READ 10.254.254.2:32833->10.254.254.1:40706 (19)][PXENV_UDP_WRITE 40707->10.254.254.2:69 (50)] etc etc. Please try compiling Etherboot...
2005 Mar 09
0
Re: [Fwd: Re: etherboot 5.3.14 and pxelinux keyboard problem]
.... Here is the results: > > Etherboot 5.3.14 (GPL) http://etherboot.org > Drivers: 3C90X Images: NBI ELF PXE Exports: PXE > Protocols: DHCP TFTP > Relocating _text from: [00010420,00022880) to [5feedba0,5ff00000) > Boot from (N)etwork or (Q)uit? > > <snip> > [PXENV_UDP_WRITE 40708->10.0.0.100:69 (41)] > [PXENV_UDP_READ 10.0.0.100:33016->10.0.0.101:40708 (12)] > [PXENV_UDP_WRITE 40708->10.0.0.100:33016 (4)] > [PXENV_UDP_READ 10.0.0.100:33016->10.0.0.101:40708 (260)] > [PXENV_UDP_WRITE 40708->10.0.0.100:33016 (4)] > Unknown keyword in confi...
2009 May 24
1
Sending UDP packets from comboot
...at i want to do is: Prompt the user for 2 values, desired hostname and a "pin" (just a number) and send this information over UDP to my server The problem is not the user input but the UDP part. I've tried to change the code from the post of jesse barker (6.1.2007): // code start s_PXENV_UDP_WRITE args; memset(&args, 0, sizeof(args)); args.ip = inet_addr("255.255.255.255"); // inet_addr working here? args.gw = inet_addr("0.0.0.0"); args.src_port = 4711; args.dst_port = 4799; args.buffer_size = <some sizeof() code> args.buffer = <some stuff to put my data i...
2003 Apr 11
1
PXELINUX on top of Etherboot?
Question for people... Has anyone actually tried running PXELINUX on top of Etherboot? There is something in Etherboot 5.1.7 called FREEBSD_PXEEMU, which seems to be a PXE stack subset, in particular it seems to support the following calls: PXENV_GET_CACHED_INFO PXENV_UDP_OPEN PXENV_UDP_WRITE PXENV_UDP_READ PXENV_UDP_CLOSE PXENV_UNLOAD_STACK PXENV_UNDI_SHUTDOWN This happens to be pretty close to the subset used by PXELINUX, with two exceptions: PXELINUX will also invoke PXENV_STOP_UNDI (for version >= 2.00) or PXENV_UNDI_CLEANUP (for version < 2.00). I'd be really curious...
2009 May 28
1
Message 11 Syslinux Digest, Vol 74, Issue 24(Re: PXEboot trouble with Soekris 4826 (Miller, Shao)
...or 2 values, desired hostname and > a "pin" (just a number) and send this information > over UDP to my server > The problem is not the user input but the UDP part. > > I've tried to change the code from the post of jesse barker (6.1.2007): > > // code start > s_PXENV_UDP_WRITE args; > > memset(&args, 0, sizeof(args)); > > args.ip = inet_addr("255.255.255.255"); // inet_addr working here? > args.gw = inet_addr("0.0.0.0"); > args.src_port = 4711; > args.dst_port = 4799; > args.buffer_size = <some sizeof() code> > ar...
2012 Jul 16
5
[PATCH 0/5] Deleting __intcall() from Syslinux
From: Matt Fleming <matt.fleming at intel.com> Since we can't use __intcall() for EFI, and since we can now have the ELF module code resolve all our symbols at runtime, we should delete as many references to __intcall() as possible and just access the symbols directly. The most interesting patch is the support for weak symbols. We need to be able to reference derivative-specific
2012 Aug 14
1
[GIT PULL] elflink fixes
...oad_tftp.c index 5e73c1c..6a0dacb 100644 --- a/com32/libupload/upload_tftp.c +++ b/com32/libupload/upload_tftp.c @@ -53,7 +53,6 @@ const char *tftp_string_error_message[]={ static int send_ack_packet(struct tftp_state *tftp, const void *pkt, size_t len) { - com32sys_t ireg, oreg; t_PXENV_UDP_WRITE *uw; t_PXENV_UDP_READ *ur; clock_t start; @@ -67,9 +66,6 @@ static int send_ack_packet(struct tftp_state *tftp, uw = lmalloc(sizeof *uw + len); ur = lmalloc(sizeof *ur + RCV_BUF); - memset(&ireg, 0, sizeof ireg); - ireg.eax.w[0] = 0x0009; - for (timeout = time...