On Thu, Aug 12, 2004 at 14:57:31 +0200, Ronald van der Pol wrote:
> Yep, I have the same problem with the latest 4.10: no ICMP6
> packet too big packets are sent.
Sorry, I made a mistake. I did not set net.inet6.ip6.forwarding=1
on the test machine. Now I have and now I get "packet too big"
icmp6
On Thu, Aug 12, 2004 at 14:01:56 +0200, Ronald van der Pol wrote:
> So, maybe something changed getween July 17th and now. I will
> see what happens after an upgrade to the latest 4.10.
Yep, I have the same problem with the latest 4.10: no ICMP6
packet too big packets are sent.
rvdp
On Thu, Aug 12, 2004 at 12:02:17 +1000, Mark Andrews wrote:
> Is this a known issue?
> Do you need more information?
I have tried it on
4.10-STABLE FreeBSD 4.10-STABLE #8: Sat Jul 17 10:08:52 CEST 2004
It sends "Packet too big" icmp6s on the wire. I also see the
netstat -s -p icmp6 "
On Thu, Aug 12, 2004 at 12:02:17 +1000, Mark Andrews wrote:
> The box does not appear to be generating a ICMP6 too big error
> message which I would expect to see once the 1428 octet TCP
> segments start arriving.
You could also check the output of:
netstat -s -p icmp6
There ha
I have a 4.10 stable box updated around August 1. It was previously
running 4.9-pre and was working fine.
It has the following interface configuration.
tx0 is internal, sis0 is external. The gif0 interface is
providing external IPv6 connectivity.
tx0: f
