https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207087
--- Comment #37 from g_amana...@yahoo.com ---
Setting dhcpcd to ignore the interface MTU resolves my problem.
However if I manually reduce the MTU the problem reappears and the client
receives no fragmentation-needed-ICMP. I am leaving thi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207087
--- Comment #36 from g_amana...@yahoo.com ---
I figured it out:
the dhcpcd changed the MTU of em0 each time it acquired a lease.
Setting "#option interface_mtu" in dhcpcd.conf leaves the MTU at 1500.
I think this resolves the whole thing.
I
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207087
--- Comment #35 from g_amana...@yahoo.com ---
I just did a:
$ route get 8.8.8.8
and got:
route to: google-public-dns-a.google.com
destination: default
mask: default
gateway: 69.251.142.1
fib: 0
interface: em0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207087
--- Comment #34 from g_amana...@yahoo.com ---
The only hypothesis I have is that when fragmentation is needed for an outgoing
packet (I have no idea why) and the client sending this packet is behind NAT,
the gateway cannot see the real IP of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207179
Marcelo Araujo changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|ara...@freebsd.org
--- Comment #3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207218
Mark Linimon changed:
What|Removed |Added
Keywords||patch
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207223
Mark Linimon changed:
What|Removed |Added
Keywords||patch
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207087
--- Comment #33 from George V. Neville-Neil ---
Really? Then why is there the "packet too large" ICMP message?
--
You are receiving this mail because:
You are on the CC list for the bug.
___
fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207087
--- Comment #32 from g_amana...@yahoo.com ---
(In reply to George V. Neville-Neil from comment #31)
MTU is 1500 on all interfaces (on WAN and LAN interface on the gateway, as well
as on the client).
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207232
Bug ID: 207232
Summary: unbound configuration file does not "Just Work" after
install. Suggest "borrowing" OpenBSD's .conf
Product: Base System
Version: 10.2-RELEASE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207179
--- Comment #2 from Nikolai Lifanov ---
I would like to comment that this patch is non-intrusive and low risk.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207087
--- Comment #31 from George V. Neville-Neil ---
Looking at the pcap files I see that the client is always advertising an MSS of
1460. In your setup what are the MTUs of each interface involved?
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207223
--- Comment #1 from Lars Engels ---
Works for me (TP X230):
# sysctl hw.acpi.battery.rate
hw.acpi.battery.rate: 13834
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207085
--- Comment #3 from joss.up...@yahoo.com ---
(In reply to Konstantin Belousov from comment #1)
Here's the state of the machine during one of these panics (back trace at the
bottom).
There are four instances of "monitor" and four instances o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207223
Bug ID: 207223
Summary: acpica/acpi_battery.c: introduce hw.acpi.battery.rate
sysctl
Product: Base System
Version: 11.0-CURRENT
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207208
--- Comment #2 from Maxim Konovalov ---
Also it makes sense to check the following sysctls for any non-standard
settings
net.inet.ip.maxfragpackets
net.inet.ip.maxfragsperpacket
and network stats for errors:
netstat -sp ip
netstat -sp ic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207208
Maxim Konovalov changed:
What|Removed |Added
CC||ma...@freebsd.org
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200663
--- Comment #3 from Larry Rosenman ---
any news on this?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207218
Bug ID: 207218
Summary: import dma_flushq rc script
Product: Base System
Version: 11.0-CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207215
Kristof Provost changed:
What|Removed |Added
CC||k...@freebsd.org
Assig
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207215
Bug ID: 207215
Summary: ipv6 pf rfc1323 seem to have an issue causing slow/no
connect with tcp6
Product: Base System
Version: 11.0-CURRENT
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207087
--- Comment #30 from g_amana...@yahoo.com ---
I am using in-kernel NAT, you can see the configuration in the ipfw.txt
attached above.
--
You are receiving this mail because:
You are on the CC list for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207087
--- Comment #29 from George V. Neville-Neil ---
If you have a natd.conf file that would also be helpful.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207208
Jasper Siepkes changed:
What|Removed |Added
Summary|ping has a problem with |ping has a problem with
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207208
Bug ID: 207208
Summary: ping has a problem with fragemented replies
Product: Base System
Version: 10.2-RELEASE
Hardware: amd64
OS: Any
Status: New
S
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206887
j...@nlnetlabs.nl changed:
What|Removed |Added
CC||j...@nlnetlabs.nl
--- Comment #
26 matches
Mail list logo
