Date: Tue, 21 Aug 2001 14:37:25 +0100 (BST) From: Michael Grant <mg-fbsd@grant.org> To: freebsd-questions@FreeBSD.ORG Subject: Re: mtrace Message-ID: <200108211337.OAA22808@splat.grant.org>
next in thread | raw e-mail | index | archive | help
You're a genius, thanks. It was the firewall. I added the following rule to my ipf.conf and now it works fine. pass out quick proto 2 all "No route to host" is a really strange error to me. I guess the packet is somehow stopped before it gets sent out and EHOSTUNREACH is returned. I personally think the packet should be sent down and blocked by the firewall such that the firewall would put something into it's logs. This doesn't seem to be happening though. -Mike mark tinguely <tinguely@web.cs.ndsu.nodak.edu> wrote: > Do you have a packet filter enabled, what I hear you saying sounds a lot > like a packet filter rule discarding the multicast packets. > > If you are really sure that there is no packet filtering going on, then: > > If you stop the multicast daemon, start tcpdumps (-n -net 224) on xl0 and lo0, > start a multicast application such as vic 224.2.2.4/2224 (transmit using the > X window as your source). If you see no multicast traffic, then the packets > are not making it to the stack or out the driver. > > A check in the network stack (ip_output in sys/netinet/ip_output.c) or > in the xl driver sys/pci/if_xl.c may indicate the problem. tcpdump > should be just as good as the last test, so I would look what is going > on in the ip_output() code. > > There was a recent (after 4.3-RELEASE) patch to sys/netinet/ip_output.c > to better handle multicast routes, but by having a static multicast > route like you have would be the same affect. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200108211337.OAA22808>