Maksim Yevmenkin wrote:
Pyun,
I can't sure but bridge(4) seems to have checksum related issues.
Here is my theory.
Interface A : H/W checksum offloading supported, Have IP address
Interface B : no H/W checksum offloading, No IP address assigned
Gateway : 192.168.10.1
| B
On Wed, May 11, 2005 at 12:25:49AM +0200, Jeremie Le Hen wrote:
> This is a little bit off-topic but I strongly support import of
> if_bridge(4). AFAIK the latter supports spanning-tree protocol whereas
> our bridge(4) doesn't.
We're working on it.
BMS
___
> if you think that porting OpenBSD/NetBSD bridge driver is a good idea
> you are welcome to submit the patches. imo, it should be possible to fix
> this in our current bridge(4) implementation. bridge(4) knows where
> packet is coming from and going to. it could check hardware capabilities
> o
Pyun,
I can't sure but bridge(4) seems to have checksum related issues.
Here is my theory.
Interface A : H/W checksum offloading supported, Have IP address
Interface B : no H/W checksum offloading, No IP address assigned
Gateway : 192.168.10.1
| Bridge
+--
Yes, this works, atleast on my development system. Thanks.
On Mon, 9 May 2005, Maksim Yevmenkin wrote:
Dear Hackers,
could someone please take/try a look at the attached patch? since i do not
have a card that is capable of hardware checksumming i can not test it here.
thanks,
max
Maksim Yevmenkin
Dear Hackers,
could someone please take/try a look at the attached patch? since i do
not have a card that is capable of hardware checksumming i can not test
it here.
thanks,
max
Maksim Yevmenkin wrote:
Patrick,
Yes, ifconfig -txcsum fixes the problem, so somewhere packets are not
getting marked
