[ previous ] [ next ] [ threads ]
 
 From:  Joey Morin <joeymorin at gmail dot com>
 To:  Chris Buechler <cbuechler at gmail dot com>
 Cc:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] ath, bridge, and dhcp... am i missing something?
 Date:  Thu, 3 Sep 2009 05:10:12 -0400
hi chris, thanks for your quick reply.

On Thu, Sep 3, 2009 at 1:36 AM, Chris Buechler <cbuechler at gmail dot com> wrote:

>
> Does it work if you put a static IP on the client?
>

yup


> Also, browse to exec.php and run ifconfig, paste the output here or
> email it to me.
>

rl0 is my lan

$ ifconfig -a
xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=9<RXCSUM,VLAN_MTU>
	inet6 fe80::210:4bff:fe09:7da4%xl0 prefixlen 64 scopeid 0x1
	ether 00:10:4b:09:7d:a4
	media: Ethernet autoselect (10baseT/UTP)
	status: active
rl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=8<VLAN_MTU>
	inet 192.168.58.1 netmask 0xffffff00 broadcast 192.168.58.255
	inet6 fe80::250:fcff:fe2a:d79b%rl0 prefixlen 64 scopeid 0x2
	ether 00:50:fc:2a:d7:9b
	media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
ath0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	inet6 fe80::21d:6aff:fe13:1f17%ath0 prefixlen 64 scopeid 0x3
	ether 00:1d:6a:13:1f:17
	media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>
	status: associated
	ssid xxxxxxxx channel 2 bssid 00:1d:6a:13:1f:17
	authmode WPA2/802.11i privacy MIXED deftxkey 3 AES-CCM 2:128-bit
	AES-CCM 3:128-bit txpowmax 36 bmiss 7 protmode CTS burst dtimperiod 1
	bintval 100
enc0: flags=41<UP,RUNNING> mtu 1536
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	inet 127.0.0.1 netmask 0xff000000
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
ng0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> mtu 1492
	inet6 fe80::210:4bff:fe09:7da4%ng0 prefixlen 64 scopeid 0x6
	inet 65.95.56.122 --> 64.230.197.203 netmask 0xffffffff
ng1: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
	inet6 fe80::210:4bff:fe09:7da4%ng1 prefixlen 64 scopeid 0x7
ng2: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
	inet6 fe80::210:4bff:fe09:7da4%ng2 prefixlen 64 scopeid 0x8
ng3: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
ng4: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
ng5: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
ng6: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
ng7: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
ng8: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
ng9: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
ng10: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
ng11: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
ng12: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
ng13: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
ng14: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
ng15: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500
ng16: flags=8890<POINTOPOINT,NOARP,SIMPLEX,MULTICAST> mtu 1500



> There may be an issue with wireless bridging, there is part of the
> code in pfSense that I didn't pull over in the wireless portion
> related to bridging, but I don't think it affects 6.x so possibly not
> an issue here. if_bridge doesn't like differing MTUs, but I think the
> ath default changed to 2290 in 7.x, is 1500 in 6.x.
>

ath0 has an mtu of 1500.  there are some other interfaces i don't know
anything about, some have odd mtu, enc0 has 1536, ng0 has 1492.  does this
mean anything?

cheers,
jj