> On Mon, Apr 6, 2015 at 12:15 PM, Anton Farber > <dr_sweety_1...@hotmail.com> wrote: > > I've opened a thread on the FreeBSD networking forum > > (https://forums.freebsd.org/threads/jail-fails-to-connect-to-main-host.50833/) > > as sometime ago my FreeBSD server (initially running 10.1, now CURRENT) > > started to behave strangely after an upgrade from 10.0 to 10.1. I first > > noticed that a jail (192.168.1.5) wasn't able to contact the base system > > (192.168.1.1). Running a tcpdump revealed the following: the jail is using > > em0 instead of lo0 for communicating with the base system: > > You need to look at your routing tables. From inside the jail, run > "netstat -rn -f inet". You probably won't see any entry for 127.0.0.1 > or 127.0.0.0/8. Those are the entries that your jail needs in order > to talk to the base system. You can add them, but think carefully. > Many server processes, such as ntpd, have reduced security for > connections coming over 127.0.0.1. Whether or not it is appropriate > to add those routes depends on why you are using a jail.
Ok, so the behaviour I'm seeing regarding the communication between jail and base system is to be expected then. My reason for posting it was, that I was unsure whether it might have anything to do with the main problem. I don't think that this is the case so the question remains, why is my FreeBSD server sometimes using the router for contacting hosts on the local network? Regards, Anton _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
