Re: vmware changes result in nasty bridging mess

2000-08-08 Thread Vladimir N. Silyaev
On Tue, Aug 08, 2000 at 02:36:02PM +0900, Akinori -Aki- MUSHA wrote: At a quick glance, "start_bridge" doesn't seem to have chance to be 1, does it? It's depend. I'm pretty tired that discussian about bridging. So if people want to use bridge let set start_bridge to 1, if not leave it in

Re: vmware changes result in nasty bridging mess

2000-08-07 Thread Vladimir N. Silyaev
Ok, guys. See in the attachment fix, you should apply it to prevent current behavior. On Sun, Aug 06, 2000 at 07:14:59PM -0400, Robert Watson wrote: On Thu, 3 Aug 2000, Vladimir N. Silyaev wrote: Bridging on by default may have nasty side effects for multi-interface machines (especially

Re: vmware changes result in nasty bridging mess

2000-08-07 Thread Akinori -Aki- MUSHA
At a quick glance, "start_bridge" doesn't seem to have chance to be 1, does it? And, what's the difference among those three values of "bridge"? + bridge="_bridge_on" + bridge="_bridge" + bridge="_bridge_off" -- /

Re: vmware changes result in nasty bridging mess

2000-08-06 Thread Robert Watson
On Thu, 3 Aug 2000, Vladimir N. Silyaev wrote: Bridging on by default may have nasty side effects for multi-interface machines (especially security side effects). It's several ways to work around about that: - compile kernel without bridging support. - remove bridge starting code

Re: vmware changes result in nasty bridging mess

2000-08-06 Thread Kris Kennaway
On Sun, 6 Aug 2000, Robert Watson wrote: Un-announced, the vmware port enabled bridging between the ethernet interfaces on my notebook This is bad - ethernet segments should not be bridged without explicit user confirmation, because they are commonly separated precisely for security reasons.

RE: vmware changes result in nasty bridging mess

2000-08-03 Thread Reinier Bezuidenhout
I'm using vmware2 in a different way ... I do not have bridging enabled in the kernel. I'm using the host method although I do not have a "legal" subnet on the other side. I've ment to contact the port maintainer so he can add this to the Hints.FreeBSD file. I've configured 10.1.1.1 for the

RE: vmware changes result in nasty bridging mess

2000-08-03 Thread Robert Watson
On Thu, 3 Aug 2000, Reinier Bezuidenhout wrote: I'm using vmware2 in a different way ... I do not have bridging enabled in the kernel. I'm using the host method although I do not have a "legal" subnet on the other side. That was the configuration I was using also, until I upgraded my

Re: vmware changes result in nasty bridging mess

2000-08-03 Thread Vladimir N. Silyaev
In muc.lists.freebsd.hackers, you wrote: bridge_in-- reading table bridge_in-- reading table bridge_in-- reading table bridge_in-- reading table bridge_in-- reading table bridge_in-- reading table bridge_in-- reading table bridge_in-- reading table bridge_in-- reading table ... The vmware2 port

vmware changes result in nasty bridging mess

2000-08-02 Thread Robert Watson
bridge_in-- reading table bridge_in-- reading table bridge_in-- reading table bridge_in-- reading table bridge_in-- reading table bridge_in-- reading table bridge_in-- reading table bridge_in-- reading table bridge_in-- reading table ... The vmware2 port now seems to enable bridging by default,