ful use of anchors
and some scripting (or ifstated which might be in ports) can move
traffic off failed links or respond to changing loads.
I've done a lot with both ipfw and PF now, and I'm finding PF to be
more flexible for my uses.
--
Jon Simola
Sys
its already seperated, otherwise it has to figure it out by
looking in the header for the presence of the ETHERTYPE_VLAN tag.
Hope that helps you out.
--
Jon Simola
Systems Administrator
ABC Communications
___
freebsd-net@freebsd.org mailing list
http://li
#x27;m not sure how
polite pcap is about leaving dangling bpf devices.
--
Jon Simola
Systems Administrator
ABC Communications
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
he MAC of my upstream router, stopping my network dead. I have
to become very agressive with layer2 filtering with ipfw to keep the
bridge from seeing packets on the wrong interface.
--
Jon Simola
Systems Administrator
ABC Communications
___
freebsd-net@f
0).
> >>[EMAIL PROTECTED]:~$ sysctl -a | grep kern.polling
> >>kern.polling.handlers: 0
No handlers? On all my boxes I've got one handler per polled device.
--
Jon Simola
Systems Administrator
ABC Communications
___
freebsd-net
> > On Sunday 13 February 2005 22:36, David Gilbert wrote:
> >> Has anyone considered patching the vlan driver to support altq? I
> >> gather that since tun works, so should vlan.
>
> Well... the issue is several fold. Firstly, the router in question is
> talking in trunk mode to a switch which i
On Thu, 3 Feb 2005 12:18:05 -0500, Michael W. Oliver
<[EMAIL PROTECTED]> wrote:
> subject sums it up. will be used in small firewall boxes with WAN, LAN,
> DMZ, and WLAN (via x-over to AP) connections. older hardware, so
> please, no fancy super-duper mega-bandwidth PCI cards that I won't have
>
mp on either em1 or one of the vlan interfaces reduces
throughput by a factor of 10 or so. Running tcpdump with the -p option
does not.
This is a steady stream of 10 to 20 Mbps of traffic, routing 11 /24s
over 4 vlans, kernel polling is enabled for the em devices.
Thank you,
Jon Simola
Systems Administ
On Wed, 19 Jan 2005 13:01:52 -0800, Charlie Schluting
<[EMAIL PROTECTED]> wrote:
> Now, in 5.3, the only thing I can get working is to configure the em0 int with
> the IP, and set the trunk to have the native vlan corresponding to that IP.
> Weird.
Sounds like you're not getting the module loade
On Mon, 17 Jan 2005 23:07:54 +0100, Andrew Seguin <[EMAIL PROTECTED]> wrote:
> With the help, in pointing out the mask feature to me from Jon Simola, this
> quite possibly might be the path I'll take (I'll sleep on it first).
> Interfaces are 100Mbps, but our interne
On Mon, 17 Jan 2005 22:41:16 +0100, Andrew Seguin <[EMAIL PROTECTED]> wrote:
> >What I was doing with the same setup:
> >$IPFW pipe 1 config mask src-ip 0x buckets 512
> >$IPFW pipe 2 config mask dst-ip 0x buckets 512
> >$IPFW add 32001 pipe 1 src-ip 192.168.110.0/24 bridged
> >$IP
On Mon, 17 Jan 2005 21:11:13 +0100, Andrew Seguin <[EMAIL PROTECTED]> wrote:
> But, here's my situation. A dedicated FreeBSD transparent firewall-bridge
> with 3 NICs (two for the bridge w/o IP, one for console). I'm using IPFW for
> the firewall, and at the moment I'm doing some very bare-bones s
OCK(&ifp->if_snd);
+ }
+
ifv = ifp->if_softc;
p = ifv->ifv_p;
ifp->if_flags |= IFF_OACTIVE;
for (;;) {
- IF_DEQUEUE(&ifp->if_snd, m);
+ IFQ_DEQUEUE(&ifp->if_snd, m);
if (m == 0)
13 matches
Mail list logo