Julian Elischer wrote:
Ragnar Lonn wrote:
Hello all,
Does anyone know if virtual network stack support (as implemented at
http://www.tel.fer.hr/zec/vimage/) is on the roadmap for future
FreeBSD releases?
that depends on who you are talking to :-)
the problems are not with the concept of virtual
It appear that ipfw doesn't work with bridge in 5.3 and 5.4. The
symptoms are that the bridge stops forwarding packets altogether,
for me a few minutes after it is set up. It takes a
# net.link.ether.bridge_ipfw=0 && sleep 5 && net.link.ether.bridge_ipfw=1
to get it back up and running, which i
El Miércoles, 4 de Mayo de 2005 16:24, Josef Karthauser escribió:
> It appear that ipfw doesn't work with bridge in 5.3 and 5.4. The
> symptoms are that the bridge stops forwarding packets altogether,
> for me a few minutes after it is set up. It takes a
>
> # net.link.ether.bridge_ipfw=0 && slee
El Miércoles, 4 de Mayo de 2005 16:47, Jose M Rodriguez escribió:
> El Miércoles, 4 de Mayo de 2005 16:24, Josef Karthauser escribió:
> > It appear that ipfw doesn't work with bridge in 5.3 and 5.4. The
> > symptoms are that the bridge stops forwarding packets altogether,
> > for me a few minutes
On Wed, 2005-05-04 at 15:24 +0100, Josef Karthauser wrote:
> It appear that ipfw doesn't work with bridge in 5.3 and 5.4. The
> symptoms are that the bridge stops forwarding packets altogether,
> for me a few minutes after it is set up. It takes a
>
> # net.link.ether.bridge_ipfw=0 && sleep 5 &&
On Wed, May 04, 2005 at 06:13:22PM +0100, Gavin Atkinson wrote:
>
> I believe I am seeing similar problems to you, though uptime for me is
> generally measurable in days rather than minutes. I've found that
> adding an explicit "allow all from any to any" and then removing it
> again seems to get
On Mon, 2 May 2005, Sten Spans wrote:
On Mon, 2 May 2005, Maksim Yevmenkin wrote:
Hello,
i think we have few options here:
1) revert back original tapwrite function that was changed in v. 1.48
and set offset to 2 bytes in top mbuf
2) change current version of tapwrite so it would m_prepend and
m
Hello,
i think we have few options here:
1) revert back original tapwrite function that was changed in
v. 1.48 and set offset to 2 bytes in top mbuf
2) change current version of tapwrite so it would m_prepend and
m_pullup mbuf after m_uiotombuf
3) change m_uiotombuf to accept one more parameter
Ragnar Lonn wrote:
Julian Elischer wrote:
Ragnar Lonn wrote:
Hello all,
Does anyone know if virtual network stack support (as implemented at
http://www.tel.fer.hr/zec/vimage/) is on the roadmap for future
FreeBSD releases?
that depends on who you are talking to :-)
the problems are not with th
