Hi guys.
When you ifconfig athX channel XX it works fine
But when you then want to change that to ifconfig athX channel any (or '-' or
'0') the old channel number does not change.
The number then can be changed only to a different numeric value.
Cheers,
Marcin Jessa
_
> Currently I am going through netstat and
> rewriting some of the functions to rely on sysctl rather than kvm.
> The hope is to completely remove kvm from netstat, and parts that
> solely depend on it, like the core dump analysis would be factored
> out and moved to a more suitable place (
Hello,
Suppose I have three daemons, who grab all the packets which are
forwarded to their addresses via different vlans
fwd 10.104.50.2,9998 tcp from any to any dst-port 80 in recv vlan0
fwd 10.104.50.6,9998 tcp from any to any dst-port 80 in recv vlan1
fwd 10.104.50.10,9998 tcp from any to any
On Tue, 12 Jul 2005, Ed Maste wrote:
On Tue, Jul 12, 2005 at 04:30:18PM +0100, Robert Watson wrote:
I'm concerned about the multicast address list problems you've been
experiencing, but haven't yet had a chance to investigate. If you could
provide a code fragment that exercises this problem,
On Sat, 23 Jul 2005, Robert Watson wrote:
The attached patch introduces locking around the link layer and IPv4
multicast address lists, as well as updates drivers to use the locking.
It's a fairly large diff, but other than the changes to if.c, in.c, and
igmp.c, is fairly mechanical. It may
I believe the solution is not patching ALTQ to the VLAN driver, but
rather make ALTQ recognize rules that classify according to fields in
Layer 2 header (fields such as VLANid and Priority, other than just
src/dst addr/port and protocol in IP header). For example, build
filter rules
Anders Persson wrote:
Hi all,
I have not had time to go through netgraph enough yet, but does
anyone have some ideas how to avoid using kvm to obtain netgraph info?
what info do you want to get that isn't already avaliable?
Thanks a lot,
Anders
__
