On Fri, Jan 11, 2002 at 07:53:08AM -0800, CJTT wrote:
>
> (using the ti and and also the bge drivers)
> with 4.5-PRERELEASE (cvs'upped two days ago), I've now lost
> the ability to see the VLAN traffic on the main interface
> (even with no VLAN in the kernel!)...so once again,
> I've lost tha
Is there a way to see entire VLAN packets with
netgraph even if the driver has stripped off
the VLAN info? (examples or pointers would be
appreciated)...
Thanks
On Fri, 11 Jan 2002, CJTT wrote:
>
> (using the ti and and also the bge drivers)
> with 4.5-PRERELEASE (cvs'upped two days ago)
(using the ti and and also the bge drivers)
with 4.5-PRERELEASE (cvs'upped two days ago), I've now lost
the ability to see the VLAN traffic on the main interface
(even with no VLAN in the kernel!)...so once again,
I've lost that loving feeling ;-(
Is there anything I can do in stable that wi
On Wed, Dec 12, 2001 at 03:15:58PM -0500, Sam Tannous wrote:
> On Thu, Nov 15, 2001 at 01:42:07PM -0800, Brooks Davis wrote:
> > On Thu, Nov 15, 2001 at 03:41:21PM -0600, Shaun Marko wrote:
> > > Could you also get the desired result by using a kernel without
> > > VLAN support?
> > > The origina
On Thu, Nov 15, 2001 at 01:42:07PM -0800, Brooks Davis wrote:
> On Thu, Nov 15, 2001 at 03:41:21PM -0600, Shaun Marko wrote:
> > Could you also get the desired result by using a kernel without
> > VLAN support?
> > The original poster said he didn't want to configure VLAN interfaces
> > anyway.
On Fri, Nov 16, 2001 at 06:27:25AM -0800, CJTT wrote:
> (I'll temporarily remove the VLAN support from the kernel).
> But when this is MFC'd, what will I need to do in order to
> continue seeing all traffic on the main interface
> (while using libpcap (tcpdump))?
>
> Will the VLAN_INPUT_TAG ma
On Thu, 15 Nov 2001, Brooks Davis wrote:
> For the moment, on stable hosts, that will work. Driver vlan support is
> no longer optional in current and that change will be MFC'd just as soon
> as I get it tested. The right answer is probably to modify the
> VLAN_INPUT_TAG macro to do the bpf stuf
On Thu, Nov 15, 2001 at 02:04:07PM -0800, CJTT wrote:
> I see what you're talking about in the driver (if_ti.c).
> But I'm not sure if I understand you correctly
> (I can't seem to find where the VLAN_INPUT_TAG macro
> is located). Would a temporary fix in if_ti.c
> be to just remove the vlan_inp
On Thu, 15 Nov 2001, Brooks Davis wrote:
> On Thu, Nov 15, 2001 at 03:41:21PM -0600, Shaun Marko wrote:
> > Could you also get the desired result by using a kernel without VLAN support?
> > The original poster said he didn't want to configure VLAN interfaces anyway.
>
> For the moment, on stable
On Thu, Nov 15, 2001 at 03:41:21PM -0600, Shaun Marko wrote:
> Could you also get the desired result by using a kernel without VLAN support?
> The original poster said he didn't want to configure VLAN interfaces anyway.
For the moment, on stable hosts, that will work. Driver vlan support is
no
Could you also get the desired result by using a kernel without VLAN support?
The original poster said he didn't want to configure VLAN interfaces anyway.
-Shaun
On Thursday 15 November 2001 03:22, Brooks Davis wrote:
> On Thu, Nov 15, 2001 at 12:53:35PM -0800, CJTT wrote:
> > While sending some
While sending some test traffic to a
FreeBSD 4.4 (cvsupped yesterday), I noticed
that tcpdump doesn't seem to see VLAN traffic
received on the ti card as it does on the fxp card.
(however, tcpdump on the sending ti card
sees the traffic leave).
tcpdump with non-VLAN traffic on receive side:
12 matches
Mail list logo
