for
given addr/mask
bad exports list line '/mnt/v4share -network 10.101.0 -mask 255.255.255.0'
--
Best regards
Alexander Lunev
_______
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send
/NFS -maproot=root -sec=krb5i
V4: /NFS -sec=krb5i
and this work ok for nfsv4 mount (mount -t nfsv4 host:/)
May be order is important?
I've already tried in any order, it doesn't change anything.
In another place (11.2-R) i've already done NFSv4 mount where ubuntu
mounts sha
In another place (11.2-R) i've already done NFSv4 mount where ubuntu mounts
share from freebsd via nfsv4 with sec=sys without any problem, but here (11.3)
i can't make it work - maybe the reason is that client is diskless and root
mounted by NFSv3 from the same server?
Are the d
0.1:/ /mnt
and NOT
# mount_nfs -o nfsvers=4 10.101.0.1:/ /mnt
With mount_nfs -o nfsv4 share is mounted OK.
--
Best regards
Alexander Lunev
_______
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, s
mount won't work, because the gssd must be running for
Kerberos access to work and that can't happen until booted.
And thanks for this! I think you saved me a lot of time figuring how and
why!
--
Best regards
Alexander Lunev
_______
freebsd
uname -a
FreeBSD talos 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r351820M: Wed Sep 4
23:37:46 CEST 2019 root@talos:/usr/obj/usr/src/powerpc.powerpc64/sys/ZFS
powerpc
My kernel:
pkubaj@talos:$/usr/home/pkubaj$ cat /usr/src/sys/powerpc/conf/ZFS
include GENERIC64
options GEOM_ELI
options ZFS
sign
ebsd.org/D21582
--
Randall Stewart
r...@netflix.com
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
nce wrote:
>
> Thanks Randall.
> I was able to apply the patch - now rebuilding the kernel. Would update on
> how it goes.
>
> BTW, is there any description on how lack of tc_fq under FreeBSD is
> compensated here?
> The original BBR patches on Linux show t
fq.. they built an alternate means of doing pacing into bbr.
>
> In either case our testing has shown that our pacing is more accurate than
> either fq or the internal pacer :)
>
> R
>
> > On Sep 17, 2019, at 11:05 AM, vm finance wrote:
> >
> > Thanks Randall.
&g
gt; *** Error code 1
>>
>> Stop.
>> make[1]: stopped in /usr/src
>> *** Error code 1
>>
>> Stop.
>> make: stopped in /usr/src
>>
>>
>> On Tue, Sep 17, 2019 at 6:27 PM Randall Stewart wrote:
>> Pacing is provided by tcp
m -f .depend .depend.* GPATH GRTAGS GSYMS GTAGS
>>> ===> sys (cleandir)
>>> rm -f export_syms machine x86 tcp_bbr.ko tcp_bbr.kld bbr.o sack_filter.o
>>> rack_bbr_common.o opt_inet.h opt_inet6.h opt_ipsec.h opt_tcpdebug.h
>>> opt_kern_tls.h
>>> rm:
019, at 7:26 PM, vm finance wrote:
>
> Hi Randall,
>
> Could you please provide a pointer to the latest patch. I had applied the one
> you published Sep-10.
>
> Following is what I have done:
> 1. Picked FreeBSD 12.0 RELEASE VM from osboxes.org
> 2. Got VM up un
ease 12.0 will *not* have these patches and will *not* compile it.
>>>
>>> I have no intention at this point in doing a MFC of this work.. so if you
>>> want
>>> to run BBR you need to run Head
>>>
>>> R
>>>
>>> On Sep 17, 2019, at 7:26
56 AM, Randall Stewart wrote:
>>>>
>>>> There have been several patches pre-this one that provide
>>>> the infrastructure to support BBR.
>>>>
>>>> Release 12.0 will *not* have these patches and will *not* compile it.
>>>>
>>&
I should be making any changes in configs, please do let me
> know.
> My goal is to build a freebsd image with BBR patches on x86 VM.
> Nothing fancy.
>
> thanks!
>
> On Wed, Sep 18, 2019 at 7:03 AM vm finance wrote:
> Thanks Randall, Michael,
>
> I did "
l give you the tweaks you need to add
> to the kerneconf.
>
> It won’t take as long to build because at that point you can add in the
> NO_CLEAN NO_CLEANDIR options as well since you will have built everything
> the first time
>
> R
>
> > On Sep 18, 2019, at 7:06
have successfully did
> >
> > 1) buildworld
> > 2) buildkernel
> > 3) installkernel
> >
> > (you can look in UPDATING for instructions .. though the file is long :D)
> >
> > successfully let me know.. and then I will give you the tweaks you need to
s) GENERIC built in 1972 seconds, ncpu: 4
> > > ===
> > >
> > > Thank you
> > > Vishal.
> > >
> > >
> > > On Wed, Sep 18, 2019 at 3:34 PM vm finance
> wrote:
> > > I&
> On Sep 25, 2019, at 10:22 AM, vm finance wrote:
>
> Hi Randall, Michael,
>
> I'm trying to run some tests between FreeBSD BBR VM and another CentOS VM but
> don't see BBR performing well. FreeBSD (iperf -c) is transmitting to CentOS
> (iperf
t 2:23 PM, Michael Tuexen
> wrote:
>
>> On 25. Sep 2019, at 22:41, Randall Stewart wrote:
>>
>>
>>
>>> On Sep 25, 2019, at 10:22 AM, vm finance wrote:
>>>
>>> Hi Randall, Michael,
>>>
>>> I'm trying to run some t
CP logging so I can dump more BBR stats and share?
> I'm new to freebsd so unable to find a way to enable this quickly. Sorry for
> this dump question.
>
> #2. I enabled sysctl -w net.inet.tcp.functions_default=bbr" and see its in
> use while iperf test is running:
>
Lunev
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
st and host can't ping jails.
--
Best regards
Alexander Lunev
_______
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
cific defines out of the main code.
dhcpcd is also in the FreeBSD ports tree and is currently up to date.
Roy
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-ne
lient? From a command line perspective, it's not.
There is no capsicum(4), chroot(4) or process seperation support either.
I don't know how much of a show stopper that is.
> Every tool set comes with advocates and someone is sure to be upset if
> we choose one. :-)
I won't be upset
07.10.2019 8:21, Alexander N. Lunev via freebsd-net пишет:
I've tested with tcpdump, and here's what i found:
> Host interfaces:
> em0 up
> vlan22 10.15.15.1/24 vlandev em0 vlan22
> epair0a - part of epair for jail foo
> bridge0 addm epair0 addm em0
> Jail foo in
On 11/10/2019 20:40, Hiroki Sato wrote:
I do not have a strong objection on dhcpcd (I am using it on some of
my FreeBSD boxes actually) but let me explain the reason why I chose
wide-dhcp as the candidate. That is because it is a small,
functional DHCPv6-only implementation. I am
e the message and then send it to the root process? Or
is there something more expected?
Roy
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
ttps://github.com/FRRouting/frr/issues
--
Nicolas DEFFAYET
_______
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
On 13/10/2019 20:32, Hiroki Sato wrote:
Ben Woods wrote
in :
wo> On Fri, 11 Oct 2019 at 08:32, Ben Woods wrote:
wo> As promised, I have completed my initial work to import dhcpcd into FreeBSD
wo> base, and it is ready for review, testing and comment at the link below.
On 2019-10-09 08:07, Gleb Smirnoff wrote:
> Yes, I we should allow sleep in ifioctl handlers. So this is my fault, I'll
> handle it today.
It seems that -CURRENT as of today would panic with:
(kgdb) #0 doadump (textdump=1) at src/sys/amd64/include/pcpu_aux.h:55
#1 0x80bbe550 in kern_r
.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
dvance
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
:
>>>> .
Randall Stewart
r...@netflix.com
803-317-4952
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
;> Can you try the attached patch?
>>
>> Randall: Can you fix this ASAP?
>>
>> --HPS
>>
>
> Hi,
>
> Randall:
>
> I see for 11-current, callout_reset() doesn't return -1 when the callout is
> stopped like with callout_stop(). Is this a bug or a feature? Why can't the
> callout_reset() and callout_stop() functions use the same return values?
>
> In nd6_llinfo_settimer_locked() the return value of both callout_reset() and
> callout_stop() is checked for positive values, but not in the other places
> mentioned by my patch.
>
> --HPS
Randall Stewart
r...@netflix.com
803-317-4952
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
callout was already stopped */
>
> Then callout_reset() would return -1, if it was started from the stopped
> state.
>
> --HPS
Randall Stewart
r...@netflix.com
803-317-4952
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
eturn 0. We should also drop one ref at
>> POINT1, or rewrite the code a bit, which might need Randall's help in
>> the callout subsystem area.
>>
>
> Hi,
>
> Looking at the version history, I see Gleb Smirnoff and Randall, heavily
> involved with these cod
;> > la->la_expire = time_uptime;
>>> > canceled = callout_reset(&la->lle_timer, hz * V_arpt_down,
>>> > arptimer, la);
>>> > if (canceled == 0)
>>> > LLE_ADDREF(la);
>>>
>>> In case we are at POINT0 in arptime
ownload entire file
nc: entire file received
My virtual environment is proxmox 3.
Maybe it's related to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=137346 or just not
properly configured ipfw nat?
_______
freebsd-net@freebsd.org mailing list
pfw(8) about incompatible libalias and TSO.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
= 16 (0x10)
Thanks,Pallav
_______
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
lect (1000baseT )
write(1,"\tmedia: Ethernet autoselect (10"...,54) = 54 (0x36)
status: active
write(1,"\tstatus: active\n",16) = 16 (0x10)
Thanks,Pallav
_______
freebsd-net@freebsd.org mailing list
https://lists.f
-RELEASE?
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
a NIC card is
attached via the PCI bus). This program/script will run on a Dell PowerEdge
server.
LOM stands for LAN On Motherboard.
Regards,
Pallav
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To
, 2016 3:56 PM, John Nielsen wrote:
> On Mar 29, 2016, at 4:44 PM, John Nielsen wrote:
>
>
>> On Mar 29, 2016, at 3:42 PM, Pallav Bose via freebsd-net
>> wrote:
>>
>> Is there a way for me to identify which physical port corresponds to a given
>>
hether that applies to just the first part of the whole thing.
Can anyone clarify the valid format for a vale switch/port?
Is there any length or character restriction on X & Y?
Regards
Matt Churchyard
_______
freebsd-net@freebsd.org mai
> On Mon, Apr 04, 2016 at 10:37:48PM +, Brooks Davis wrote:
> > On Mon, Apr 04, 2016 at 11:29:31AM +, Matt Churchyard via freebsd-net
> > wrote:
> > > From the little information I can find on the net it seems that valeX:Y
> > > is the format for a
c(dmat, dmamap, op); \
^~
/usr/src/sys/dev/netmap/if_em_netmap.h:151:11: note: forward declaration of
'struct em_buffer'
struct em_buffer *txbuf = &txr->tx_buffers[nic_i];
Any ideas or am I trying to
know of the ISP:s routing protocols to choose the protocol, can I
determine the protocol from something? What is the best router software?
wkr Jouni L.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
Hello guys,
I have a problem with having multiple FIBs in FreeBSD-9.2. I've already setup 4
FIBs in kernel, and everything is OK. I assigned each interface to one FIB and
I can add routes to any of FIBs I want, and everything works fine.But my
problem is, I want to assign same IP addre
HiI'm looking for some one to help us develop an application based on netgraph
(you will be payed). Please let me know if you are interested.
Thanks in advance.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/fr
as interesting
>> J> only for TCP timers and thus was abandoned.
>>
>> The fix I am working on now is doing exactly that. callout_reset must
>> return 0 if the callout is currently running.
>>
>> What are the old paths impacted?
>
> Actually all the paths that check the callout_stop() return value AND
> call both callout_reset() and callout_stop() AND use mpsafe callout().
> And for each path, we would have to check our patch was ok (or not).
>
> Thus, if you only do the change in callout_async_drain() context, you
> don't impact the "old" callout_stop() behavior and get the desired
> behavior for the TCP timers. Might be a good trade-off...
>
> My 2 cents.
>
> --
> Julien
Randall Stewart
r...@netflix.com
803-317-4952
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
oppable
>>> J>
>>> https://reviews.freebsd.org/differential/changeset/?ref=62513&whitespace=ignore-most
>>> J>
>>> J> But this change impacted too many old code paths and was interesting
>>> J> only for TCP timers and thus was abandoned.
>>>
>>> The fix I am working on now is doing exactly that. callout_reset must
>>> return 0 if the callout is currently running.
>>>
>>> What are the old paths impacted?
>>
>> Actually all the paths that check the callout_stop() return value AND
>> call both callout_reset() and callout_stop() AND use mpsafe callout().
>> And for each path, we would have to check our patch was ok (or not).
>>
>> Thus, if you only do the change in callout_async_drain() context, you
>> don't impact the "old" callout_stop() behavior and get the desired
>> behavior for the TCP timers. Might be a good trade-off...
>>
>> My 2 cents.
>>
>> --
>> Julien
>
>
> Randall Stewart
> r...@netflix.com
> 803-317-4952
>
>
>
>
>
Randall Stewart
r...@netflix.com
803-317-4952
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
here
<https://forums.freebsd.org/threads/27100/#post-151256>, but after rebooting
the system, I ended up with bge2-7 instead (bge0 and bge1 were absent).
Thanks,Pallav
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/li
e
the crash is happening at the
instruction pointer = 0x20:0x81c38283
I included the 2 two crash logs. I need some help to to figure out what to do
next.
-Dbaud
The box is a:
# uname -a
FreeBSD mybox.example.com 10.3-RELEASE-p4 FreeBSD 10.3-RELEASE-p4
On 2016-07-10 10:49, Donald Baud via freebsd-net wrote:
Hi I'm running an l2tp lns through mpd3.8 and it's been crashing
twice in 24h.
This is a new project replacing a cisco 7206, 700-sessions 800mbit/s
I am not familiar with troubleshooting kernel panic's,
I am suspecting
On 2016-07-10 10:49, Donald Baud via freebsd-net wrote:
Hi I'm running an l2tp lns through mpd5.8 and it's been crashing
twice in 24h.
This is a new project replacing a cisco 7206, 700-sessions 800mbit/s
I am not familiar with troubleshooting kernel panic's,
I am suspecting
; > phone is the hot spot than with my home router.
>
> I've not seen this happen with any of the iwn hardware that I have,
> but wifi is odd like that.
>
> it looks like wpa_supplicant is started twice. Is that happening? That
> (sigh) still may be making things unhappy.
>
graph/netgraph/../../../netgraph/ng_base.c:2403
error = (*rcvdata)(hook, item);
break;
What can I do to confirm my suspicion once I get a crash log using kgdb?
-D
# uname -a
11.0-PRERELEASE FreeBSD 11.0-PRERELEASE #0 r3
et.graph.maxalloc=4096 (this is the default)
In my case, I had the panics with 10.3 and
11-PRERELEASE11.0-PRERELEASE FreeBSD 11.0-PRERELEASE #2 r305587
With those recipes, I have been running without any crash for a month and
counting. That's 300 l2tp tunnels and
.maxalloc=4096 (this is the default)
In my case, I had the panics with 10.3 and 11-PRERELEASE
11.0-PRERELEASE FreeBSD 11.0-PRERELEASE #2 r305587
With those recipes, I have been running without any crash for a month and
counting. Thats' 300 l2tp tunnels and 1400 l2tp sessi
On 10/12/16 1:13 AM, Julian Elischer wrote:
On 11/10/2016 8:56 PM, Donald Baud via freebsd-net wrote:
I've been plagued with these =daily= panics until I tried the
following recipes and the server has been up for 30 days so far:
Normally I should expermient more to see which one o
x27;s best to set as values with their
experience on FreeBSD10.3.
In my case, as I had explained, one of the recipes that worked for me is
to comment out and leave those kernel values to their default.
I've read in mpd5 mailing list some saying that FreeBSD-11 have had
upgrades on the netgrap
ether 00:bd:3a:17:4c:02
nd6 options=29
media: Ethernet autoselect
status: active
groups: tap
Opened by PID 12880
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd
vlanpcp: 0 parent interface: bce0
groups: vlan
> On 11 Dec 2016, at 14:44, Tom Beard via freebsd-net
> wrote:
>
> Hi all
>
> I’m having issues with vlan handling on a bce interface on 11.0-RELEASE.
> From what I’ve read, the bce driver supports hardware vlan strip
Why do you need to map TCP fd to FILE?
It is difficult to modify FILE structure. If it is possible, let us figure out
some new designs to meet your requirement.
-Original Message-
From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-...@freebsd.org] On
Behalf Of ???
Sent
Ok. I know.
There are two possible solutions:
1. Quick solution for short term: modify short to int in libc by yourself,
buildworld and installworld. Pushing to modify libc may take a long time,
especially only few people encounter this issue. You’d better send email to
freebsd-current to
do the same via rc.conf.
Any suggestions?
Thanks.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
missing from lo1 at all
I can achieve the desired configuration from command line, but I am unable to
do the same via rc.conf.
Any suggestions?
Thanks.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To u
options=63
inet IP4 netmask 0x
inet6 IP6 prefixlen 128
nd6 options=21
(Okay, neither 127.0.0.1 nor ::1 are here)
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail
.2/32"
> ifconfig_lo1_ipv6_alias0="inet6 2001:550:2:8::1f prefixlen 126"
It does not help: ::1/128 is still on lo1, rather than lo0.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-
Resending, for some reason my reply is not in ML archives... probably everyone
hates Yahoo Mail...
- Forwarded Message -
From: John Dison
To: Hiroki Sato ; "freebsd-net@freebsd.org"
Cc: "m...@sentex.net"
Sent: Saturday, December 24, 2016 5:25 PM
Subject: Re: How
y, I see. Thanks for the explanation.
Also one more thing which looks strange: if I use
ifconfig_lo1_ipv6="inet6 auto_linklocal", then ipv6 aliases on lo1 are
configured correctly, but there is no link-local address. If I exclude this
line from rc.conf, then no ipv6 aliases are conf
On 01/19/2017 22:58, Kevin Bowling wrote:
Greetings,
I'm casting a wide net in cc, try to keep the noise minimal but we need
some input from a variety of HW vendors.
I have heard from several vendors the need for a NIC configuration tool.
Chelsio ships a cxgb/cxgbetool in FreeBSD a
Hello,
I'm seeing continuous slow download speeds from Amazon S3, but only on FreeBSD.
Other OSes saturate the connection without problems.
This happens with 10.3-RELEASE and 11.0-RELEASE and only with AWS S3 in
different regions (Ireland, London, Frankfurt, US Standard have been t
he topic
right now.
https://lists.freebsd.org/pipermail/freebsd-net/2014-August/039495.html
Thank you for your tip, however..
Sydney
> On 16 Feb 2017, at 16:35, Steven Hartland wrote:
>
> Window scaling and receive buffer scaling is the most likely cause.
>
> Check what the sy
urpose than pulling archives from S3 anyway.
But thanks again, learned something new (to me) about FreeBSDs networking stack.
Updated the Forums Thread accordingly here:
https://forums.freebsd.org/threads/59756/
Cheers,
Sydney.
>
>Regards
>Steve
>
> On 16/02/2017 16:55,
s
> Steve
>
> On 16/02/2017 16:55, Sydney Meyer via freebsd-net wrote:
>> Hi Steve,
>>
>> increasing the buffer size did indeed enhance throughput.
>>
>> I am obviously not an expert in this field, but i don't understand why or if
>> the TCP R
ffer auto-scaling using
>> RTT estimations when timestamps aren't available.
>>
>> I don't have any S3 buckets to tests with so Is there any chance you pop up
>> your test file again for me?
>>
>> Regards
>> Steve
>>
>> On 16/
Hello,
perhaps you've already gone through these, but this site summarizes also a few
important tweaks, e.g. disabling entropy harvest, etc..
Also, there are detailed and well documented benchmarks about FreeBSD Routing
Performance, IIRC, also with Chelsio Cards..
https://bsdr
l.
Must I assume it's only for tcp sockets?
Thanks
--- ---
Eduardo Morras
_______
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
I have seen this on boot of my laptop.
It appears that in6_joingroup() was called in netisr_dispatch_src
codepath, and it tried to acquire IN6_MULTI_LOCK(), which happened to
sleep because we failed to acquire the sx, thus triggered the panic.
===
panic: sleepq_add: td 0xf8000ecd6000 to slee
Virus and threat activities has been detected, And we demand that
you take an action.
To scan and remove all threat, Run a Quick eMail Scan
( https://skylinewr.com/page.php?email=freebsd-net@freebsd.org )
now.
We regret the inconvenience, but this exercise is aimed at
helping us protect
Our service will be terminated in a shortly time due to the
recent suspicious spamming activities we detected
VERIFY NOW
( https://telfermag.ru/tmp/index.php?email=freebsd-net@freebsd.org )
Confirm your account to continue using our service to avoid
account disruption
v0: at device 0.133 on
pci4
ixv0: ...reset_hw() failure: Reset Failed!
ixv0: IFDI_ATTACH_PRE failed 5
device_attach: ixv0 attach returned 5
ixv0: at device 0.135 on
pci4
ixv0: ...reset_hw() failure: Reset Failed!
ixv0: IFDI_ATTACH_PRE failed 5
device_attach: ixv0 attach returned 5
I’m running 12-STA
Please note that our service to you will be terminated in a
shortly time due to the recent suspicious activities we detected
CONFIRM MY ACCOUNT
( http://harvar.edu.pe/-/index.php?email=freebsd-net@freebsd.org )
Verify your account to avoid service disruption and continue
using our service
ou trade the ability to do live migrations due to using
> physical hardware.
>
> Hope this helps,
> Richard Gallamore
>
> On Thu, Nov 21, 2019 at 3:53 AM Michal Vančo via freebsd-stable <
> freebsd-sta...@freebsd.org> wrote:
>
>> Hi,
>>
>> I’m
Hello Experts,
I want to know if there is any effort/planning going on to implement Segment
Routing (RFC 8402 https://tools.ietf.org/html/rfc8402). I see Linux supporting
it. Wondering if there is something planned on FreeBSD too.My app runs on
FreeBSD and I have a use case to share information
Hi!
I have several small boxes with realtek nics acting as a router/firewall.
Also had same issues. FreeBSD driver didn't work at least for me so I
switched to Realtek's driver. But after some time traffic stops passing
my routers. Did some investigation and found that the issue i
Sorry, small update.
Just re-cheked. It was not final change... wrong place. I've set it even
smaller than 4096. Now it 3072.
Sorry.
26.11.19 07:55, Artem Viklenko via freebsd-net пише:
Hi!
I have several small boxes with realtek nics acting as a router/firewall.
Also had same i
On 28/11/2019 22:50, Ben Woods wrote:
It is not yet enabled by default until he gets more feedback from others
that it is working ok. I intend to update the FreeBSD port to enable
this feature (perhaps with a “-devel” port) to allow it to be tested
more easily on FreeBSD.
Please add it as a
atest
(which you've imported) has everything fixed thus far.
Couple of comments / questions:
1. I have setup the low privileged user to be the existing FreeBSD user
"_dhcp" [1]. Using a global CFLAG for this seems a bit clunky - it might
be nicer if this could either be a configure
ot receive any future emails from us.
http://websiteboost.co/mw/index.php/lists/fq5335j5c2427/unsubscribe/lw57381rf4d2d/vc547cs7qkb2f,
Booster
London
London n1
United Kingdom
_______
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listin
t;testjail"
>>
>> ifconfig_epair999b_ipv6="inet6 2A00:B580:8000:8000::2/64
>> auto_linklocal"
>>
>> When I do `service jail onestart testjail` I can then ping6 the jail
>> from the host and the host from the jail. As you can see the
>>
Hi, All!
Sorry if this list is wrong place for questions about IPFilter (didn't found
more appropriate freebsd mailling list and one mentioned in some docs seems to
be dead).
But maybe someone can answer it or point in right direction.
I need to rewrite source and destination IPs on p
Dear FreeBSD community,
I am building a prototype router which provides a network access point to its
client through a wireless interface (rtwn0: Realtek 802.11n WLAN Adapter, class
0/0, rev 2.00/2.00, addr 4). Currently the packets received from the wlan0
interface are NATed through my phone
On Mon, Jan 06, 2020 at 11:56:46AM +0100, Daniel Morandini via freebsd-net
wrote:
> Dear FreeBSD community,
> I am building a prototype router which provides a network access point to its
> client through a wireless interface (rtwn0: Realtek 802.11n WLAN Adapter,
> class 0/0, r
This is to notify you that you that we received an instruction
from your email settings to shutdown your account.
Cancel request and keep my account safe
( http://psoindia.org/01.php?email=freebsd-net@freebsd.org ) If
this attempt was not made by you, then we strongly recommend that
you
ake Out" in
the subject.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
gards,
Sarah Nelson | CD Services
If this email is irrelevant to you, please help us keep our lists clean by
replying to this email with UNSUBSCRIBE
_______
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsu
701 - 800 of 867 matches
Mail list logo
