Hans-Peter Jansen <[EMAIL PROTECTED]> writes:
> Hi Shane,
>
> Difference: 181 Bytes (padding ignored)
>
> The whole module takes about 9K, compared to dhcp in initrd, which
> takes a few hundred K! Hmm.
And the kinit from the klibc package (A static executable that
does everything the kernel
Hans-Peter Jansen [EMAIL PROTECTED] writes:
Hi Shane,
Difference: 181 Bytes (padding ignored)
The whole module takes about 9K, compared to dhcp in initrd, which
takes a few hundred K! Hmm.
And the kinit from the klibc package (A static executable that
does everything the kernel
Hans-Peter Jansen wrote:
On Thursday 03 February 2005 05:47, Shane Hathaway wrote:
The attached patch enhances the kernel's DHCP client support (in
net/ipv4/ipconfig.c) to set the interface MTU if provided by the
DHCP server. Without this patch, it's difficult to netboot on a
network that uses
On Friday 04 February 2005 19:22, Richard A Nelson wrote:
>
> What will this code do at the (increasingly common) misconfigured
> sites - many places (hotels, airports, etc) return a MTU of 64...
> to which the DHCP3 client faithfully attempts to set, only to
> receive:
> SIOCSIFMTU: Invalid
On Fri, 4 Feb 2005, Hans-Peter Jansen wrote:
> On Thursday 03 February 2005 05:47, Shane Hathaway wrote:
> > The attached patch enhances the kernel's DHCP client support (in
> > net/ipv4/ipconfig.c) to set the interface MTU if provided by the
> > DHCP server. Without this patch, it's difficult to
Hi Shane,
On Thursday 03 February 2005 05:47, Shane Hathaway wrote:
> The attached patch enhances the kernel's DHCP client support (in
> net/ipv4/ipconfig.c) to set the interface MTU if provided by the
> DHCP server. Without this patch, it's difficult to netboot on a
> network that uses jumbo
On Thursday 03 February 2005 06:47, Shane Hathaway wrote:
> The attached patch enhances the kernel's DHCP client support (in
> net/ipv4/ipconfig.c) to set the interface MTU if provided by the DHCP server.
>
> Without this patch, it's difficult to netboot on a network that uses jumbo
> frames.
On Thursday 03 February 2005 06:47, Shane Hathaway wrote:
The attached patch enhances the kernel's DHCP client support (in
net/ipv4/ipconfig.c) to set the interface MTU if provided by the DHCP server.
Without this patch, it's difficult to netboot on a network that uses jumbo
frames. The
Hi Shane,
On Thursday 03 February 2005 05:47, Shane Hathaway wrote:
The attached patch enhances the kernel's DHCP client support (in
net/ipv4/ipconfig.c) to set the interface MTU if provided by the
DHCP server. Without this patch, it's difficult to netboot on a
network that uses jumbo frames.
On Fri, 4 Feb 2005, Hans-Peter Jansen wrote:
On Thursday 03 February 2005 05:47, Shane Hathaway wrote:
The attached patch enhances the kernel's DHCP client support (in
net/ipv4/ipconfig.c) to set the interface MTU if provided by the
DHCP server. Without this patch, it's difficult to
On Friday 04 February 2005 19:22, Richard A Nelson wrote:
What will this code do at the (increasingly common) misconfigured
sites - many places (hotels, airports, etc) return a MTU of 64...
to which the DHCP3 client faithfully attempts to set, only to
receive:
SIOCSIFMTU: Invalid
Hans-Peter Jansen wrote:
On Thursday 03 February 2005 05:47, Shane Hathaway wrote:
The attached patch enhances the kernel's DHCP client support (in
net/ipv4/ipconfig.c) to set the interface MTU if provided by the
DHCP server. Without this patch, it's difficult to netboot on a
network that uses
Followup to: <[EMAIL PROTECTED]>
By author:Herbert Xu <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Have you looked at using initramfs and running the DHCP client in
> user space? You'll get a lot more freedom that way.
>
Note that the klibc distribution already contains a working
Herbert Xu wrote:
Shane Hathaway <[EMAIL PROTECTED]> wrote:
The attached patch enhances the kernel's DHCP client support (in
net/ipv4/ipconfig.c) to set the interface MTU if provided by the DHCP server.
Without this patch, it's difficult to netboot on a network that uses jumbo
frames. The
Shane Hathaway <[EMAIL PROTECTED]> wrote:
>
> The attached patch enhances the kernel's DHCP client support (in
> net/ipv4/ipconfig.c) to set the interface MTU if provided by the DHCP server.
>
> Without this patch, it's difficult to netboot on a network that uses jumbo
> frames. The patch
Shane Hathaway [EMAIL PROTECTED] wrote:
The attached patch enhances the kernel's DHCP client support (in
net/ipv4/ipconfig.c) to set the interface MTU if provided by the DHCP server.
Without this patch, it's difficult to netboot on a network that uses jumbo
frames. The patch is based
Herbert Xu wrote:
Shane Hathaway [EMAIL PROTECTED] wrote:
The attached patch enhances the kernel's DHCP client support (in
net/ipv4/ipconfig.c) to set the interface MTU if provided by the DHCP server.
Without this patch, it's difficult to netboot on a network that uses jumbo
frames. The patch
Followup to: [EMAIL PROTECTED]
By author:Herbert Xu [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
Have you looked at using initramfs and running the DHCP client in
user space? You'll get a lot more freedom that way.
Note that the klibc distribution already contains a working dhcp
The attached patch enhances the kernel's DHCP client support (in
net/ipv4/ipconfig.c) to set the interface MTU if provided by the DHCP server.
Without this patch, it's difficult to netboot on a network that uses jumbo
frames. The patch is based on 2.6.10, but I'll update it to the latest
The attached patch enhances the kernel's DHCP client support (in
net/ipv4/ipconfig.c) to set the interface MTU if provided by the DHCP server.
Without this patch, it's difficult to netboot on a network that uses jumbo
frames. The patch is based on 2.6.10, but I'll update it to the latest
20 matches
Mail list logo
