--On 04 July 2019 10:59 +0200 Christian M
wrote:
From my tests I found that 10.4-RELEASE was as fast as you could expect
(>10Gbit/s), then something changed in 11.0-RELEASE and carried on and got
even worse in 12.0-RELEASE. Would it not be a good idea to begin there
(10.4 -> 11.0), and
--On 04 July 2019 09:23 +0200 Roger Pau Monné wrote:
As a workaround you can switch to the emulated network card by
setting 'hw.xen.disable_pv_nics=1' in /boot/loader.conf. That will
give you worse performance than a fully working PV network card, but
at least should be consistent. There are
--On 22 September 2017 at 20:16:25 +0100 Steven Hartland
wrote:
CARP on 9 and 10 are very different its not a separate interface anymore,
its a property on the parent interface, so the behavior your described is
expected.
If you want to disable carp just remove
Hi,
We've been using CARP for a long time - initially under FreeBSD 9.x.
We're just looking at setting it up on some 10.3 boxes, and have hit a
snag. Some of the syntax for setting it up has changed, but that's Ok,
we've read up and got it working.
The issue we've got is if I want to
--On 06 September 2016 09:42 +0100 Steven Hartland
wrote:
Yes known issue I'm afraid.
I created a patch set to address this but there where objections so it
was removed, see the attached which is based on 10.2-RELEASE.
Hi,
Thanks for the reply, and the
--On 06 September 2016 09:13 +0100 Karl Pielorz <kpielorz_...@tdx.co.uk>
wrote:
We've just changed the network config on a box - going from a single
'em1' adapter to a lagg failover of em0, em1.
Sorry - not enough coffee yet, I should have said this is on FreeBSD
10.3-RELEASE-p7
Hi,
We've just changed the network config on a box - going from a single 'em1'
adapter to a lagg failover of em0, em1.
This works - but we noticed after the machine rebooted, we couldn't ping it
from other hosts.
Checking on other machines on the LAN they still had an ARP entry for the
Ok...
--On 23 June 2016 13:32 +0100 Matthew Seaman wrote:
I use a similar config with vlans over lagg. While I haven't seen
exactly your problem, I did see one instance of the vlan interface
coming up with an all-zero MAC address (out of about 10 systems upgraded
to
--On 23 June 2016 13:32 +0100 Matthew Seaman wrote:
I use a similar config with vlans over lagg. While I haven't seen
exactly your problem, I did see one instance of the vlan interface
coming up with an all-zero MAC address (out of about 10 systems upgraded
to
--On 23 June 2016 14:30 +0200 Michael Gmelin wrote:
I don't think having an IP address on an interface that also has vlan
interfaces is a good idea. What kind of traffic are you expecting on
lagg1?
Hi,
This has worked for 'quite a while' (i.e. >year). lagg1 is connected
--On 23 June 2016 11:53 +0100 Karl Pielorz <kpielorz_...@tdx.co.uk> wrote:
This gets increasingly weird if I run tcpdump on the 10.3 box. The act of
running 'tcpdump -i lagg1.30 -n' actually fixes the problem:
As a follow up - running 'ifconfig lagg1 promisc' fixes the issue a
Hi,
We're in the process of updating our boxes from 10.1 to 10.3. This has gone
OK for the simpler cases - but I seem to have found a couple of issues with
the way 10.3 handles both configuring VLANs and actual traffic on VLANs.
On our box to be upgraded, our /etc/rc.conf has:
--On 13 July 2015 09:56 -0700 John-Mark Gurney j...@funkthat.com wrote:
You can fix the untagged traffic on lagg0 with something like the
following:
route change destination gateway -mtu 1500
You can see which routes need to be changed w/ the netstat -rWnfinet
command...
Ok, that works.
--On 13 July 2015 10:51 +0200 Steve Read steve.r...@stormshield.eu wrote:
Think about what it means. The MTU on the lagg0 interface is the
largest packet it can send for you or for its VLAN interfaces. The MTU
on the lagg0.10 (VLAN) interface is the largest packet *it* can send for
you.
--On 13 July 2015 13:06 +0100 Gary Palmer gpal...@freebsd.org wrote:
Have you read the HARDWARE section of vlan(4)?
Kind of cryptic answer ;) - But I just read vlan(4). So it looks like my
understanding of vlans (i.e. 'long frames' as it calls them) was right?
On supported kit - creating
--On 10 July 2015 11:06 -0700 John-Mark Gurney j...@funkthat.com wrote:
Try bumping the MTU on the root em's by 4 (1504) before creating the
lagg...
I had thought of that - but didn't want to try it (on the basis that out of
all the other example config's I've seen - no one else has to, and
Hi,
I've got a 10.1 box with a couple of Intel(R) PRO/1000 (82571EB) cards in
it, e.g.
em0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
options=4019bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO
...
I've set these up as a fail-over lagg
--On 14 June 2015 15:15 +0100 Karl Pielorz kpielorz_...@tdx.co.uk wrote:
I've disconnected 're1' again (as before) to see if that stops it locking
up.
Ok, don't use re1 for anything - the box is stable. Use re1 (even for
fairly low volumes of traffic) and the box locks up hard after
--On 12 June 2015 08:53:03 -0700 Adrian Chadd adr...@freebsd.org wrote:
Hi,
If this works for people then we should document this somewhere and
include the firmware/tool.
I upgraded the firmware (board shipped with 'production 4/5/2014') -
upgraded to '9/8/2014 beta' - and so far, this
for the time it had
been up.
-Karl
--On 14 June 2015 12:28:16 +0100 Karl Pielorz kpielorz_...@tdx.co.uk
wrote:
--On 12 June 2015 08:53:03 -0700 Adrian Chadd adr...@freebsd.org wrote:
Hi,
If this works for people then we should document this somewhere and
include the firmware/tool.
I
Hi,
I've recently bought an APU1 (by PC Engines) - this was to start to replace
a number of ALIX boards we use from them with FreeBSD.
However - I'm having issues with the onboard (Realtek) interfaces on it.
These show up in dmesg as:
Event timer HPET frequency 14318180 Hz quality 550
(and rebooting) - I've not seen any watchdog
timeout errors for any re interface.
-Karl
--On 10 June 2015 21:44:50 +0100 Karl Pielorz kpielorz_...@tdx.co.uk
wrote:
Hi,
I've recently bought an APU1 (by PC Engines) - this was to start to
replace a number of ALIX boards we use from them with FreeBSD
Hi,
I've got a Cisco 3750X switch a colleague is setting up. We've got this
configured - but it doesn't seem to talk nicely to our FBSD 10.0-R box,
looks like some kind of VLAN issue (but shouldn't be).
Switch side - the port is configured with:
switchport trunk encapsulation dot1q
--On 29 July 2014 09:24 -0400 Mike Tancsa m...@sentex.net wrote:
Would it not be better to have
switchport trunk allowed vlan 2200-2300
otherwise its not clear to me what would be tagged and what would not be
tagged as vlan 2000, no ?
I don't think that's the issue - I've had a couple of
Hi,
I originally posted to freebsd-xen about this (and I've raised a PR)
-pr188261 - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
It's been suggested I should ask in FreeBSD-NET to see if someone can look
at this, and suggest how to proceed...
In a nutshell - the FreeBSD PV
Hi,
I've a couple of boxes which *might* be hitting the ceiling for their NIC's
(i.e. using all the bandwidth on the link).
Other than looking at 'systat -if' - is there anything in netstat's output
(or anywhere else) that would indicate the system is either heavily queuing
outgoing
--On 13 August 2013 15:34 +0200 Daniel Hartmeier dan...@benzedrine.cx
wrote:
So, don't configure the carp interface in rc.conf, but do it in
/etc/rc.local, and be careful to add the address while the vhid is not
yet configured, as in:
ifconfig carp0 create
ifconfig carp0 inet
--On 15 August 2013 17:13:15 +0200 Damien Fleuriot m...@my.gd wrote:
Hmmm, I tried that - and it leaves the interface in a 'weird' state (at
least not the state I was expecting):
carp0: flags=9UP,LOOPBACK metric 0 mtu 1500
inet 192.168.107.21 netmask 0xff00
nd6
--On 13 December 2012 15:33 +0400 Gleb Smirnoff gleb...@freebsd.org wrote:
Nope, there is no autotuning here yet.
The hash table size is hardcoded in sys/net/if_llatbl.h. The name of
constant is LLTBL_HASHTBL_SIZE.
Default is 32, which is even commented with /* default 32 ? */ - I found
Hi,
I have an FreeBSD amd64 9-STABLE system running as a router for various
bits and pieces - this has a 'lot' of hosts on it's LAN (literally
thousands) - most are NAT end points etc.
Looking at the output from 'arp -a -n' it regularly lists 2,000-3,000
entries. Is there anything I need
--On 11 August 2012 12:36 +0430 Hooman Fazaeli hoomanfaza...@gmail.com
wrote:
NameMtu Network Address Ipkts Ierrs Idrop
Opkts Oerrs Coll em01500 Link#5 00:25:90:31:82:46 355482
10612864185945 0 291109 3032246910270 1516123455135
82574L with ASPM
Hi,
Apologies for posting to -net as well - I originally posted this to
-hackers, but was advised to re-post it here...
A FreeBSD 9.0-R amd64 box - based on a SuperMicro X8DTL-IF Rev. 2.01
w/Intel L5630 6Gb of RAM seems to have issues with it's onboard NIC (em
driver based - i.e. em0).
--On 10 August 2012 12:18 -0700 EXT-Glatting, Dennis P
dennis.p.glatt...@boeing.com wrote:
I've seen this too on a H8DG6-F but changed to the igb interfaces. I am
also seeing a problem under ESXi 5.0 on an unpatched system but haven't
had the opportunity to patch (ESXi) it. There I will see
33 matches
Mail list logo