Hi all,
Max was on to something when he wrote:
"Furthermore, remember that the OP can move to another NIC and the problem
goes away[1]. I know there have been issues in the past reported with em(4)
and pf ALTQ, but that isn't in use here."
In fact, when I was testing possible firewall
81:6999 flags
S/SA synproxy state
pass in on $ext_if inet proto tcp from any to $nat_opt port 993 flags S/SA
synproxy state
pass in quick on $int_if
pass in quick on $wifi_if
Many thanks,
Dave
On Mon, Jul 5, 2010 at 5:49 PM, David Warren wrote:
> Hi all,
>
> As several peo
0 19 1 78
Many thanks for all the ideas, and I'll report back after a bit more
testing.
Dave
On Mon, Jul 5, 2010 at 12:51 AM, Jeremy Chadwick
wrote:
> On Sun, Jul 04, 2010 at 07:52:11PM -0500, David Warren wrote:
> > I've got a persistent problem with my LAN. I'
Hi Doug,
I tried a binary update to 8.1 RC2, and then rebuilt all ports.
Unfortunately, I'm still experiencing the same problem. Any thoughts on
troubleshooting this? Thanks,
Dave
On Sun, Jul 4, 2010 at 8:40 PM, Doug Barton wrote:
> On Sun, 4 Jul 2010, David Warren wrote:
>
Hi all,
I've got a persistent problem with my LAN. I'm running a FreeBSD 8.0
box as a home server performing the following functions for wired and
wireless networks: router; firewall; DHCP server; and file server. For what
it's worth, I've got ZFS up and running as the main filesystem. The
Bartosz Fabianowski wrote:
the same device that FreeBSD used to identify as "IPOD" is now
identified as "Rockbox"
The Rockbox USB code keeps changing with each build - it used to
request power (using its own USB stack) until very recently for me,
but as of a couple of days ago, reboots into t
Just wanted to correct an error in my original note; I intended to
suggest that a change in Rockbox had caused this problem, not rsync.
Bartosz picked up on that immediately. Regarding your note, I think
that the Rockbox USB stack may in fact be running by default in the
newest releases.
