Stephen Clark wrote:
Artyom Viklenko wrote:
Artem Belevich wrote:
Here's one example where MTU!=MRU would be useful.
Think of asymmetric bandwith-limited ADSL links. Lower MTU would allow
lower TX latency for high priority packets when upstream is saturated,
yet large MRU on the downstream
Hello.
I have a FreeBSD machine connected to internal network and several ISPs. I
have set up (with pf) nat and balanced (policy-based) routing for machines
from internal network, proper routing for remote connections to interfaces
that connected to corresponding ISPs.
One thing that I can't mana
Hi,
I may have some commercial work coming up which requires me to make
modifications to the IPv4 multicast forwarding code in Linux. It is
likely I will prototype the work in FreeBSD. It will probably not be
released publicly.
To prepare for this I have started cleaning up the MROUTING code
On Sunday 22 July 2007, [EMAIL PROTECTED] wrote:
> Hello.
>
...
>
> At the moment I'm trying to get that working with netgraph's ngeth
> interfaces. But they seem to behave in some really weird way.
> Details:
> # ifconfig ngeth0 10.42.42.1 netmask 255.255.255.250
Netmask 255.255.255.250 looks wei
Mike Karels wrote:
Any two hosts, connected to single Layer2 network MUST use
same MTU. Any other cases lead to hard-to-solve problems.
I'd have to disagree. In fact, I'd say that any two hosts on the
same L2 network must use the same MRU. In particular, if a host
choses to use a lower MTU, i
> On Sunday 22 July 2007, [EMAIL PROTECTED] wrote:
>> At the moment I'm trying to get that working with netgraph's ngeth
>> interfaces. But they seem to behave in some really weird way.
>> Details:
>> # ifconfig ngeth0 10.42.42.1 netmask 255.255.255.250
>
> Netmask 255.255.255.250 looks weird to me
[EMAIL PROTECTED] wrote:
Hello.
I have a FreeBSD machine connected to internal network and several ISPs. I
have set up (with pf) nat and balanced (policy-based) routing for machines
from internal network, proper routing for remote connections to interfaces
that connected to corresponding ISPs.