sorry, neglected to include /etc/ipfw.rules
# egrep -v '^(#|$)' /etc/ipfw.rules
flush
add deny log all from any to any ipoptions ssrr,lsrr,rr
add pass tcp from me to 666.42.0.62 smtp
add deny log tcp from any to any smtp
add deny all from any to me auth
nat 42 config if vr0 log
add nat 42 ip4 from
On Thu, 13 Dec 2007, Randy Bush wrote:
> ok, i have bridging working (kernel/userland version skew likely culprit,
> thanks max),
> except that ath0 does not seem to completely bridge. bms may have warned me
> in saying
>
> > although you won't get the 802.11 frames bridged.
I'm wondering
ok, i have bridging working (kernel/userland version skew likely culprit,
thanks max),
except that ath0 does not seem to completely bridge. bms may have warned me in
saying
> although you won't get the 802.11 frames bridged.
---
the problem:
o hosts on vr1, vr2, and vr3 get dhcp addresses an
> 3) Most likely candidate: Your userland and kernel are out of sync. Try
> to rebuild ifconfig with the same headers installed as your kernel was
> built.
rebuilt all to current cvsup of current. can now bridge. on to trying
to make the ath happy with the bridge.
randy
___
On Wednesday 12 December 2007, Randy Bush wrote:
> the symptom
>
> # ifconfig bridge0 192.168.0.1 addm vr1 addm vr2 addm vr3 addm ath0 up
> ifconfig: BRDGADD vr1: Invalid argument
EINVAL can be returned from BRDGADD for three reasons:
1) The MTU on the member interfaces don't match (the first mem
> My last shot in the dark before They Who Know if_bridge get back from
> the nightclub .. Randy, just to rule ath in or out as prime suspect,
> does it come up right if you only specify the vr interfaces?
no
randy
___
freebsd-net@freebsd.org mailing li
On Wed, 12 Dec 2007, Bruce M. Simpson wrote:
> My shot from the hip, although I'm pretty much away from this stuff at
> the moment.
>
> Randy Bush wrote:
> > # ifconfig bridge0 addm ath0 addm vr1 up
> > ifconfig: BRDGADD ath0: Invalid argument
> >
> ath0 is IFT_ETHER, so it should be O
My shot from the hip, although I'm pretty much away from this stuff at
the moment.
Randy Bush wrote:
# ifconfig bridge0 addm ath0 addm vr1 up
ifconfig: BRDGADD ath0: Invalid argument
ath0 is IFT_ETHER, so it should be OK to attach it to the bridge --
although you won't
get the 802.11 frame
On Wed, 12 Dec 2007, Randy Bush wrote:
> > Ah. Well the only other thing i noticed (after posting) was that each
> > of vr1 to vr3 showed as UP, but:
> >> media: Ethernet autoselect (none)
> >> status: no carrier
> > but I don't know whether that should matter?
>
> man page
> Ah. Well the only other thing i noticed (after posting) was that each
> of vr1 to vr3 showed as UP, but:
>> media: Ethernet autoselect (none)
>> status: no carrier
> but I don't know whether that should matter?
man page says not. and if i put ath0 first, which has
carrier/assoc
On Wed, 12 Dec 2007, Randy Bush wrote:
> > did you start off with?
> >
> > # ifconfig bridge create
> >
> > when your ifconfig -a should then also show:
> >
> > bridge0: flags=8802 metric 0 mtu 1500
> > (etc)
> >
> > though it looks like 'cloned_interfaces=bridge0' is supposed to
> did you start off with?
>
> # ifconfig bridge create
>
> when your ifconfig -a should then also show:
>
> bridge0: flags=8802 metric 0 mtu 1500
> (etc)
>
> though it looks like 'cloned_interfaces=bridge0' is supposed to do that.
>
> cheers, Ian
sorry, cut and paste error with screen.
On Wed, 12 Dec 2007, Randy Bush wrote:
> the symptom
>
> # ifconfig bridge0 192.168.0.1 addm vr1 addm vr2 addm vr3 addm ath0 up
> ifconfig: BRDGADD vr1: Invalid argument
>
> the conditions
>
> # kldstat
> Id Refs AddressSize Name
> 13 0xc040 39ad48 kernel
> 21 0
13 matches
Mail list logo
