> 1) create a static ARP entry, this will create an entry to
> the routing table i.e. arp -S IPADDR MACADDR
> 2) modify the mtu for that destination
> i.e. route change IPADDR -mtu MTU
Seems to work fine :)
One problem with this approach is that a hard-coded MAC address
would break if the des
On Monday 04 August 2008 00:16:54 [EMAIL PROTECTED] wrote:
> > > >> Is there a simple way for a FreeBSD system to cause its
> > > >> peer to use a transmit segment size of, say, 640 bytes --
> > > >> so that the peer will never try to send a packet larger
> > > >> than that?
> > > >>
> > > >> I'm t
> > >> Is there a simple way for a FreeBSD system to cause its
> > >> peer to use a transmit segment size of, say, 640 bytes --
> > >> so that the peer will never try to send a packet larger
> > >> than that?
> > >>
> > >> I'm trying to get around a network packet-size problem.
> > >> In case it m
On Thu, 31 Jul 2008 01:43:11 -0700, [EMAIL PROTECTED] wrote:
>> You can edit `/etc/hostname.foo0' in the Sun too, and add
>> something like:
>>
>> 192.168.1.10/24 mtu 640
>
> [getting OT for FreeBSD]
>
> Are you sure that works as far back as SunOS 4.1.1?
Ah! That will not work, you are right
> You can edit `/etc/hostname.foo0' in the Sun too, and add
> something like:
>
> 192.168.1.10/24 mtu 640
[getting OT for FreeBSD]
Are you sure that works as far back as SunOS 4.1.1?
/etc/hostname.le0 currently consists of the single word
pluto
and it looks as if this causes /etc/rc.boot
On Thursday 31 July 2008 01:21:25 Giorgos Keramidas wrote:
> On Wed, 30 Jul 2008 16:20:06 -0500, Derek Ragona
<[EMAIL PROTECTED]> wrote:
> > At 11:04 PM 7/29/2008, [EMAIL PROTECTED] wrote:
> >> > [TCP] splits traffic to 'segments' using its own logic ...
> >>
> >> Is there a simple way for a FreeB
On Wed, 30 Jul 2008 16:20:06 -0500, Derek Ragona <[EMAIL PROTECTED]> wrote:
> At 11:04 PM 7/29/2008, [EMAIL PROTECTED] wrote:
>> > [TCP] splits traffic to 'segments' using its own logic ...
>>
>> Is there a simple way for a FreeBSD system to cause its peer to use a
>> transmit segment size of, say,
At 11:04 PM 7/29/2008, [EMAIL PROTECTED] wrote:
> [TCP] splits traffic to 'segments' using its own logic ...
Is there a simple way for a FreeBSD system to cause its peer
to use a transmit segment size of, say, 640 bytes -- so that
the peer will never try to send a packet larger than that?
I'm t
On Wed, 30 Jul 2008 00:09:45 -0700, [EMAIL PROTECTED] wrote:
Is there a simple way for a FreeBSD system to cause its peer to
use a transmit segment size of, say, 640 bytes -- so that the peer
will never try to send a packet larger than that?
I'm trying to get around a netwo
> >> Is there a simple way for a FreeBSD system to cause its peer
> >> to use a transmit segment size of, say, 640 bytes -- so that
> >> the peer will never try to send a packet larger than that?
> >>
> >> I'm trying to get around a network packet-size problem. In
> >> case it matters, the other e
On Tue, 29 Jul 2008 21:04:53 -0700, [EMAIL PROTECTED] wrote:
>> [TCP] splits traffic to 'segments' using its own logic ...
>
> Is there a simple way for a FreeBSD system to cause its peer
> to use a transmit segment size of, say, 640 bytes -- so that
> the peer will never try to send a packet large
On Wed, 30 Jul 2008 07:36:34 +0300, Giorgos Keramidas <[EMAIL PROTECTED]> wrote:
> On Tue, 29 Jul 2008 21:04:53 -0700, [EMAIL PROTECTED] wrote:
>>> [TCP] splits traffic to 'segments' using its own logic ...
>>
>> Is there a simple way for a FreeBSD system to cause its peer
>> to use a transmit segm
> [TCP] splits traffic to 'segments' using its own logic ...
Is there a simple way for a FreeBSD system to cause its peer
to use a transmit segment size of, say, 640 bytes -- so that
the peer will never try to send a packet larger than that?
I'm trying to get around a network packet-size problem.
13 matches
Mail list logo
