ON 5+, you also have to open up the MAC layer FW:
ipfw add allow mac via xl0
If the DHCP server is slow and did not reply back before the
dhclient did continue the boot process, you maybe you do have
to reload the FW rules once your DHCP connection is established.
/Martin
On Fri, 25 Mar 2005 0
Current FreeBSD problem reports
Critical problems
Serious problems
S Submitted Tracker Resp. Description
---
o [2003/04/22] kern/51274 ipfwipfw2 create dynamic rules with parent nu
f [2003/04/24] kern
CORRUPTED MESSAGE
This is the Courier Mail Server 0.48 on fosho.putnamville.com.
I received the following message for delivery to your address. This message
contains several internal formatting errors. This is often caused by
viruses that attempt to infect remote syst
On Monday 04 April 2005 05:06, Martin wrote:
> ON 5+, you also have to open up the MAC layer FW:
> ipfw add allow mac via xl0
>
Hi
where do you guess this from? Shouldn't make any sense if not loading
bridge and enabling bridge firewalling first, overall this would
matter after dhclient asked f
>Submitter-Id: current-users
>Originator:Oleg Bulyzhin <[EMAIL PROTECTED]>
>Organization: Cronyx Plus LLC
>Confidential: no
>Synopsis: dummynet & ipfw tee: kernel may hang (endless loop)
>Severity: serious
>Priority: high
>Category: kern
>Class: sw-bug
>Release:
