[syslinux] syslinux.efi pxeboot across multiple subnets

Geert Stappers stappers at stappers.nl
Sat Nov 9 12:07:17 PST 2013


Answer:
    Because it messes up the order in which people normally read text,
    especially the archives of mailing lists.

Question:
    Why is Top-posting such a bad thing?


Op 2013-11-09 om 09:22 schreef Jason Matthews:
> On Sat, Nov 9, 2013 at 4:33 AM, Geert Stappers wrote:
> > Op 2013-11-08 om 15:44 schreef H. Peter Anvin:
> > >
> > > syslinux.efi either crashed or just can't get packets out.  Either of
> > > which is bad, obviously.
> >
> > And a thrid option, still bad: Send out packets didn't get across gateway.
> >
> > That is possible when the mirror port is at the same side of a gateway
> > as the TFTP server is. Euh, I mean visible where I said possible.
> >
> > Please confirm where in the network the tcpdump is made,
> > or even better: capture the packets near the booting machine.
> >
> > Something else: How many gateway / routers are involved?
> >
> 
> The setup I was using was in a chassis. Slot 8 of the chassis is the client
> machine. It goes through Switch 1 (a Brocade switch) to the top of rack
> (BNT). The mirror is in the chassis switch. Slot 3 of the same chassis is
> connected to the mirror port in Switch 1.
>
> client = 1/0/8
> tcpdump = 1/0/3
> to TOR = 1/0/43
> 1/0/8 mirrored both directions to 1/0/3
>
> Unfortunately, I don't have access to the switch configs of the TOR
> switches so I can't say how many gateways it's going through. 10.16.233.20
> goes through 10.16.233.1 and 10.16.195.178 goes through 10.16.194.1. All
> the switch magic after that is hidden from me.

Okay, thanks for elaborationg. Summary so far:

* network capture is done elsewhere as client is.
* syslinux.efi gets through
* When syslinux.efi should run, there is no sign of it in the network capture.


Regards
Geert Stappers
--
Yes, it is good to respect the discussion order


More information about the Syslinux mailing list