From: Matthew X. Economou on
>>>>> "ryanjfarley(a)gmail" == ryanjfarley(a)gmail com <ryanjfarley(a)gmail.com> writes:

ryanjfarley(a)gmail> net.link.bridge.pfil_member: 1
ryanjfarley(a)gmail> net.link.bridge.pfil_bridge: 1
ryanjfarley(a)gmail> net.link.bridge.pfil_onlyip: 1

You've left filtering enabled on your bridge. You can either change
your firewall configuration, or you can disable filtering by setting
the above sysctls to 0.

Best wishes,
Matthew

--
I slashread your textcast about jargon and nodnodnod with your cyber-sentiment.
- gad_zuki! (http://science.slashdot.org/comments.pl?sid=215746&cid=17517040)
From: rfarley on
Thanks for all the follow-ups.

> why not just take a small switch for 20 bucks and let that one do the bridging?

Feel free to let me know if there is better output to describe the
machine's config than what's in the first email.

This falls into the "I need special features the vanilla switch
doesn't give me" issue. I'm a grad student and work in a lab with
mostly VMs. The goal is to build a small plug-and-go device that I can
use for monitoring and manipulating frames in a test environment.

> When you configure your virtual machines you have the opportunity to
> configure networking. Perhaps you should look at vmware help regarding
> networking between boxes. Getting vmware to network realboxes is trivial
> but perhaps there is some extra info required when networking virtual
> boxes. I dunno. never done it myself. Just my 2 cents.

VMware networking settings "shouldn't" be the issue, unless VMware
vmnets handle this situation abnormally. I can successfully use the
same VM (the one named bridge) as a router if the same VMnets are on
different subnets.

> You've left filtering enabled on your bridge.
[root(a)bridge]# sysctl net.link.bridge.pfil_member=0
net.link.bridge.pfil_member: 1 -> 0
[root(a)bridge]# sysctl net.link.bridge.pfil_bridge=0
net.link.bridge.pfil_bridge: 1 -> 0
[root(a)bridge]# sysctl net.link.bridge.pfil_onlyip=0
net.link.bridge.pfil_onlyip: 1 -> 0

No effects. Results same as before.

It seems like there should be a one-liner I forgot to run or some
setting that should be disabled. I'm going to keep plugging away at
this.

Willingly accepting any ideas, thanks,
-Ryan

On Aug 29, 5:20 pm, Christoph Weber-Fahr <we...(a)gmx.de> wrote:
> rfarley wrote:
> > I've since looked into arp-proxy and it unfortunately doesn't work.
>
> I doubted it anyway. You don't need proxy arp, you need a bridge.
>
> > This seems like the most trivial bridge example, I feel dumb.
>
> Can you tell us what you actually configured on your BSD box?
>
> And, just for curiosity's sake - why not just take a small
> switch for 20 bucks and let that one do the bridging? Is this
> a "I want to get this working" thing or a "I need special
> features the vanilla switch doesn't give me" issue?
>
> If the latter, which exactly?
>
> Regards
>
> Christop

From: Matthew X. Economou on
>>>>> "rfarley" == rfarley <ryanjfarley(a)gmail.com> writes:

rfarley> No effects. Results same as before.

rfarley> It seems like there should be a one-liner I forgot to run
rfarley> or some setting that should be disabled. I'm going to
rfarley> keep plugging away at this.

So the computer in question is a VM? You may have to do something
special with the interfaces as presented by VMware, but I'm not
entirely certain.

How are you setting up this bridge: Are you trying to create this
bridge by hand, or are you letting /etc/rc.d/bridge work its magic?
Grep for autobridge in /etc/defaults/rc.conf.

Best wishes,
Matthew

--
I slashread your textcast about jargon and nodnodnod with your cyber-sentiment.
- gad_zuki! (http://science.slashdot.org/comments.pl?sid=215746&cid=17517040)