I am having a problem monitoring network stats on jails on a host.
Scenario:
One host, FreeBSD 12.1, with a small number of vnet jails.
I'm using netgraph to bridge two or more VLANs from physical NICs into
each jail - so each jail has at least 2 ngether interfaces which are the
only NICs in t
et
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
--
Paul Thornton
___
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 18/08/2016 21:55, Ryan Stone wrote:
On Thu, Aug 18, 2016 at 4:48 PM, Paul A. Procacci
wrote:
You should be able to ping the local subnet.
Alternatively you can use net/arping.
~Paul
I'm specifically looking to test the handling of 255.255.255.255, so a
local broadcast address is out. U
Hi,
On 28/04/2015 22:06, Rick Macklem wrote:
... If your
net device driver is one that allocates 9K jumbo mbufs for receive
instead of using a list of smaller mbuf clusters, I'd guess this is
what is biting you.
Apologies for the thread drift, but is there a list anywhere of what
drivers migh
Hi
On 27/04/2015 06:41, Julian Elischer wrote:
Basically all the setup scripts in /etc/rc.d (andaother setup scripts in
/etc and /usr/local/etc)
all source /etc/rc.conf and it's friends (defaults etc.)
if any of thse scripts gets called (for example by devd when it notices
a new interface),
the
Hi
This happens when any interface is created if you've enabled forwarding
with the sysctl and not using gateway_enable in rc.conf. It is easily
fixed though.
See this thread from January:
https://docs.freebsd.org/cgi/getmsg.cgi?fetch=403720+0+archive/2015/freebsd-net/20150104.freebsd-net
P
On 09/02/2015 16:34, Daniel Corbe wrote:
For some reason, every time I create a GRE interface on a FreeBSD IPv6
gateway, net.inet6.ip6.forwarding is disabled. As long as I manually
re-enable it with sysctl, both the GRE tunnel and the IPv6 network
behind this machine will continue to work; howe
Hi,
On 03/01/2015 18:06, Mike Tancsa wrote:
do you set forwarding via just /etc/sysctl.conf or in /etc/rc.conf via
ipv6_gateway_enable and gateway_enable. I seem to recall some discussion
about there being a difference. Perhaps devd is calling something that
then fiddles with the setting ignor
Hi,
I can also replicate this behaviour on 10.1-RELEASE by simply creating
an additional vlan interface. It affects IPv4 and IPv6 forwarding.
This is taken from a test setup of FreeBSD boxes running Quagga as BGP
routers - but with a default GENERIC kernel. This machine has 2x ixgbe,
4x ig
On 04/05/2011 18:05, YongHyeon PYUN wrote:
>
> FYI: Committed to HEAD(r221445).
I've been away from the machines with this chipset for the past week so
have not finished the testing, but can report that the initial tests I
did involving normal use, jumbo frames, v4 and v6 etc. all worked fine
and
Hi,
Good news - I have success!
On 20/04/2011 18:18, YongHyeon PYUN wrote:
> Ok, that would indicate there is an interrupt delivery issue if all
> others changes(including Marius' patch) are correct. Because there
> is no publicly available data sheet for BCM57765 yet I'm not sure
> what is real
Hi,
On 20/04/2011 14:44, Marius Strobl wrote:
> Hrm, looks like neither NetBSD nor OpenBSD support this variant so
> far, however Linux also doesn't seem to have special handling for it.
> Could you please give the attached patch in addition to the existing
> one a try?
I've added your patch to b
Hi,
On 20/04/2011 14:16, Marius Strobl wrote:
> Looks like brgphy(4) also needs to be taught about this hardware. Could
> you please provide the corresponding part of a verbose dmesg?
Hopefully this covers everything that you might need:
pcib4: slot 0 INTA is routed to irq 18
found-> vendor=0x14
On 19/04/2011 23:09, YongHyeon PYUN wrote:
> Here is experimental patch for BCM57765 family controllers. I
> don't have these controllers so the patch was not tested at all
> except compile. Recent Broadcom controllers like BCM57765 support
> EEE(Energy Efficient Ethernet) feature but it is not yet
Hi,
The bge driver doesn't support this chipset yet and I was wondering if
anyone has looked at implementing it.
NetBSD looks like it has support for it. Now I may be wrong here, but
it appears that the BCM57765 is similar to other devices based on the
NetBSD if_bge.c source version 1.194.
I've
On 09/11/2010 20:16, Paul Thornton wrote:
>
Sorry for that unedited copy of the last mail to the list. Finger
trouble in mail client. Must try harder!
Paul.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/free
Hi folks,
Keeping the list archives updated for any poor soul that has a similar
problem in future...
On 26/10/2010 18:55, Paul Thornton wrote:
> I'm also going to give mpd a go and see if that works - but if it tries
> the same config options as pppoed then I may be straight back
On 26/10/2010 18:55, Paul Thornton wrote:
> I've been taking another look at this after being dragged off onto other
> things for a few days, and hopefully have some more information that
> might help point in the right direction for a fix / where to debug next.
>
> On 20/1
Hi,
On 29/10/2010 18:23, Chuck Swiger wrote:
> On Oct 28, 2010, at 11:39 PM, Коньков Евгений wrote:
>> so using polling on gigabit NICs is a bottle neck? and is cause of low
>> performance, is not?
>
> Simple answer is yes. It should be possible that you could tune polling to
> get similar per
I've been taking another look at this after being dragged off onto other
things for a few days, and hopefully have some more information that
might help point in the right direction for a fix / where to debug next.
On 20/10/2010 17:16, Julian Elischer wrote:
> have you tried to connect this cisco
Hi,
On 19/10/2010 22:06, Julian Elischer wrote:
> Wireshark understands all the protocols in question so get packet
> captures of good and
> bad sessions (as similar as you can) and see what is different.
> (wireshark reads
> tcpdump files so it's easy to capture).
As is often the case, the packe
Hi all,
I'm hoping that someone can point me in the right direction to get
enough debug to troubleshoot a very annoying connection problem with
PPPoE to a Cisco.
I have a freshly installed 8.1-RELEASE amd64 box with a very simple
PPPoE daemon setup on it. This works fine for a test WinXP and Mac
Hi list,
A bit of advice please, folks.
We currently use 6.2-release + Quagga as a router on a number of boxes.
These are stable but we have seen some CPU issues recently and clearly
the code is all getting old now, and so I'm starting to look at updating
them.
Specifically, the hardware c
I have found the error of my ways...
For the purposes of the archives, I'm posting what actually made this
work. It is a very simple fix and I don't quite know how I missed trying
this out during my frustrations.
Before the "ipfw fwd..." line you need one or more "ipfw skipto..."
lines to en
Hi folks,
I'm having trouble using NAT and forward in the same ipfw ruleset. It
appears that the forward "wins" over the NAT regardless of ordering in
the ipwf ruleset. I'm hoping that I'm missing something obvious; but is
there a way to use these two together?
Some background - I'm testin
Hi,
Eugene Perevyazko wrote:
You have to look at keep-alive settings to terminate dead connections.
And why don't you try an mpd (/usr/ports/net/mpd) that is perfectly suited
to manage hundreds and thousands of simultaneous ppp (and PPPoE in particular)
connections? It's fast, flexible and easy
Hi Luiz,
Luiz Otavio O Souza wrote:
Change the enable lqr to:
enable lqr echo
set echoperiod 5
The ppp will check the remote peer at echoperiod and after five
consecutive fails the ppp link will be closed.
That does exactly what I want, thank you.
Paul.
__
Hi folks,
I am currently doing some lab testing with 6.3-release and a pppoe setup
where each user has their own VLAN. On the termination box have an em
interface with about 200 VLANs configured on it, and have a ppp.conf
looking like this:
default:
set log Chat Command Phase
enable pap
28 matches
Mail list logo
