aniele B. wrote:
>
>> Actually i'm not sure about the real benefits of it, and for a soho
>> environment like mine but after 17 years I decided to take jumbo
>> frame seriously.. and MTU values of my network equipment to 9018.
>> I watched with happiness also to my
Daniele B. wrote:
> Actually i'm not sure about the real benefits of it, and for a soho
> environment like mine but after 17 years I decided to take jumbo
> frame seriously.. and MTU values of my network equipment to 9018.
> I watched with happiness also to my old Mac having
Claudio Jeker :
> This is not what hostname.if documents as a correct command line.
>
> Best is if you put mtu 9018 as a single line.
Indeed to make things easy I prefer to keep the mtu update in rc.local for now.
I was curious to clarify the error problem indeed, thnx.
On Tue, Nov 07, 2023 at 11:33:04AM +0100, Daniele B. wrote:
>
> Sorry Claudio, my fault.
>
> wiz# ifconfig reX hwfeatures
> hwfeatures= [*] hardmtu 9194
>
> by hostname.reX:
>
> wiz# nano /etc/hostname.reX:
> inet 192.168.XXX.XXX 0xff00 mtu 9018
This is not what hostname.if documents
Thanks this solved..
Zé Loff wrote:
> From man hostname.if:
>
> Regular IPv4 network setup:
> inet [alias] addr netmask broadcast_addr options
>
> The third argument after "inet" is the broadcast address. You have
> "mtu", which isn't one, hence the error. Try adding "N
"Peter N. M. Hansteen" wrote:
> try "ifconfig $device hwfeatures" and look for the "hardmtu" value.
>
> it is possible whatever mynicdevice is does not actually support
> jumbo frames.
Thxs, received, but not this case (hardmtu=9194) and however manually
the new MTU value goes up. There is s
On Tue, Nov 07, 2023 at 11:33:04AM +0100, Daniele B. wrote:
>
> Sorry Claudio, my fault.
>
> wiz# ifconfig reX hwfeatures
> hwfeatures= [*] hardmtu 9194
>
> by hostname.reX:
>
> wiz# nano /etc/hostname.reX:
> inet 192.168.XXX.XXX 0xff00 mtu 9018
>From man hostname.if:
Regular I
Sorry Claudio, my fault.
wiz# ifconfig reX hwfeatures
hwfeatures= [*] hardmtu 9194
by hostname.reX:
wiz# nano /etc/hostname.reX:
inet 192.168.XXX.XXX 0xff00 mtu 9018
ctrl+S; ctrl+X
wiz# sh /etc/netstart
ifconfig: mtu: bad value
(same eventually at boot time)
by shell or rc
On Tue, Nov 07, 2023 at 10:21:35AM +0100, Daniele B. wrote:
> About OpenBSD (7.3 stable) the only thing I need to ask explanation
> for is the reason of the error "wrong MTU value" popping up by setting
> jumbo frame directly via hostame.mynicdevice; when the setting go
> sm
On Tue, Nov 07, 2023 at 10:21:35AM +0100, Daniele B. wrote:
> Hello,
>
> Actually i'm not sure about the real benefits of it, and for a soho
> environment like mine but after 17 years I decided to take jumbo
> frame seriously.. and MTU values of my network equipment to 90
Hello,
Actually i'm not sure about the real benefits of it, and for a soho
environment like mine but after 17 years I decided to take jumbo
frame seriously.. and MTU values of my network equipment to 9018.
I watched with happiness also to my old Mac having jumbo frame hard
coded with MTU
On Thu, Mar 12, 2009 at 12:01:24PM -0300, Kleber Rocha wrote:
> OpenBSD supports jumbo frame
Yes
> if yes, how I do this configuration?
http://en.wikipedia.org/wiki/Jumbo_Frame
man ifconfig
On 12 March 2009 c. 18:01:24 Kleber Rocha wrote:
> Hello,
>
> OpenBSD supports jumbo frame, if yes, how I do this configuration?
man 8 ifconfig
man 4 name-of-your-nic-driver-here
--
Best wishes,
Vadim Zhukov
Hello,
OpenBSD supports jumbo frame, if yes, how I do this configuration?
Thanks
14 matches
Mail list logo
