On Wed, Jan 23, 2019 at 08:40:39PM +, Rick Macklem wrote:
> Well, there is a reason why NFSv4 (published in an RFC in 2003) does
> not use the Mount protocol or rpcbind.
> Those protocols were defined decades ago by a company that no longer
> exists.
I understand that. :-)
> If you took a
Hi there,
I've recently encountered a problem that my NFS box was not directly
accessible to one of its clients. I've forwarded TCP ports for the
rpcbind(8), mountd(8), and nfsd(8) with ssh(1), but mount_nfs(8) did
not work, that is, with -o tcp,proto=tcp.
Running it under truss(1) revealed
On Thu, Oct 04, 2018 at 11:38:46AM -0600, Warner Losh wrote:
> ...
> I'd also suggest that rl stands in stark contrast to the cs, wb, sn, smc,
> sf, tl, tx and vr drivers, which nobody has mentioned in this thread, and
> which I doubt are in use in any FreeBSD system of any age today.
Warner, I
On Thu, Oct 04, 2018 at 08:43:33AM -0600, Warner Losh wrote:
> As far as I know, none of the drivers listed could do 1Gbps.
Right. My point was that original proposal put 10/100 drivers into one
basket, which is IMHO not fair: 10Mbps cards are rarely seen and used,
100mbps are not, just like
On Thu, Oct 04, 2018 at 02:26:44PM +, Mark Linimon wrote:
> On Thu, Oct 04, 2018 at 08:44:11AM +0000, Alexey Dokuchaev wrote:
> > OK I guess I can understand removing 10 (I personally haven't seen
> > one in a very long time) but 100 are omnipresent and most of my NICs
>
On Wed, Oct 03, 2018 at 09:05:16PM +, Brooks Davis wrote:
> FCP-01010 (https://github.com/freebsd/fcp/blob/master/fcp-0101.md)
> outlines a plan to deprecate most 10/100 Ethernet drivers in FreeBSD 12
Holy shit! OK I guess I can understand removing 10 (I personally haven't
seen one in a very
On Tue, Apr 17, 2018 at 12:54:59PM +, Andrew Gallatin wrote:
> New Revision: 332645
> URL: https://svnweb.freebsd.org/changeset/base/332645
>
> Log:
> Make lagg creation more fault tolerant
>
> - Warn, don't exit, when SIOCSLAGGPORT returns an error.
>
> When we exit with an error
On Wed, Oct 20, 2010 at 07:15:19PM +0200, Bernhard Schmidt wrote:
# kldload if_iwi
# aireplay-ng -9 iwi0
# ifconfig iwi0
iwi0: flags=28943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,PPROMISC
metric 0 mtu 1500
media: IEEE 802.11 Wireless Ethernet autoselect (autoselect monitor)
#
On Tue, Oct 19, 2010 Bernhard Schmidt wrote:
Alexey Dokuchaev da...@freebsd.org wrote:
Not sure if this is a driver or ifconfig(8) problem, but after I -mediaopt
monitor, ifconfig(8) still reports it in media line:
media: IEEE 802.11 Wireless Ethernet autoselect monitor
However
On Sun, Oct 10, 2010 at 07:27:30AM +, Alexey Dokuchaev wrote:
On Sat, Oct 09, 2010 at 08:46:41PM +0200, Bernhard Schmidt wrote:
On Saturday 09 October 2010 08:02:39 Alexey Dokuchaev wrote:
Much better! airodump-ng iwi0 now sees stations in addition to APs,
which means it can utilize
On Sat, Oct 09, 2010 at 08:46:41PM +0200, Bernhard Schmidt wrote:
On Saturday 09 October 2010 08:02:39 Alexey Dokuchaev wrote:
Much better! airodump-ng iwi0 now sees stations in addition to APs,
which means it can utilize monitor mode. ifconfig iwi0 scan however
does not work after
On Fri, Oct 08, 2010 at 07:44:50PM +0200, Bernhard Schmidt wrote:
On Friday 08 October 2010 19:36:13 Bernhard Schmidt wrote:
After having another cup of coffee it's pretty obvious what's wrong.
The only difference between what I did and your scenario is, that I
didn't use
ifconfig iwi0
On Fri, Oct 08, 2010 at 06:07:31PM +, Paul B Mahol wrote:
Just to clear this up, iwi(4) can not support injection (see iwi_raw_xmit())
unless you manage to hack firmware ...
Can you perhaps comment on this thread:
http://ubuntuforums.org/showthread.php?t=242556
At a glance it
On Fri, Oct 08, 2010 at 11:48:57AM +, Paul B Mahol wrote:
On 10/8/10, Alexey Dokuchaev da...@freebsd.org wrote:
On Thu, Oct 07, 2010 at 12:44:20PM +, Paul B Mahol wrote:
Monitor and injection work commpletly different after vap.
I do not think that kismet and aircrack-ng from
On Thu, Oct 07, 2010 at 08:43:37PM +0200, Bernhard Schmidt wrote:
Try the attached patch, this is basically the code from stable/6
ported to head and stable/7. I did only some basic tests but monitor
mode seems to work and it is still possible to use the card in STA
mode.
I'm not sure why
On Fri, Oct 08, 2010 at 03:15:45PM +, Paul B Mahol wrote:
On 10/8/10, Alexey Dokuchaev da...@freebsd.org wrote:
I am also not sure about AHDEMO mode, since iwi(4) reports this for me:
$ ifconfig iwi0 list caps
iwi0=25818300IBSS,PMGT,SHPREAMBLE,MONITOR,WPA1,WPA2,WME,BGSCAN
I'm
On Fri, Oct 08, 2010 at 03:47:04PM +0200, Bernhard Schmidt wrote:
On Friday, October 08, 2010 15:18:50 you wrote:
On Thu, Oct 07, 2010 at 08:43:37PM +0200, Bernhard Schmidt wrote:
Try the attached patch, this is basically the code from stable/6
ported to head and stable/7. I did only some
On Fri, Oct 08, 2010 at 03:20:08PM +, Paul B Mahol wrote:
On 10/8/10, Alexey Dokuchaev da...@freebsd.org wrote:
On Thu, Oct 07, 2010 at 08:43:37PM +0200, Bernhard Schmidt wrote:
Try the attached patch, this is basically the code from stable/6
ported to head and stable/7. I did only some
On Wed, Oct 06, 2010 at 11:56:25AM -0500, Brandon Gooch wrote:
2010/10/6 Alexey Dokuchaev da...@freebsd.org:
On Fri, Dec 14, 2007 at 11:19:25PM +0100, Jan Henrik Sylvester wrote:
In contrast to 6.2-RELEASE, monitor mode does not work. Kismet does
not receive anything, while it does with ath
On Fri, Dec 14, 2007 at 11:19:25PM +0100, Jan Henrik Sylvester wrote:
In contrast to 6.2-RELEASE, monitor mode does not work. Kismet does
not receive anything, while it does with ath or ural (even at the same
time). dmesg with debug.iwi=2 is below -- anything unusual?
Moreover, ifconfig
20 matches
Mail list logo
