On Tue, Oct 30, 2012 at 9:29 AM, Kim Culhan <w8hd...@gmail.com> wrote: > On Tue, Oct 30, 2012 at 8:19 AM, Gleb Smirnoff <gleb...@freebsd.org> wrote: >> Kim, >> >> On Mon, Oct 29, 2012 at 05:59:04PM -0400, Kim Culhan wrote: >> K> >> What svn revision of FreeBSD -current are you running? >> K> > >> K> > FreeBSD head r238604. >> K> >> K> I should have mentioned earlier this is with r242126, there have been >> K> some changes >> K> to the network code since 238604, maybe that is why you don't have this >> problem. >> >> If you can do binary search, that may be valuable. >> >> -- >> Totus tuus, Glebius. > > Ok I can begin that process, Monthadar since you have an earlier > version can you try > a test: > > From a machine on one of your 2 interfaces, can you ping a machine on > the other interface? > > Do you see the MAC for a machine on the other interface in the arp table? > > When this problem is present, it is possible to reach the router and > out to the internet > (if it is routed that way) but in the case of the wireless interface, > for example, you cannot > reach a machine on the wired interface. > > The interfaces here:
Sorry omitted one interface: wlan1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 ether fa:d1:11:38:3c:e5 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng <hostap> status: running ssid ap2 channel 6 (2437 MHz 11g ht/40+) bssid fa:d1:11:38:3c:e5 regdomain 32924 country CN indoor ecm authmode OPEN privacy OFF txpower 20 scanvalid 60 protmode CTS ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 1 -kim _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"