[PC-BSD Testing] BIND problem in jail
kris at pcbsd.org
Fri May 7 04:36:20 PDT 2010
On 05/07/2010 14:09, Jeff wrote:
> Well, this has come back to bite me again.
> I was living in Thailand when it I fixed it, using a Dlink ADSL router
> and used DHCP for the PCBSD box. Then I moved back to the US and set
> up my old network using a Linksys router and a Linksys wireless bridge
> to connect my PCBSD box to the router and the internet.
> I'm using lagg0 for the jail but set up the box with a static IP. So
> now the original problem is back - slow server response in the jail
> and Drupal cannot talk to the internet for updates and such. Set it
> up with DHCP and same problem.
> Oddly enough, when I had it setup with a static IP, Firefox was really
> slow accessing the server site, like 10 seconds lag, but Opera was the
> normal 1 or 2 seconds. When I changed to DHCP both were slow, taking
> nearly 20 seconds to respond - it's all lag time - the page loads very
> fast after that.
> I noticed at boot there is a message something to the effect of re0
> busy. Also noticed in Webmin, the network interface is reported as:
> * <http://127.0.0.1:10000/net/list_ifcs.cgi?mode=active#>* *Name
> <http://127.0.0.1:10000/net/list_ifcs.cgi?mode=active#>* *Type
> <http://127.0.0.1:10000/net/list_ifcs.cgi?mode=active#>* *IP Address
> <http://127.0.0.1:10000/net/list_ifcs.cgi?mode=active#>* *Netmask
> <http://127.0.0.1:10000/net/list_ifcs.cgi?mode=active#>* *Status
> lagg0 Unknown 192.168.1.101 255.255.255.0 Up
> lagg0:0 Unknown (Virtual) 192.168.1.12 255.255.255.255 Up
> lo0 <http://127.0.0.1:10000/net/edit_aifc.cgi?idx=0> Loopback
> 127.0.0.1 255.0.0.0 Up
> 192.168.1.12 is the IP for the jail and .101 is the network interface
> card on DHCP.
> I have had similar problems with PCBSD going way back and never
> resolved them. I just keep fiddling and rebooting and somehow it
> magically gets fixed but I never know why. Now however, I can't get
> it to work properly no matter what I try.
> What in the world causes this behavior and how do I fix it?
Well, I'm unsure which is causing the failure here. Maybe a good thing
to try is taking the "lagg0" device out of the loop and see if the
problem goes away. You'll need to edit /etc/rc.conf manually, remove the
ifconfig_lagg0 line, and setup ifconfig_re0 to DHCP. Switch your jail to
running on re0 as well, and test, does it work better?
If that doesn't solve it, then you may be uncovering some other
networking bug :( I would recommend reporting it over to the freebsd-net
Some of the folks over there could probably track it down relatively
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Testing