ng_ipacct VIMAGE option on 12.1-RELEASE

Hi. Please change in pkg base default option on FreeBSD-12.1 to VIMAGE enabled because each time I do `pkg upgrade` it tries to reinstall ng_ipacct with VIMAGE DISabled. Installed packages to be REINSTALLED: ng_ipacct-20180401 (options changed) After that I must do pkg deinstall

Re: ng_ipacct on FreeBSD 12.1 doesnt work

Great Thanks. сб, 7 дек. 2019 г. в 03:28, Eugene Grosbein : > 07.12.2019 7:22, Eugene Grosbein wrote: > > Adding port maintainer to CC: > > >> Yes. It works. Thank you very much. > >> > >> I delete manual copied file. > >> I install ports via portsnap. > >> I fetch srcs from ftp. > >> And

Re: ng_ipacct on FreeBSD 12.1 doesnt work

two years it works on version 11.1 very well. But after upgrade from 11.3 to 12.1 "pkg install ng_ipacct" got broken. Is it really can be? Or it's my mistake? Thanks again. пт, 6 дек. 2019 г. в 22:37, Eugene Grosbein : > 07.12.2019 0:49, Eugene Kazarinov wrote: > > &g

ng_ipacct on FreeBSD 12.1 doesnt work

Hi. pkg install ng_ipacct install ng_ipacct.ko in /boot/modules/ and it doesnt start if I copy ng_ipacct.ko to /boot/kernel/ it didnt start with error: link_elf_obj: symbol tcbinfo undefined linker_load_file: /boot/kernel/ng_ipacct.ko - unsupported file type How to run ng_ipacct on FreeBSD 12.1?

Re: something is not working: ipfw fwd VIA nat TO tun on FreeBSD-11 stable r318266

) By now I see that ipnat.rules is mapping forwarded packets on 10.3-STABLE and doesnt map they on version FreeBSD-11 stable r318266. So. Something in ipnat mechanism is broken in FreeBSD-11 stable r318266. 2017-05-15 23:28 GMT+03:00 Eugene Kazarinov <kamu...@milshop.ru>: > Hello. > A

something is not working: ipfw fwd VIA nat TO tun on FreeBSD-11 stable r318266

Hello. After upgrade from 10.3 stable something broke. I have tun0 tun0: flags=8151 metric 0 mtu 1500 options=8 inet 10.10.0.6 --> 10.10.0.5 netmask 0x groups: tun Opened by PID in pf.conf I have rule nat on tun0

Re: i386 vs amd64?

Hello everybody. (sorry for my english) # For individuals wanting to upgrade their sources (even if only a # delta of a few days): # # 1. `cd /usr/src' (or to the directory containing your source tree). # 2. `make buildworld' # 3. `make buildkernel KERNCONF=YOUR_KERNEL_HERE'

FreeBSD 6.3/amd64: cvsup: Bus error (core dumped)

Hello. Dont know is this list right for this topic, but dont know witch one is. So I got 6.3-STABLE-200807-amd64-disc1.iso I have installed it cd /usr/ports/net/cvsup-without-gui/ make install make clean #cvsup some-stable-sup-file Connected to cvsup.xx.ru Bus error (core dumped) I cant get

Re: FreeBSD 6.3/amd64: cvsup: Bus error (core dumped)

