Re: what is the secret behind 192.168.0.121

Hi, I found the cause of the problem. After fixing this problem in /etc/hosts: 192.168.0.127 raspberry8.alogt.comRaspberry8 192.168.0.128 raspberry8.alogt.comRaspberry9 After fixing the second line to 192.168.0.127 raspberry8.alogt.comRaspberry8 192.168

[Bug 205194] Changing MTU higher than 1500 on the interface pfsync0 causes panic

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205194 Kristof Provost changed: What|Removed |Added CC||k...@freebsd.org Assig

what is the secret behind 192.168.0.121

Hi, I have a very weird problem with my testing LAN. Only FreeBSD machines are on the network. It all works as expected until I give the address 192.168.0.121 to a client machine. This machine is not able to mount remote file systems via NFS despite this IP address is specifically mentioned in /et

Re: arp response fails

On Tue, 15 Dec 2015 23:47:39 +0100, bcs wrote: [..] > I use ipfw but "ipfw -q -f flush" didn't solve the issue. Here are my [..] > /boot/loader.conf: > ipfw_load="YES" > net.inet.ip.fw.default_to_accept=1 ipfw(8): Tunables can be set in loader(8) prompt, loader.conf(5) or kenv(1) before

FreeBSD LAGG port crash

Hi Team, I am seeing a crash with 10.1 stable which is not seen in 11-CURRENT. This is with lagg port operations, the below simple sequence of cmds cause system crash. ifconfig lagg0 create ifconfig lagg0 laggproto failover laggport le0 ifconfig lagg0 /* crash here */ See below for the backtraces