On Sun, 2003-08-03 at 02:28, Terry Lambert wrote:
The fact of the matter is, if you use 802.1q encapsulation, the total
frame size can be 1504. That is the standard.
This is truly evil.
Actually, after a lot of discussions over this very topic during the
IEEE ratification process, the
Boris Kovalenko wrote:
I have Compaq DL360G2 with Broadcom BCM5701 Gigabit Ethernet and
FreeBSD 5.1R installed. There are no problems if I use bge as usual
network card, but when I try to use 802.1Q vlans, I can't receive (only
receive, sending is ok) packets more then 1456 bytes! What is
Terry Lambert wrote:
Hello!
Boris Kovalenko wrote:
I have Compaq DL360G2 with Broadcom BCM5701 Gigabit Ethernet and
FreeBSD 5.1R installed. There are no problems if I use bge as usual
network card, but when I try to use 802.1Q vlans, I can't receive (only
receive, sending is ok) packets more
On Sat, 2 Aug 2003, Terry Lambert wrote:
...
I suppose you want to do this because you are trunking a channel
that goes to a border device, and for some reason you have disabled
receipt of all ICMP, instead of only abusable ICMP, and thus you
have broken end-to-end path MTU discovery.
It
Boris Kovalenko wrote:
No, this is test machine, I have installed it two days ago and have
firewall_type=OPEN in my settings. So I have not disabled MTU path
discovery You are speaking of. Nevertheless, what is substracted from
available MTU? Why? The correct way it should work:
1500 bytes
Tom Samplonius wrote:
Probably wouldn't be affective anyhow. L2 switches assume that they can
encapsulate 1500 byte ethernet frames into 802.1q properly. It is part of
the 802.1q standard. If the NIC can't understand the frame because it is
now 1504 bytes, it will be a layer 2 discard.
Hello!
I have Compaq DL360G2 with Broadcom BCM5701 Gigabit Ethernet and
FreeBSD 5.1R installed. There are no problems if I use bge as usual
network card, but when I try to use 802.1Q vlans, I can't receive (only
receive, sending is ok) packets more then 1456 bytes! What is the
problem? BGE
Hm. A bit of a stab in the dark, but from sys/dev/bge/if_bge.c, line
3185 (on 5.1 release, 2399)
/* Specify MTU. */
CSR_WRITE_4(sc, BGE_RX_MTU, ifp-if_mtu +
ETHER_HDR_LEN + ETHER_CRC_LEN);
Wonder if this should be
/* Specify MTU. */
In article [EMAIL PROTECTED],
Peter Edwards [EMAIL PROTECTED] wrote:
Hm. A bit of a stab in the dark, but from sys/dev/bge/if_bge.c, line
3185 (on 5.1 release, 2399)
/* Specify MTU. */
CSR_WRITE_4(sc, BGE_RX_MTU, ifp-if_mtu +
ETHER_HDR_LEN + ETHER_CRC_LEN);
John Polstra [EMAIL PROTECTED] wrote:
Peter Edwards [EMAIL PROTECTED] wrote:
CSR_WRITE_4(sc, BGE_RX_MTU, ifp-if_mtu +
ETHER_HDR_LEN + ETHER_CRC_LEN + ETHER_VLAN_ENCAP_LEN);
Good guess, but the approved way of doing it is to add this code
near the point where
In article [EMAIL PROTECTED],
Peter Edwards [EMAIL PROTECTED] wrote:
John Polstra [EMAIL PROTECTED] wrote:
Peter Edwards [EMAIL PROTECTED] wrote:
CSR_WRITE_4(sc, BGE_RX_MTU, ifp-if_mtu +
ETHER_HDR_LEN + ETHER_CRC_LEN + ETHER_VLAN_ENCAP_LEN);
Good guess, but the
John Polstra [EMAIL PROTECTED] wrote:
No, you are right. I didn't read the posting carefully enough.
Sorry!
No problem.
[snip]
I assume you mean, that after setting if_hdrlen,
[snip]
I think you also have to set if_data.ifi_hdrlen as I said
[snip]
My fault: I jumped from one term for the
In article [EMAIL PROTECTED],
Peter Edwards [EMAIL PROTECTED] wrote:
John Polstra [EMAIL PROTECTED] wrote:
[snip]
I assume you mean, that after setting if_hdrlen,
[snip]
I think you also have to set if_data.ifi_hdrlen as I said
[snip]
My fault: I jumped from one term for the same
Ok. After all that, and given I've gone this far...
Boris, does the patch included fix your problem?
--
Peter Edwards.
Index: sys/dev/bge/if_bge.c
===
RCS file: /pub/FreeBSD/development/FreeBSD-CVS/src/sys/dev/bge/if_bge.c,v
14 matches
Mail list logo
