Re: Multicast in jail?
- "Bjoern A. Zeeb" wrote: > On Tue, 7 Jul 2009, Alexander Leidinger wrote: > > > Quoting Bill Marquette (from Mon, 6 > Jul 2009 > > 20:14:02 -0500 (CDT)): > > > >> I'm trying to run Avahi in a jail, much the same as Alexander > Leidinger in > >> this email from late last year > >> http://www.mail-archive.com/freebsd-jail@freebsd.org/msg00587.html. > I > >> couldn't find any replies to that thread and it seems that I'm > running into > >> the same issues - the service announcements make it on the wire and > the > >> other devices in the network see them. > Alternatively I wouldn't wonder if enabling raw sockets would give > what you want or you'll wait for virtualization to be ready. I tried raw sockets also but as with Alexander, that didn't make any appreciable difference. In the short term I think I can work around this by bouncing Avahi every couple of minutes (it appears to work properly over the last couple minutes at least). I'm certainly willing to give VIMAGE a try if it's likely to fix the issue although by your statement, it sounds like it's unlikely to at this time. Thanks --Bill ___ freebsd-jail@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
Re: Multicast in jail?
Quoting "Bjoern A. Zeeb" (from Tue, 7 Jul 2009 11:08:46 + (UTC)): Alternatively I wouldn't wonder if enabling raw sockets would give Didn't work for me. what you want or you'll wait for virtualization to be ready. As _I_ don't need it on -stable: it's what I'm waiting for. Bye, Alexander. -- The greatest of faults is to be conscious of none. http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-jail@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
Re: Multicast in jail?
On Tue, 7 Jul 2009, Alexander Leidinger wrote: Quoting Bill Marquette (from Mon, 6 Jul 2009 20:14:02 -0500 (CDT)): I'm trying to run Avahi in a jail, much the same as Alexander Leidinger in this email from late last year http://www.mail-archive.com/freebsd-jail@freebsd.org/msg00587.html. I couldn't find any replies to that thread and it seems that I'm running into the same issues - the service announcements make it on the wire and the other devices in the network see them. So far I have nothing working. I assume that the mcast traffic is not arriving at all IPs. guess>Either because on overly restrictive jail check, and/or just because there's no code which is distributing the traffic to all IPs. It seems kern_jail.c is a place to check if there's some code which handles No, in_pcb.c in6_pcb.c in_m*.[ch] in6_m*.[ch] are the files you need as a starting point; there's more and more and more. this. Maybe prison_check_ip[46] if mcast is on top of this, or something new to write if mcast is a different "AF". Again, this is a wild guess, I don't have enough understanding of the network code in the kernel to even make educated guesses about the real reason. But you first will have to understand all implications, that need a proper design plan and after that thoughtout implementation. Alternatively I wouldn't wonder if enabling raw sockets would give what you want or you'll wait for virtualization to be ready. /bz -- Bjoern A. Zeeb The greatest risk is not taking one. ___ freebsd-jail@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
Re: Multicast in jail?
Quoting Bill Marquette (from Mon, 6 Jul 2009 20:14:02 -0500 (CDT)): I'm trying to run Avahi in a jail, much the same as Alexander Leidinger in this email from late last year http://www.mail-archive.com/freebsd-jail@freebsd.org/msg00587.html. I couldn't find any replies to that thread and it seems that I'm running into the same issues - the service announcements make it on the wire and the other devices in the network see them. So far I have nothing working. I assume that the mcast traffic is not arriving at all IPs. guess>Either because on overly restrictive jail check, and/or just because there's no code which is distributing the traffic to all IPs. It seems kern_jail.c is a place to check if there's some code which handles this. Maybe prison_check_ip[46] if mcast is on top of this, or something new to write if mcast is a different "AF". Again, this is a wild guess, I don't have enough understanding of the network code in the kernel to even make educated guesses about the real reason. Bye, Alexander. -- Ask not for whom the Bell tolls, and you will pay only the station-to-station rate. -- Howard Kandel http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-jail@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
Multicast in jail?
I'm trying to run Avahi in a jail, much the same as Alexander Leidinger in this email from late last year http://www.mail-archive.com/freebsd-jail@freebsd.org/msg00587.html. I couldn't find any replies to that thread and it seems that I'm running into the same issues - the service announcements make it on the wire and the other devices in the network see them. However after some time, the other devices expire the service from their cache and ask for an update. As best as I can tell, the multicast update packets aren't making it into the jail (I can certainly imagine why not!). I don't have MROUTED compiled in the kernel, however the previously noted email did and it still didn't work. I'm running 8.0-CURRENT as of 27-June-2009 on this machine now, GENERIC kernel with WITNESS and INVARIANTS compiled out. Host: > ifmcstat em0: inet 192.168.69.100 igmpv3 flags=0<> rv 2 qi 125 qri 10 uri 3 group 224.0.0.251 mode exclude mcast-macaddr 01:00:5e:00:00:fb group 224.0.0.1 mode exclude mcast-macaddr 01:00:5e:00:00:01 lo0: inet 127.0.0.1 igmpv3 flags=0<> rv 2 qi 125 qri 10 uri 3 group 224.0.0.1 mode exclude inet6 fe80::1%lo0 mldv2 flags=0<> rv 2 qi 125 qri 10 uri 3 group ff01::1%lo0 mode exclude group ff02::2:736f:581e%lo0 mode exclude group ff02::1%lo0 mode exclude group ff02::1:ff00:1%lo0 mode exclude Jail: > ifmcstat lo0: inet6 fe80::1%lo0 mldv2 flags=0<> rv 2 qi 125 qri 10 uri 3 group ff01::1%lo0 mode exclude group ff02::2:736f:581e%lo0 mode exclude group ff02::1%lo0 mode exclude group ff02::1:ff00:1%lo0 mode exclude I'm pretty sure I saw em0 in the ifmcstat output for the jail the other day when I was messing with this, but I've rebooted since and have no idea what sequence of events led to that. I hope I'm just missing something and I can get this setup working. Any help would be most appreciated. Thanks --Bill ___ freebsd-jail@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
