At 12:11 AM 1/24/2006, you wrote:
Our new code in head allows a bridge group to receive an ip and will
remedy this.
1.0 is not even out and 1.1 is much more fancy. Go figure ;)
not complaining. i'm just puzzled it works on pfsense on not my
sitch. oh well...
Scott
On 1/23/06, Dan
On 1/24/06, Dan Swartzendruber [EMAIL PROTECTED] wrote:
not complaining. i'm just puzzled it works on pfsense on not my
sitch. oh well...
We use if_bridge if pfSense. Is that what you are using?
-
To unsubscribe, e-mail:
Yes, Andrew is investigating this problem. We are seeing some
similar issues as well.
On 1/24/06, Dan Swartzendruber [EMAIL PROTECTED] wrote:
At 09:54 AM 1/24/2006, you wrote:
On 1/24/06, Dan Swartzendruber [EMAIL PROTECTED] wrote:
not complaining. i'm just puzzled it works on pfsense on
At 09:58 AM 1/24/2006, you wrote:
Yes, Andrew is investigating this problem. We are seeing some
similar issues as well.
boy that's a relief. i was noticing that when the wifi card was on
my pfsense box and bridging on, ftp proxy broke. possibly other
weird stuff...
I have also Problems with AppleTalk (EtherTalk) packets on a
ath - sis bridge.
Am 24.01.2006 um 16:47 schrieb Dan Swartzendruber:
At 09:58 AM 1/24/2006, you wrote:
Yes, Andrew is investigating this problem. We are seeing some
similar issues as well.
boy that's a relief. i was noticing
There is a sysctl to work around this:
sysctl net.link.bridge.pfil_onlyip=0
On 1/24/06, Tom Müller-Kortkamp [EMAIL PROTECTED] wrote:
I have also Problems with AppleTalk (EtherTalk) packets on a
ath - sis bridge.
Am 24.01.2006 um 16:47 schrieb Dan Swartzendruber:
At 09:58 AM 1/24/2006, you
At 11:42 AM 1/24/2006, you wrote:
There is a sysctl to work around this:
sysctl net.link.bridge.pfil_onlyip=0
this sysctl did not show up on my freebsd
box. the other pfil ones did. another odd difference?
On 1/24/06, Tom Müller-Kortkamp [EMAIL PROTECTED] wrote:
I have also Problems
Make sure you're freebsd box is on RELENG_6 and up to date.
On 1/24/06, Dan Swartzendruber [EMAIL PROTECTED] wrote:
At 11:42 AM 1/24/2006, you wrote:
There is a sysctl to work around this:
sysctl net.link.bridge.pfil_onlyip=0
this sysctl did not show up on my freebsd
box. the other pfil
At 11:45 AM 1/24/2006, you wrote:
Make sure you're freebsd box is on RELENG_6 and up to date.
it's supposed to be. i've been running cvsup every couple of
weeks. i'll make sure i didn't pooch something. thx!
-
To
If you where up to date, you would have that sysctl :)
Scott
On 1/24/06, Dan Swartzendruber [EMAIL PROTECTED] wrote:
At 11:45 AM 1/24/2006, you wrote:
Make sure you're freebsd box is on RELENG_6 and up to date.
it's supposed to be. i've been running cvsup every couple of
weeks. i'll make
At 11:50 AM 1/24/2006, you wrote:
If you where up to date, you would have that sysctl :)
Maybe I misread something. Here is my cvsup tag:
*default release=cvs tag=RELENG_6_0
Please tell me this is wrong :)
-
To
At 12:00 PM 1/24/2006, you wrote:
That is wrong. I said RELENG_6
On 1/24/06, Dan Swartzendruber [EMAIL PROTECTED] wrote:
At 11:50 AM 1/24/2006, you wrote:
If you where up to date, you would have that sysctl :)
Maybe I misread something. Here is my cvsup tag:
*default release=cvs
That is FreeBSD 6 release. That does not include all the new goodies
in -STABLE.
On 1/24/06, Dan Swartzendruber [EMAIL PROTECTED] wrote:
At 12:00 PM 1/24/2006, you wrote:
That is wrong. I said RELENG_6
On 1/24/06, Dan Swartzendruber [EMAIL PROTECTED] wrote:
At 11:50 AM 1/24/2006, you
At 12:02 PM 1/24/2006, you wrote:
That is FreeBSD 6 release. That does not include all the new goodies
in -STABLE.
i'm wondering if that explains some of the anomalies i saw. i'll
test tonight after doing a make world and make kernel etc...
That is wrong. I said RELENG_6
On 1/24/06, Dan Swartzendruber [EMAIL PROTECTED] wrote:
At 11:50 AM 1/24/2006, you wrote:
If you where up to date, you would have that sysctl :)
Maybe I misread something. Here is my cvsup tag:
*default release=cvs tag=RELENG_6_0
Please tell me this is
At 12:02 PM 1/24/2006, you wrote:
That is FreeBSD 6 release. That does not include all the new goodies
in -STABLE.
that did it! no more loss of connectivity. bless you, my son! :)
-
To unsubscribe, e-mail: [EMAIL
On Jan 24, 2006, at 11:48 AM, Dan Swartzendruber wrote:
At 11:45 AM 1/24/2006, you wrote:
Make sure you're freebsd box is on RELENG_6 and up to date.
it's supposed to be. i've been running cvsup every couple of
weeks. i'll make sure i didn't pooch something. thx!
Make sure to remove
Scott Ullrich wrote:
That is FreeBSD 6 release. That does not include all the new goodies
in -STABLE.
just wanted to add that this is only advisable if you're doing it for
good reason. in this case, you want -STABLE because of the relevant
changes you need for this particular purpose.
On 1/24/06, Chris Buechler [EMAIL PROTECTED] wrote:
just wanted to add that this is only advisable if you're doing it for
good reason. in this case, you want -STABLE because of the relevant
changes you need for this particular purpose.
In all other circumstances, RELENG_6_0 would be your
At 06:53 PM 1/24/2006, you wrote:
Scott Ullrich wrote:
That is FreeBSD 6 release. That does not include all the new goodies
in -STABLE.
just wanted to add that this is only advisable if you're doing it
for good reason. in this case, you want -STABLE because of the
relevant changes you
Pardon the somewhat off-topic post, but I'm at my wits end. I have a
cisco aironet card that was in my pfsense box. I wanted to bridge it
to the LAN, but every time I tried, it would take down the ftp proxy,
so I thought I'd move it to the freebsd 6.0 server. I did
so. Unfortunately,
I got it working, but only by moving the IP address from fxp0 to
bridge0. WTF???
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I've never really tried doing bridging with FreeBSD, but with Linux
that's how bridging is done. For every interface you want to add to
the bridge, you set its IP address to 0.0.0.0. Then, you set the IP
address of the bridge interface and that becomes the bridged IP
address for all the interfaces
At 07:32 PM 1/23/2006, you wrote:
I've never really tried doing bridging with FreeBSD, but with Linux
that's how bridging is done. For every interface you want to add to
the bridge, you set its IP address to 0.0.0.0. Then, you set the IP
address of the bridge interface and that becomes the
I was looking over the bridging example posted earlier, but it wasn't
quite what I was wondering about. Is it possible to bridge an OPT
interface to the WAN interface even though the WAN interface is in a
totally different subnet than the hosts on the OPT interface? My situation:
home DSL
On 10/24/05, Dan Swartzendruber [EMAIL PROTECTED] wrote:
I was looking over the bridging example posted earlier, but it wasn't
quite what I was wondering about. Is it possible to bridge an OPT
interface to the WAN interface even though the WAN interface is in a
totally different subnet than
Subject: [pfSense Support] bridging question
I was looking over the bridging example posted earlier, but it wasn't
quite what I was wondering about. Is it possible to bridge an OPT
interface to the WAN interface even though the WAN interface is in a
totally different subnet than the hosts
work well.
-Original Message-
From: Dan Swartzendruber [mailto:[EMAIL PROTECTED]
Sent: 24 October 2005 23:38
To: support@pfsense.com
Subject: Re: [pfSense Support] bridging question
At 05:49 PM 10/24/2005, you wrote:
Yes, but the shaper won't shape the way you want it to right now
28 matches
Mail list logo
