hi,
thanks, good finding!
it looks right, but i have to re-think the promisc handling of trunk a
bit to see if we
a) either inherit the promisc flag on the trunk device directly which
means that trunks would always be promisc (sounds bad...).
b) find a way to use trunk without enforcing the por
* LeviaComm Networks NOC [2010-06-15 08:07]:
> On 6/13/2010 9:50 PM, Patrick Coleman wrote:
> >For some reason however, on one particular VLAN the switch is
> >erroneously forwarding traffic from a particular host (203.135.184.10)
> >to the OpenBSD box. The traffic is forwarded even when the desti
On Wed, Jun 16, 2010 at 04:33:42PM +0800, Patrick Coleman wrote:
> On Wed, Jun 16, 2010 at 4:28 PM, David Coppa wrote:
> >
> > diff -u is preferred. Can you resend it in unified format?
>
> Sure. See http://patrick.ld.net.au/20100616-fix-gratuitous-reset.patch.
And, not to nitpick, but I'm going
On Wed, Jun 16, 2010 at 4:28 PM, David Coppa wrote:
>
> diff -u is preferred. Can you resend it in unified format?
Sure. See http://patrick.ld.net.au/20100616-fix-gratuitous-reset.patch.
Cheers,
Patrick
--
http://www.labyrinthdata.net.au - WA Backup, Web and VPS Hosting
On Wed, Jun 16, 2010 at 10:17 AM, Patrick Coleman wrote:
> Index: if_ethersubr.c
> ===
> RCS file: /cvs/src/sys/net/if_ethersubr.c,v
> retrieving revision 1.139
> diff if_ethersubr.c
> 540a541
>> struct ifnet *ifp_orig = ifp0;
On Tue, Jun 15, 2010 at 2:16 PM, LeviaComm Networks NOC
wrote:
>
> OpenBSD may be running the network in promiscuous mode, which would be why
> it is responding to MACs that it shouldn't. If you aren't running a clean
> installation, I would recommend turning off everything except routed,
> inclu
On 6/15/2010 5:02 AM, Bryan Vyhmeister wrote:
On Tue, Jun 15, 2010 at 7:10 AM, Stuart Henderson
wrote:
On 2010-06-15, LeviaComm Networks NOC wrote:
One last thing, Is there a reason that you are doing a router-on-a-stick
configuration? I ask only because they tend to cause more headaches
then
On Tue, Jun 15, 2010 at 7:10 AM, Stuart Henderson
wrote:
> On 2010-06-15, LeviaComm Networks NOC wrote:
>> One last thing, Is there a reason that you are doing a router-on-a-stick
>> configuration? I ask only because they tend to cause more headaches
>> then they are worth, as Gigabit NICs are p
On 2010-06-15, LeviaComm Networks NOC wrote:
> One last thing, Is there a reason that you are doing a router-on-a-stick
> configuration? I ask only because they tend to cause more headaches
> then they are worth, as Gigabit NICs are pretty much a dime-a-dozen
> nowadays.
I dispute this. I've
On Tue, Jun 15, 2010 at 2:16 PM, LeviaComm Networks NOC
wrote:
>
> I just wanted to eliminate as much as possible before spending too much
time
> on the problem. I have a few questions about your setup:
No problem.
> How is your switch configured? Is this the only switch?
It's a stack of six
On 6/14/2010 10:20 PM, Patrick Coleman wrote:
On Tue, Jun 15, 2010 at 1:03 PM, LeviaComm Networks NOC
wrote:
It would be best if you had a working switch to test with, the switch may be
forwarding packets to the OpenBSD box because its MAC table is broken. The
switch may be the cause, please
On 6/13/2010 9:50 PM, Patrick Coleman wrote:
For some reason however, on one particular VLAN the switch is
erroneously forwarding traffic from a particular host (203.135.184.10)
to the OpenBSD box. The traffic is forwarded even when the destination
MAC address is not that of the OpenBSD box. So t
On Mon, Jun 14, 2010 at 10:20 PM, Patrick Coleman wrote:
> On Tue, Jun 15, 2010 at 1:03 PM, LeviaComm Networks NOC
> wrote:
>> It would be best if you had a working switch to test with, the switch may
> be
>> forwarding packets to the OpenBSD box because its MAC table is broken.
The
>> switch ma
On Tue, Jun 15, 2010 at 1:03 PM, LeviaComm Networks NOC
wrote:
> It would be best if you had a working switch to test with, the switch may
be
> forwarding packets to the OpenBSD box because its MAC table is broken. The
> switch may be the cause, please confirm that it isn't before making noise.
>
On Mon, Jun 14, 2010 at 11:23 PM, Ted Unangst wrote:
>> In my pf.conf I have "match in all scrub (reassemble tcp)" and
>> "antispoof log for $interfaces" and nothing else that isn't a simple
>> pass/block or NAT rule. I'm not ruling out some sort of config error
>> here, because I'm pretty new to
On Mon, Jun 14, 2010 at 12:50 AM, Patrick Coleman wrote:
> The strange thing is that occasionally, the OpenBSD box will reply to
> the gratuitous traffic with a spoofed TCP RST. For example, see [1] -
> a TCP connection was initiated from 203.135.184.10 (an OSX server) to
> 203.135.184.6 (a Linux
Hi,
I've got an interesting problem that I'd really appreciate some input
on. I am in the process of migrating our Linux router-on-a-stick to an
OpenBSD router, and have configured an OpenBSD 4.7 (GENERIC) box with
an IP on each VLAN. At present, no devices are configured to use the
OpenBSD box as
17 matches
Mail list logo