Displaying 6 results from an estimated 6 matches for "snaplength".
2013 Nov 08
3
syslinux.efi pxeboot across multiple subnets
...ng the text output of tcpdump.
Fetch the new capture with
wget -O pcap2.zip http://ge.tt/api/1/files/136167y/0/blob?downlad
The capture[1] shows two[2] TFTP transmissions of sles113/syslinux.efi,
but nothing after that. As if syslinux.efi was crashed.
Groeten
Geert Stappers
Notes
[1] With a snaplength of 96 bytes or something.
Add -S0 to tcpdump to get the full network packets.
[2] A previous posting says that the repeated transmission
is an artifact of the firmware.
2013 Nov 09
3
syslinux.efi pxeboot across multiple subnets
...ch the new capture with
> >
> > wget -O pcap2.zip http://ge.tt/api/1/files/136167y/0/blob?downlad
> >
> > The capture[1] shows two TFTP transmissions of sles113/syslinux.efi,
> > but nothing after that. As if syslinux.efi was crashed.
> >
> > [1] With a snaplength of 96 bytes or something.
> > Add -S0 to tcpdump to get the full network packets.
>
> 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 pos...
2013 Nov 08
0
syslinux.efi pxeboot across multiple subnets
...>
> wget -O pcap2.zip http://ge.tt/api/1/files/136167y/0/blob?downlad
>
>
> The capture[1] shows two[2] TFTP transmissions of sles113/syslinux.efi,
> but nothing after that. As if syslinux.efi was crashed.
>
> Groeten
> Geert Stappers
>
> Notes
> [1] With a snaplength of 96 bytes or something.
> Add -S0 to tcpdump to get the full network packets.
> [2] A previous posting says that the repeated transmission
> is an artifact of the firmware.
syslinux.efi either crashed or just can't get packets out. Either of
which is bad, obviously.
-hpa
2013 Nov 09
0
syslinux.efi pxeboot across multiple subnets
...; >
> > > wget -O pcap2.zip http://ge.tt/api/1/files/136167y/0/blob?downlad
> > >
> > > The capture[1] shows two TFTP transmissions of sles113/syslinux.efi,
> > > but nothing after that. As if syslinux.efi was crashed.
> > >
> > > [1] With a snaplength of 96 bytes or something.
> > > Add -S0 to tcpdump to get the full network packets.
> >
> > 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...
2013 Nov 09
1
syslinux.efi pxeboot across multiple subnets
.../ge.tt/api/1/files/136167y/0/blob?downlad
>>
>>
>> The capture[1] shows two[2] TFTP transmissions of sles113/syslinux.efi,
>> but nothing after that. As if syslinux.efi was crashed.
>>
>> Groeten
>> Geert Stappers
>>
>> Notes
>> [1] With a snaplength of 96 bytes or something.
>> Add -S0 to tcpdump to get the full network packets.
>> [2] A previous posting says that the repeated transmission
>> is an artifact of the firmware.
>
> syslinux.efi either crashed or just can't get packets out. Either of
> which...
2013 Nov 08
4
syslinux.efi pxeboot across multiple subnets
I did change both instances of txdata->GatewayAddress, but I think
something may be wrong in my toolchain. If I extract syslinux.zip and
attempt to make from there (without modifying any files), the cached DHCP
packet isn't read on the same subnet.
I receive "Succeed to download NBP file." twice before anything from
syslinux is loaded, so I believe the duplicate request for