nice. After posting I think to get a look to manual if it has changed since last time then I look into and tatata... ;) *Note:* The implementation of *CVSup* protocol included with the FreeBSD system is called *csup*. It first appeared in FreeBSD 6.2. 2008/8/7 Eugene Kazarinov [EMAIL

FreeBSD 6.3/amd64: ng_ipacct Depends on kernel ?? why? when?

Hello again. Situation 1 I have installed 6.3-STABLE-200807-amd64-disc1.iso #cd /usr/ports/net-mgmt/ng_ipacct/ #make install clean it's ok. It has installed. (sorry for my english) next Situation 2 I have installed 6.3-STABLE-200807-amd64-disc1.iso csup it to last src tree. csup it to last

Re: FreeBSD 6.3/amd64: ng_ipacct Depends on kernel ?? why? when?

By the way. I use this kernel config since 5.4-stable, then was 6.0, after that 6.2 and on one server is 6.3-PRERELEASE now. It works. My kernel config is === include GENERIC options IPFIREWALL options IPFIREWALL_FORWARD options IPFIREWALL_VERBOSE

Re: FreeBSD 6.3/amd64: ng_ipacct Depends on kernel ?? why? when?

Ok Let's see There is /usr/ports/net-mgmt/ng_ipacct/Makefile old version is # $FreeBSD: ports/net-mgmt/ng_ipacct/Makefile,v 1.9 2008/06/02 16:27:40 skv Exp $ and containts these lines .ifndef PACKAGE_BUILDING NO_PACKAGE= Depends on kernel .endif last version is # $FreeBSD:

Re: FreeBSD 6.3/amd64: ng_ipacct Depends on kernel ?? why? when?

# $FreeBSD: ports/net-mgmt/ng_ipacct/Makefile,v 1.9 2008/06/02 NO_PACKAGE= Depends on kernel # $FreeBSD: ports/net-mgmt/ng_ipacct/Makefile,v 1.10 2008/08/05 IGNORE= Depends on kernel Should I change IGNORE to NO_PACKAGE and it should works fine for me? Or something

Re: FreeBSD 6.3/amd64: ng_ipacct Depends on kernel ?? why? when?

So, one gets run on the module you want to load fails (and prints the message you see). The next one is run and it understands that file type so loads it. I understand now. Thank you a lot again. ___ freebsd-stable@freebsd.org mailing list

6.2-pre: g_vfs_done():ad4s1d[READ(offset=-8573723385966362624, length=16384)]error=5

IMHO very nice offset. It worked on ali chip, about wich I ask in message with topic: cant start 18, 21-24 hdd drives on 6.2-PRERELEASE/amd64. pls pls hel I mean sata drive that freebsd fand on ali controller - ad26 (seagate 320 gb 7200.10 sata II) fsck doesnt fix it. It hangs on [EMAIL

ipnat: map 10.0.0.0/8 - 212.118.x.y/29: freebsd freeze

Now I use map 10.0.0.0/8 - 212.118.z.w/32 and it works fine. ipnat -s now shows inuse 55633, maximus that i saw was about 8 How to resolve this problem? ___ freebsd-stable@freebsd.org mailing list

cant start 18, 21-24 hdd drives on 6.2-PRERELEASE/amd64. pls pls help

I have nForce3 motherboard and Athlon 64 Here is /var/log/messages Sep 28 03:41:03 ddf syslogd: kernel boot file is /boot/kernel/kernel Sep 28 03:41:03 ddf kernel: Copyright (c) 1992-2006 The FreeBSD Project. Sep 28 03:41:03 ddf kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991,

Re: cant start 18, 21-24 hdd drives on 6.2-PRERELEASE/amd64. pls pls help

[EMAIL PROTECTED] /]# vmstat -i interrupt total rate irq1: atkbd0 381 0 irq14: ata0 135495 28 irq15: ata1 166738 34 irq16: atapci3 36963 7

Re: Polling and em0

Since 6.1 I have stopped using polling as a regular kernel seems to give good performance as compared to polling mode. In fact I used to get anything between 55-75megs/sec on 6.1 with regular cables but since upgraded to cat6 quality Ethernet cable I get practically full gigabit speed with no

ERROR: StepTime does not match Avc 900. Please Report this.

FreeBSD 6.2-PRERELEASE #10: Sat Sep 16 04:13:37 MSD 2006 16-09-2006 16:50:01, ERROR: StepTime does not match Avc 900. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc -600. Please Report this. 16-09-2006 16:50:01, ERROR: StepTime does not match Avc

Re: em0: watchdog timeout -- resetting (6.1-STABLE)

Something with em0 is really wrong. I dont get timeouts, but Before cvsup I had 6.0-PRERELEASE and didn't have a problem. Now I have FreeBSD 6.2-PRERELEASE #8: Fri Sep 15 03:44:49 MSD 2006 and the problem is so: (On machine I have LARGE_NAT, em0, em1, em2) on fresh system ping to www.ru from