text: Title: DHCP failure in Local Redirect mode (Windows)
  Body: #### Problem Description
  I've been experimenting with local redirect mode on a Windows 11 AWS machine, and noticed the machine loses all connectivity after mitmdump has been running for a while (could take up to an hour).
  In order to debug this issue I've set both proxy_debug=true & termlog_verbosity=debug, and noticed at the end of the log when the machine loses all network capabilities, there are several DHCP broadcasts (UDP ports 67 & 68) that looks like this:
  
  `*:68 -> udp -> 255.255.255.255:67`
  
  After observing this, I'm thinking WinDivert might be having some issues with re-injecting broadcast packets.
  
  I also found the following issue that could be relevant: https://github.com/basil00/Divert/issues/320
  
  I recompiled the windows-redirector binary with a modified filter (could be a nice feature flag to customize the WinDivert filter with an argument), and it seemed that the problem ceased when the filter (on WinDivert) was set to exclude broadcasts.
  
  I can open a PR for this if you think the fix is appropriate but it's pretty straight forward, I changed these 2 filters:
  
  https://github.com/mitmproxy/mitmproxy_rs/blob/c30c9d8ffc41a453670a27909b2cb0d97abbbb81/mitmproxy-windows/redirector/src/main2.rs#L112
  
  https://github.com/mitmproxy/mitmproxy_rs/blob/c30c9d8ffc41a453670a27909b2cb0d97abbbb81/mitmproxy-windows/redirector/src/main2.rs#L117
  
  
  From "tcp || udp" to "remoteAddr != 255.255.255.255 && (tcp || udp)"
  
  #### Steps to reproduce the behavior:
  1. Start up a Windows EC2 instance on AWS
  2. Let mitmdump run for a while in local redirect mode
  3. Wait for machine to lose connection (eg. RDP session will disconnect and no further connections will be possible)
  
  #### System Information
  EC2 instance on AWS
  Mitmproxy: 10.3.0 binary
  Python:    3.12.3
  OpenSSL:   OpenSSL 3.2.1 30 Jan 2024
  Platform:  Windows-11-10.0.22631-SP0
  