ipac-ng-common — The ipac-ng USER MAILING LIST. Discussions, Help, etc.

Re: [Ipac-ng-common] ipac-ng-1.34.2 data accounting discrepancy

[Sergey M. <sm...@sm...>]

Hello, Matthew.

ipacsum makes interpolation of data. If the data was recorded at 
00:00:10 and 00:05:14, and you will call ipacsum after 00:05:14 
requesting interval from 00:00:00 to 00:05:00, it will output whole data 
recorded at 00:05:14 minus interpolated data for 14 seconds plus 
interpolated data for 10 seconds from previous record.

Sergey Merzlikin

10.03.2016 6:07, Matthew пишет:
> Hello Sergey,
>
> I just wanted a clarification of the output. fetchipac is saving ip
> accounting data every 5 minutes using cron.
>
> So if I wanted to know the data that went from
> 00:00:00 through to 00:05:00
> this data is actually saved at
> 00:05:14
> do I actually need to request the data from
> 00:05:00 to 00:10:00 (--starttime YYYYMMDD0005 --endtime YYYYMMDD0010)
> to actually find out the data that went from 00:00:00 through to 00:05:00
> ??
>
>
> Kind regards,
> Matthew
>
>
>

Re: [Ipac-ng-common] ipac-ng-1.34.2 data accounting discrepancy

[Matthew <ipa...@wi...>]

Hello Sergey,

I just wanted a clarification of the output. fetchipac is saving ip  
accounting data every 5 minutes using cron.

So if I wanted to know the data that went from
00:00:00 through to 00:05:00
this data is actually saved at
00:05:14
do I actually need to request the data from
00:05:00 to 00:10:00 (--starttime YYYYMMDD0005 --endtime YYYYMMDD0010)
to actually find out the data that went from 00:00:00 through to 00:05:00
??


Kind regards,
Matthew



Quoting "Sergey Merzlikin" <sm...@sm...>:

> Hello, Matthew.
>
>  > What situations could cause ipac-ng to be inaccurate?
>  >
> Ifconfig shows traffic counted by hardware or driver, whereas ipac-ng
> shows traffic counted by linux kernel. These are different points of
> traffic flow, so counted traffic may differ. In particular, some packets
> may be silently dropped or silently retransmitted due to hardware
> offloading logic of nic chip. Moreover, ipac-ng counts only ipv4
> traffic, whereas hardware counts all transmitted traffic including ipv6,
> ppp etc. But in practice, if you use ipv4 only, hardware and software
> counters must closely match.
>
> In general, different points of traffic counting is a big problem in
> disputes with ISPs. Your and ISP traffic counters can't be equal.
> Suppose you detached incoming internet cable at all and expect your
> incoming traffic to be zero. Nevertheless ISP will count some traffic in
> your direction at that period. This traffic will include data sent to
> your IP address from whole internet. Of course, this traffic was not
> received, but it was sent! In case of purposeful attack the amount of
> such traffic may be very big, and you can't do anything with it except
> ask ISP to block attacker at ISP level.
>
>  > Another question I have is if the internet went down at 14:03 and then
>  > fetchipac is called at 14:05 and the internet was still down at 14:10
>  > when fetchipac gets called again, the counters would not have changed
>  > as the internet is down but will that data be counted twice?
>
> No, that data will be counted once.
>
> Sergey Merzlikin
>
> 25.02.2016 6:09, Matthew ?????:
>> Hello Sergey,
>>
>>
>>> Maybe your ISP counts PPP traffic, but not traffic inside PPPoE tunnel?
>> For off-peak period my ISP is meant to be counting data from 01:00:00
>> to 09:00:00 (8 Hours) but based on my initial research using ipac-ng
>> they appear to be counting data from 04:00:00 to 16:00::00 (12 hours
>> long) so I think they may be overlapping peak and off-peak data and so
>> are counting some data twice.
>>
>>
>>> You can compare traffic from ifconfig output with ipacsum output to
>>> estimate accuracy of ipac-ng.
>> What situations could cause ipac-ng to be inaccurate?
>>
>>
>>> As far as you don't reload iptables the accounting must be accurate. If
>>> you reload iptables (for example as reaction on some interface up
>>> event), you will lose traffic accounting data between last call of
>>> fetchipac (before reloading) and subsequent fetchipac -s (after reloading).
>> I found out that this was occuring and so I was losing some accounting
>> data in certain situations.
>>
>>
>> I edited /etc/init.d/firewall to log to a file everytime iptables was
>> started or stopped:
>> <cut>
>> start() {
>>           echo `date +"%Y-%m-%d %H:%M:%S"` firewall start >>
>> /var/log/firewall.log
>>           <cut>
>> stop() {
>>           echo `date +"%Y-%m-%d %H:%M:%S"` firewall stop >>
>> /var/log/firewall.log
>>           <cut>
>>
>>
>> I found out firewall stop was never called even on a reboot and so
>> currently I would be losing some accounting data if I shutdown or
>> rebooted the linux box. I also found out that if ppp0 went down the
>> firewall was started again after some time(call to fetchipac -s) and
>> so I could be losing data there also. I know I would not be losing
>> much data as I rarely shutdown or reboot my linux box and my internet
>> usually has uptimes in weeks at a time but still I will fix it so that
>> no accounting data is lost.
>>
>>
>> I need to make sure I call fetchipac everytime the ppp0 interface goes
>> down. I noticed in the logs:
>> Feb 25 13:23:15 wilber14 NET[4157]:
>> /etc/sysconfig/network-scripts/ifdown-post : updated
>> /etc/resolv-peerdns.conf
>> ^ That this occurs as soon as ppp0 goes down. I will look into this.
>>
>>
>> Another question I have is if the internet went down at 14:03 and then
>> fetchipac is called at 14:05 and the internet was still down at 14:10
>> when fetchipac gets called again, the counters would not have changed
>> as the internet is down but will that data be counted twice?
>>
>> Kind regards,
>> Matthew
>>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> _______________________________________________
> Ipac-ng-common mailing list
> Ipa...@li...
> https://lists.sourceforge.net/lists/listinfo/ipac-ng-common
>

Re: [Ipac-ng-common] ipac-ng-1.34.2 data accounting discrepancy

[Sergey M. <sm...@sm...>]

Hello, Matthew.

 > What situations could cause ipac-ng to be inaccurate?
 >
Ifconfig shows traffic counted by hardware or driver, whereas ipac-ng 
shows traffic counted by linux kernel. These are different points of 
traffic flow, so counted traffic may differ. In particular, some packets 
may be silently dropped or silently retransmitted due to hardware 
offloading logic of nic chip. Moreover, ipac-ng counts only ipv4 
traffic, whereas hardware counts all transmitted traffic including ipv6, 
ppp etc. But in practice, if you use ipv4 only, hardware and software 
counters must closely match.

In general, different points of traffic counting is a big problem in 
disputes with ISPs. Your and ISP traffic counters can't be equal. 
Suppose you detached incoming internet cable at all and expect your 
incoming traffic to be zero. Nevertheless ISP will count some traffic in 
your direction at that period. This traffic will include data sent to 
your IP address from whole internet. Of course, this traffic was not 
received, but it was sent! In case of purposeful attack the amount of 
such traffic may be very big, and you can't do anything with it except 
ask ISP to block attacker at ISP level.

 > Another question I have is if the internet went down at 14:03 and then
 > fetchipac is called at 14:05 and the internet was still down at 14:10
 > when fetchipac gets called again, the counters would not have changed
 > as the internet is down but will that data be counted twice?

No, that data will be counted once.

Sergey Merzlikin

25.02.2016 6:09, Matthew пишет:
> Hello Sergey,
>
>
>> Maybe your ISP counts PPP traffic, but not traffic inside PPPoE tunnel?
> For off-peak period my ISP is meant to be counting data from 01:00:00
> to 09:00:00 (8 Hours) but based on my initial research using ipac-ng
> they appear to be counting data from 04:00:00 to 16:00::00 (12 hours
> long) so I think they may be overlapping peak and off-peak data and so
> are counting some data twice.
>
>
>> You can compare traffic from ifconfig output with ipacsum output to
>> estimate accuracy of ipac-ng.
> What situations could cause ipac-ng to be inaccurate?
>
>
>> As far as you don't reload iptables the accounting must be accurate. If
>> you reload iptables (for example as reaction on some interface up
>> event), you will lose traffic accounting data between last call of
>> fetchipac (before reloading) and subsequent fetchipac -s (after reloading).
> I found out that this was occuring and so I was losing some accounting
> data in certain situations.
>
>
> I edited /etc/init.d/firewall to log to a file everytime iptables was
> started or stopped:
> <cut>
> start() {
>           echo `date +"%Y-%m-%d %H:%M:%S"` firewall start >>
> /var/log/firewall.log
>           <cut>
> stop() {
>           echo `date +"%Y-%m-%d %H:%M:%S"` firewall stop >>
> /var/log/firewall.log
>           <cut>
>
>
> I found out firewall stop was never called even on a reboot and so
> currently I would be losing some accounting data if I shutdown or
> rebooted the linux box. I also found out that if ppp0 went down the
> firewall was started again after some time(call to fetchipac -s) and
> so I could be losing data there also. I know I would not be losing
> much data as I rarely shutdown or reboot my linux box and my internet
> usually has uptimes in weeks at a time but still I will fix it so that
> no accounting data is lost.
>
>
> I need to make sure I call fetchipac everytime the ppp0 interface goes
> down. I noticed in the logs:
> Feb 25 13:23:15 wilber14 NET[4157]:
> /etc/sysconfig/network-scripts/ifdown-post : updated
> /etc/resolv-peerdns.conf
> ^ That this occurs as soon as ppp0 goes down. I will look into this.
>
>
> Another question I have is if the internet went down at 14:03 and then
> fetchipac is called at 14:05 and the internet was still down at 14:10
> when fetchipac gets called again, the counters would not have changed
> as the internet is down but will that data be counted twice?
>
> Kind regards,
> Matthew
>

Re: [Ipac-ng-common] ipac-ng-1.34.2 data accounting discrepancy

[Matthew <ipa...@wi...>]

Hello Sergey,


> Maybe your ISP counts PPP traffic, but not traffic inside PPPoE tunnel?
For off-peak period my ISP is meant to be counting data from 01:00:00
to 09:00:00 (8 Hours) but based on my initial research using ipac-ng  
they appear to be counting data from 04:00:00 to 16:00::00 (12 hours  
long) so I think they may be overlapping peak and off-peak data and so  
are counting some data twice.


> You can compare traffic from ifconfig output with ipacsum output to
> estimate accuracy of ipac-ng.
What situations could cause ipac-ng to be inaccurate?


> As far as you don't reload iptables the accounting must be accurate. If
> you reload iptables (for example as reaction on some interface up
> event), you will lose traffic accounting data between last call of
> fetchipac (before reloading) and subsequent fetchipac -s (after reloading).
I found out that this was occuring and so I was losing some accounting  
data in certain situations.


I edited /etc/init.d/firewall to log to a file everytime iptables was  
started or stopped:
<cut>
start() {
         echo `date +"%Y-%m-%d %H:%M:%S"` firewall start >>  
/var/log/firewall.log
         <cut>
stop() {
         echo `date +"%Y-%m-%d %H:%M:%S"` firewall stop >>  
/var/log/firewall.log
         <cut>


I found out firewall stop was never called even on a reboot and so  
currently I would be losing some accounting data if I shutdown or  
rebooted the linux box. I also found out that if ppp0 went down the  
firewall was started again after some time(call to fetchipac -s) and  
so I could be losing data there also. I know I would not be losing  
much data as I rarely shutdown or reboot my linux box and my internet  
usually has uptimes in weeks at a time but still I will fix it so that  
no accounting data is lost.


I need to make sure I call fetchipac everytime the ppp0 interface goes  
down. I noticed in the logs:
Feb 25 13:23:15 wilber14 NET[4157]:  
/etc/sysconfig/network-scripts/ifdown-post : updated  
/etc/resolv-peerdns.conf
^ That this occurs as soon as ppp0 goes down. I will look into this.


Another question I have is if the internet went down at 14:03 and then  
fetchipac is called at 14:05 and the internet was still down at 14:10  
when fetchipac gets called again, the counters would not have changed  
as the internet is down but will that data be counted twice?

Kind regards,
Matthew



Quoting "Sergey Merzlikin" <sm...@sm...>:

> Hello, Matthew.
>
> Maybe your ISP counts PPP traffic, but not traffic inside PPPoE tunnel?
>
> You can compare traffic from ifconfig output with ipacsum output to
> estimate accuracy of ipac-ng.
>
>  > /etc/ipac-ng/rules.conf
>  > 0ppp0 RX fm inet passthru wilber14|ipac~fi|ppp0|all||||
>  > 1ppp0 RX fm inet to wilber14|ipac~o|ppp0|all||||
>  > 2ppp0 TX to inet passthru wilber14|ipac~fo|ppp0|all||||
>  > 3ppp0 TX to inet from wilber14|ipac~i|ppp0|all||||
>  >
>  > ^ Q1. Will those 4 rules above capture all the traffic that is passing
>  > through the ppp0 internet inferface in both directions(download and
>  > upload)?
>
> Yes, these rules appears correct.
>
>  > ^ Q2. I am saving the IP accounting info on every shutdown/reboot as
>  > well as any time the internet connection drops. So if the cron job
>  > saved the IP info at 13:15 and then the internet drops at 13:17 and
>  > saves the IP info save then and comes back up again and so then the
>  > next cron job saves the IP info at 13:20 will that mess up any
>  > internal accounting?
>  >
>
> As far as you don't reload iptables the accounting must be accurate. If
> you reload iptables (for example as reaction on some interface up
> event), you will lose traffic accounting data between last call of
> fetchipac (before reloading) and subsequent fetchipac -s (after reloading).
>
>  > ^ Q3. Are there any known bugs/issues with ipac-ng-1.34.2.tar.gz using
>  > iptables that would cause some data to be missed or not counted?
>  >
>
> No. As far as fetchipac compiles and doesn't produce segfaults, it is
> compatible with particular Linux. In development version I fixed
> compatibility with newer iptables and some specific things discussed
> here earlier.
>
> Sergey Merzlikin
>
> 24.02.2016 5:34, Matthew ?????:
>> I've been using ipac-ng since late December 2015 but wiped the
>> database in January to coincide with my ISP's monthly quota. Towards
>> the end of the billing cycle when I compared my usage records using
>> ipac-ng against theirs we differed by as much as 10GB!
>>
>> My ISP counts data for both downloads and uploads in both peak as well
>> as off-peak time periods. So by totalling their 4 figures(offpeak down
>> and up and peak down and up) a total data usage for the day can be
>> obtained which can be compared against ipac-ng's 4 figures(two for
>> download and two for upload).
>>
>> I wrote to their billing department and they wrote back:
>> "Your usage records in our Exetel member's facility are according to
>> our supplier records and those records are accurate."
>>
>> I wrote to their provisioning department and they just forwarded on
>> the email to their support department. At least the support department
>> has been a lot more helpful:
>> "However I cross checked the usage records with our internal records
>> and it looks similar."
>> "There is no configuration errors from our end and the usage meter is
>> correct in both ends. Could you please provide us usage logs with time
>> stamps from your equipment as you mentioned so we can investigate
>> further."
>>
>>
>>
>>
>> Before I send off to them all my usage logs I just wanted to make sure
>> that there is nothing wrong with my setup and the way I have been
>> using ipac-ng as well as make sure that there are no known bugs or
>> issues which would cause us to be 10GB apart in data usage over a month.
>>
>> My linux box has two ethernet ports and I have an ADSL modem which is
>> setup in bridge mode and connected to eth0, eth1 connects to my
>> internal lan. I use Roaring Penguin PPPoE
>> client(rp-pppoe-3.10-11.v6.i686) which creates the ppp0 interface when
>> the internet connection is active. I'm using ipac-ng-1.34.2.tar.gz on
>> kernel-2.6.32-573.1.1.v6.i686 with iptables-1.4.7-16.v6.i686. Some
>> relevant configs and output:
>>
>> /etc/sysconfig/network-scripts/ifcfg-eth0
>> DEVICE=eth0
>> BOOTPROTO="none"
>> ONBOOT="no"
>>
>>
>>
>> /sbin/ifconfig
>> eth0      Link encap:Ethernet  HWaddr 00:18:8B:26:3B:12
>>             UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>             RX packets:21443703 errors:0 dropped:0 overruns:0 frame:0
>>             TX packets:13858182 errors:0 dropped:0 overruns:0 carrier:0
>>             collisions:0 txqueuelen:1000
>>             RX bytes:28286567926 (26.3 GiB)  TX bytes:1465986694 (1.3 GiB)
>>             Interrupt:16
>>
>> ppp0      Link encap:Point-to-Point Protocol
>>             inet addr:220.233.87.133  P-t-P:220.233.1.150   
>> Mask:255.255.255.255
>>             UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
>>             RX packets:21372091 errors:0 dropped:0 overruns:0 frame:0
>>             TX packets:13792777 errors:0 dropped:0 overruns:0 carrier:0
>>             collisions:0 txqueuelen:3
>>             RX bytes:27726182866 (25.8 GiB)  TX bytes:1103069366 (1.0 GiB)
>>
>>
>>
>> /etc/ipac-ng/rules.conf
>> 0ppp0 RX fm inet passthru wilber14|ipac~fi|ppp0|all||||
>> 1ppp0 RX fm inet to wilber14|ipac~o|ppp0|all||||
>> 2ppp0 TX to inet passthru wilber14|ipac~fo|ppp0|all||||
>> 3ppp0 TX to inet from wilber14|ipac~i|ppp0|all||||
>>
>> ^ Q1. Will those 4 rules above capture all the traffic that is passing
>> through the ppp0 internet inferface in both directions(download and
>> upload)?
>>
>>
>> /etc/crontab
>> # Save IP accounting info for ipacsum every five minutes.
>> */5 * * * * root /usr/local/sbin/fetchipac
>>
>> ^ I'm not running any cron jobs to summarise the ip accounting info.
>> So I still have all the accounting information between 2016/01/14
>> 10:05:01 AEDT to 2016/02/24 13:06:05 AEDT.
>>
>>
>> /etc/init.d/firewall
>> start() {
>> <cut>
>>           # Switch on ip accounting
>>           /usr/local/sbin/fetchipac -S
>> }
>>
>> stop() {
>>           # Save IP accounting
>>           /usr/local/sbin/fetchipac
>> <cut>
>>
>> ^ Q2. I am saving the IP accounting info on every shutdown/reboot as
>> well as any time the internet connection drops. So if the cron job
>> saved the IP info at 13:15 and then the internet drops at 13:17 and
>> saves the IP info save then and comes back up again and so then the
>> next cron job saves the IP info at 13:20 will that mess up any
>> internal accounting?
>>
>>
>> [quote]
>> I recommend to download current development tarball, it contains some
>> fixes to iptables support:
>> http://ipac-ng.cvs.sourceforge.net/viewvc/ipac-ng/ipac-ng/?view=tar
>>
>> Sergey Merzlikin
>> [/quote]
>>
>> ^ Q3. Are there any known bugs/issues with ipac-ng-1.34.2.tar.gz using
>> iptables that would cause some data to be missed or not counted?
>>
>>
>> Any help would be greatly appreciated.
>>
>> Thanking you,
>> Matthew
>>
>> ------------------------------------------------------------------------------
>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>> Monitor end-to-end web transactions and take corrective actions now
>> Troubleshoot faster and improve end-user experience. Signup Now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
>> _______________________________________________
>> Ipac-ng-common mailing list
>> Ipa...@li...
>> https://lists.sourceforge.net/lists/listinfo/ipac-ng-common
>>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> _______________________________________________
> Ipac-ng-common mailing list
> Ipa...@li...
> https://lists.sourceforge.net/lists/listinfo/ipac-ng-common
>

Re: [Ipac-ng-common] ipac-ng-1.34.2 data accounting discrepancy

[Sergey M. <sm...@sm...>]

Hello, Matthew.

Maybe your ISP counts PPP traffic, but not traffic inside PPPoE tunnel?

You can compare traffic from ifconfig output with ipacsum output to 
estimate accuracy of ipac-ng.

 > /etc/ipac-ng/rules.conf
 > 0ppp0 RX fm inet passthru wilber14|ipac~fi|ppp0|all||||
 > 1ppp0 RX fm inet to wilber14|ipac~o|ppp0|all||||
 > 2ppp0 TX to inet passthru wilber14|ipac~fo|ppp0|all||||
 > 3ppp0 TX to inet from wilber14|ipac~i|ppp0|all||||
 >
 > ^ Q1. Will those 4 rules above capture all the traffic that is passing
 > through the ppp0 internet inferface in both directions(download and
 > upload)?

Yes, these rules appears correct.

 > ^ Q2. I am saving the IP accounting info on every shutdown/reboot as
 > well as any time the internet connection drops. So if the cron job
 > saved the IP info at 13:15 and then the internet drops at 13:17 and
 > saves the IP info save then and comes back up again and so then the
 > next cron job saves the IP info at 13:20 will that mess up any
 > internal accounting?
 >

As far as you don't reload iptables the accounting must be accurate. If 
you reload iptables (for example as reaction on some interface up 
event), you will lose traffic accounting data between last call of 
fetchipac (before reloading) and subsequent fetchipac -s (after reloading).

 > ^ Q3. Are there any known bugs/issues with ipac-ng-1.34.2.tar.gz using
 > iptables that would cause some data to be missed or not counted?
 >

No. As far as fetchipac compiles and doesn't produce segfaults, it is 
compatible with particular Linux. In development version I fixed 
compatibility with newer iptables and some specific things discussed 
here earlier.

Sergey Merzlikin

24.02.2016 5:34, Matthew пишет:
> I've been using ipac-ng since late December 2015 but wiped the
> database in January to coincide with my ISP's monthly quota. Towards
> the end of the billing cycle when I compared my usage records using
> ipac-ng against theirs we differed by as much as 10GB!
>
> My ISP counts data for both downloads and uploads in both peak as well
> as off-peak time periods. So by totalling their 4 figures(offpeak down
> and up and peak down and up) a total data usage for the day can be
> obtained which can be compared against ipac-ng's 4 figures(two for
> download and two for upload).
>
> I wrote to their billing department and they wrote back:
> "Your usage records in our Exetel member's facility are according to
> our supplier records and those records are accurate."
>
> I wrote to their provisioning department and they just forwarded on
> the email to their support department. At least the support department
> has been a lot more helpful:
> "However I cross checked the usage records with our internal records
> and it looks similar."
> "There is no configuration errors from our end and the usage meter is
> correct in both ends. Could you please provide us usage logs with time
> stamps from your equipment as you mentioned so we can investigate
> further."
>
>
>
>
> Before I send off to them all my usage logs I just wanted to make sure
> that there is nothing wrong with my setup and the way I have been
> using ipac-ng as well as make sure that there are no known bugs or
> issues which would cause us to be 10GB apart in data usage over a month.
>
> My linux box has two ethernet ports and I have an ADSL modem which is
> setup in bridge mode and connected to eth0, eth1 connects to my
> internal lan. I use Roaring Penguin PPPoE
> client(rp-pppoe-3.10-11.v6.i686) which creates the ppp0 interface when
> the internet connection is active. I'm using ipac-ng-1.34.2.tar.gz on
> kernel-2.6.32-573.1.1.v6.i686 with iptables-1.4.7-16.v6.i686. Some
> relevant configs and output:
>
> /etc/sysconfig/network-scripts/ifcfg-eth0
> DEVICE=eth0
> BOOTPROTO="none"
> ONBOOT="no"
>
>
>
> /sbin/ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:18:8B:26:3B:12
>             UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>             RX packets:21443703 errors:0 dropped:0 overruns:0 frame:0
>             TX packets:13858182 errors:0 dropped:0 overruns:0 carrier:0
>             collisions:0 txqueuelen:1000
>             RX bytes:28286567926 (26.3 GiB)  TX bytes:1465986694 (1.3 GiB)
>             Interrupt:16
>
> ppp0      Link encap:Point-to-Point Protocol
>             inet addr:220.233.87.133  P-t-P:220.233.1.150  Mask:255.255.255.255
>             UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
>             RX packets:21372091 errors:0 dropped:0 overruns:0 frame:0
>             TX packets:13792777 errors:0 dropped:0 overruns:0 carrier:0
>             collisions:0 txqueuelen:3
>             RX bytes:27726182866 (25.8 GiB)  TX bytes:1103069366 (1.0 GiB)
>
>
>
> /etc/ipac-ng/rules.conf
> 0ppp0 RX fm inet passthru wilber14|ipac~fi|ppp0|all||||
> 1ppp0 RX fm inet to wilber14|ipac~o|ppp0|all||||
> 2ppp0 TX to inet passthru wilber14|ipac~fo|ppp0|all||||
> 3ppp0 TX to inet from wilber14|ipac~i|ppp0|all||||
>
> ^ Q1. Will those 4 rules above capture all the traffic that is passing
> through the ppp0 internet inferface in both directions(download and
> upload)?
>
>
> /etc/crontab
> # Save IP accounting info for ipacsum every five minutes.
> */5 * * * * root /usr/local/sbin/fetchipac
>
> ^ I'm not running any cron jobs to summarise the ip accounting info.
> So I still have all the accounting information between 2016/01/14
> 10:05:01 AEDT to 2016/02/24 13:06:05 AEDT.
>
>
> /etc/init.d/firewall
> start() {
> <cut>
>           # Switch on ip accounting
>           /usr/local/sbin/fetchipac -S
> }
>
> stop() {
>           # Save IP accounting
>           /usr/local/sbin/fetchipac
> <cut>
>
> ^ Q2. I am saving the IP accounting info on every shutdown/reboot as
> well as any time the internet connection drops. So if the cron job
> saved the IP info at 13:15 and then the internet drops at 13:17 and
> saves the IP info save then and comes back up again and so then the
> next cron job saves the IP info at 13:20 will that mess up any
> internal accounting?
>
>
> [quote]
> I recommend to download current development tarball, it contains some
> fixes to iptables support:
> http://ipac-ng.cvs.sourceforge.net/viewvc/ipac-ng/ipac-ng/?view=tar
>
> Sergey Merzlikin
> [/quote]
>
> ^ Q3. Are there any known bugs/issues with ipac-ng-1.34.2.tar.gz using
> iptables that would cause some data to be missed or not counted?
>
>
> Any help would be greatly appreciated.
>
> Thanking you,
> Matthew
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> _______________________________________________
> Ipac-ng-common mailing list
> Ipa...@li...
> https://lists.sourceforge.net/lists/listinfo/ipac-ng-common
>

[Ipac-ng-common] ipac-ng-1.34.2 data accounting discrepancy

[Matthew <ipa...@wi...>]

I've been using ipac-ng since late December 2015 but wiped the  
database in January to coincide with my ISP's monthly quota. Towards  
the end of the billing cycle when I compared my usage records using  
ipac-ng against theirs we differed by as much as 10GB!

My ISP counts data for both downloads and uploads in both peak as well  
as off-peak time periods. So by totalling their 4 figures(offpeak down  
and up and peak down and up) a total data usage for the day can be  
obtained which can be compared against ipac-ng's 4 figures(two for  
download and two for upload).

I wrote to their billing department and they wrote back:
"Your usage records in our Exetel member's facility are according to  
our supplier records and those records are accurate."

I wrote to their provisioning department and they just forwarded on  
the email to their support department. At least the support department  
has been a lot more helpful:
"However I cross checked the usage records with our internal records  
and it looks similar."
"There is no configuration errors from our end and the usage meter is  
correct in both ends. Could you please provide us usage logs with time  
stamps from your equipment as you mentioned so we can investigate  
further."




Before I send off to them all my usage logs I just wanted to make sure  
that there is nothing wrong with my setup and the way I have been  
using ipac-ng as well as make sure that there are no known bugs or  
issues which would cause us to be 10GB apart in data usage over a month.

My linux box has two ethernet ports and I have an ADSL modem which is  
setup in bridge mode and connected to eth0, eth1 connects to my  
internal lan. I use Roaring Penguin PPPoE  
client(rp-pppoe-3.10-11.v6.i686) which creates the ppp0 interface when  
the internet connection is active. I'm using ipac-ng-1.34.2.tar.gz on  
kernel-2.6.32-573.1.1.v6.i686 with iptables-1.4.7-16.v6.i686. Some  
relevant configs and output:

/etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO="none"
ONBOOT="no"



/sbin/ifconfig
eth0      Link encap:Ethernet  HWaddr 00:18:8B:26:3B:12
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:21443703 errors:0 dropped:0 overruns:0 frame:0
           TX packets:13858182 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:28286567926 (26.3 GiB)  TX bytes:1465986694 (1.3 GiB)
           Interrupt:16

ppp0      Link encap:Point-to-Point Protocol
           inet addr:220.233.87.133  P-t-P:220.233.1.150  Mask:255.255.255.255
           UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
           RX packets:21372091 errors:0 dropped:0 overruns:0 frame:0
           TX packets:13792777 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:3
           RX bytes:27726182866 (25.8 GiB)  TX bytes:1103069366 (1.0 GiB)



/etc/ipac-ng/rules.conf
0ppp0 RX fm inet passthru wilber14|ipac~fi|ppp0|all||||
1ppp0 RX fm inet to wilber14|ipac~o|ppp0|all||||
2ppp0 TX to inet passthru wilber14|ipac~fo|ppp0|all||||
3ppp0 TX to inet from wilber14|ipac~i|ppp0|all||||

^ Q1. Will those 4 rules above capture all the traffic that is passing  
through the ppp0 internet inferface in both directions(download and  
upload)?


/etc/crontab
# Save IP accounting info for ipacsum every five minutes.
*/5 * * * * root /usr/local/sbin/fetchipac

^ I'm not running any cron jobs to summarise the ip accounting info.  
So I still have all the accounting information between 2016/01/14  
10:05:01 AEDT to 2016/02/24 13:06:05 AEDT.


/etc/init.d/firewall
start() {
<cut>
         # Switch on ip accounting
         /usr/local/sbin/fetchipac -S
}

stop() {
         # Save IP accounting
         /usr/local/sbin/fetchipac
<cut>

^ Q2. I am saving the IP accounting info on every shutdown/reboot as  
well as any time the internet connection drops. So if the cron job  
saved the IP info at 13:15 and then the internet drops at 13:17 and  
saves the IP info save then and comes back up again and so then the  
next cron job saves the IP info at 13:20 will that mess up any  
internal accounting?


[quote]
I recommend to download current development tarball, it contains some
fixes to iptables support:
http://ipac-ng.cvs.sourceforge.net/viewvc/ipac-ng/ipac-ng/?view=tar

Sergey Merzlikin
[/quote]

^ Q3. Are there any known bugs/issues with ipac-ng-1.34.2.tar.gz using  
iptables that would cause some data to be missed or not counted?


Any help would be greatly appreciated.

Thanking you,
Matthew

Re: [Ipac-ng-common] ipac-ng-1.34.2 can't find mysql and other compile time conflicts and warnings

[Sergey M. <sm...@sm...>]

Hello, Matthew.

For some reason configure script can't find MySQL client library in 
RedHat-based Linuxes.

Try ./configure LDFLAGS="-L/usr/lib/mysql"

Yes, there are some warnings while configuration and compilation not 
affecting result.

I recommend to download current development tarball, it contains some 
fixes to iptables support: 
http://ipac-ng.cvs.sourceforge.net/viewvc/ipac-ng/ipac-ng/?view=tar

Sergey Merzlikin

26.12.2015 4:43, Matthew пишет:
> Hi,
>
> I downloaded ipac-ng-1.34.2 and during the configure process it
> complains that it can't find mysql:
> [ ipac-ng]# ./configure
> checking for mysql_query in -lmysqlclient... no
> configure: WARNING: mysql library not found!
>           support for optional storage "mysql" will be disabled
> checking for sqlite_get_table in -lsqlite... yes
> [ ipac-ng]#
>
>
>
> I've already installed almost all the mysql rpms using:
> [ ~]# yum install `yum search mysql | grep noarch | grep -v zabbix |
> cut -d ":" -f 1`
> ^ I did something similar for the i686 rpms as well.
>
>
> I'm using ClearOS 6.5.0 which is built on top of CentOS/RedHat. Here
> is a list of mysql rpms that I have installed:
> [ ~]# rpm -qa | grep -i mysql | sort
> app-mysql-1.7.0-1.v6.noarch
> app-mysql-core-1.7.0-1.v6.noarch
> apr-util-mysql-1.3.9-3.el6_0.1.i686
> dmlite-plugins-mysql-0.7.5-1.el6.i686
> dspam-mysql-3.10.2-7.el6.i686
> holland-mysqldump-1.0.10-3.el6.noarch
> holland-mysqllvm-1.0.10-3.el6.noarch
> libdbi-dbd-mysql-0.8.3-5.1.el6.i686
> libnss-mysql-1.5-12.el6.i686
> libodb-mysql-2.3.0-1.el6.i686
> libodb-mysql-devel-2.3.0-1.el6.i686
> lua-sql-mysql-2.1.1-7.el6.i686
> mod_auth_mysql-3.0.0-11.el6_0.1.i686
> mysql++-3.0.9-3.el6.i686
> mysql-5.1.73-5.el6_6.i686
> mysql-bench-5.1.73-5.el6_6.i686
> mysql-connector-java-5.1.17-6.el6.noarch
> mysql-connector-odbc-5.1.5r1144-7.el6.i686
> mysql-connector-python-1.1.6-1.el6.noarch
> mysql++-devel-3.0.9-3.el6.i686
> mysql-devel-5.1.73-5.el6_6.i686
> mysql-embedded-5.1.73-5.el6_6.i686
> mysql-embedded-devel-5.1.73-5.el6_6.i686
> mysql-libs-5.1.73-5.el6_6.i686
> mysql++-manuals-3.0.9-3.el6.i686
> mysql-mmm-2.2.1-2.el6.noarch
> mysql-mmm-agent-2.2.1-2.el6.noarch
> mysql-mmm-monitor-2.2.1-2.el6.noarch
> mysql-mmm-tools-2.2.1-2.el6.noarch
> mysql-proxy-0.8.5-1.el6.i686
> mysql-proxy-devel-0.8.5-1.el6.i686
> MySQL-python-1.2.3-0.3.c1.1.el6.i686
> mysqlreport-3.5-4.el6.noarch
> mysql-server-5.1.73-5.el6_6.i686
> mysql-test-5.1.73-5.el6_6.i686
> mysqltuner-1.1.1-1.el6.noarch
> mysql-utilities-1.3.6-1.el6.noarch
> MySQL-zrm-3.0-6.el6.noarch
> nagios-plugins-mysql-2.0.3-3.el6.i686
> ndoutils-mysql-1.5.2-1.el6.i686
> nodejs-mysql-2.0.0-alpha9.2.el6.2.noarch
> opendbx-mysql-1.4.6-6.el6.i686
> openscada-DB-MySQL-0.7.2-1.el6.i686
> owncloud-mysql-7.0.11-1.el6.noarch
> pam_mysql-0.7-0.12.rc1.el6.i686
> perl-Class-DBI-mysql-1.00-7.el6.noarch
> perl-Config-Extend-MySQL-0.04-1.el6.noarch
> perl-DateTime-Format-MySQL-0.04-8.el6.noarch
> perl-DBD-MySQL-4.013-3.el6.i686
> perl-Test-mysqld-0.17-3.el6.noarch
> perl-Time-Piece-MySQL-0.05-8.el6.noarch
> php-mysql-5.3.3-46.el6_6.i686
> php-pear-MDB2-Driver-mysql-1.5.0-0.8.b4.el6.noarch
> php-pear-MDB2-Driver-mysqli-1.5.0-0.8.b4.el6.noarch
> php-ZendFramework-Db-Adapter-Mysqli-1.12.13-1.el6.noarch
> php-ZendFramework-Db-Adapter-Pdo-Mysql-1.12.13-1.el6.noarch
> poco-mysql-1.4.2p1-2.el6.i686
> pyicq-t-mysql-0.8.1.5-5.el6.noarch
> qt3-MySQL-3.3.8b-30.el6.i686
> qt5-qtbase-mysql-5.5.1-2.el6.i686
> qt-mysql-4.6.2-28.el6_5.i686
> rekall-mysql-2.4.6-13.el6.i686
> ruby-mysql-2.8.2-1.el6.i686
> soci-mysql-3.2.2-2.el6.i686
> soci-mysql-devel-3.2.2-2.el6.i686
> system-mysql-5.1.73-3.v6.1.i686
> system-mysql-bench-5.1.73-3.v6.1.i686
> system-mysql-devel-5.1.73-3.v6.1.i686
> system-mysql-embedded-5.1.73-3.v6.1.i686
> system-mysql-embedded-devel-5.1.73-3.v6.1.i686
> system-mysql-libs-5.1.73-3.v6.1.i686
> system-mysql-server-5.1.73-3.v6.1.i686
> system-mysql-test-5.1.73-3.v6.1.i686
> tcl-mysqltcl-3.05-8.el6.i686
> trytond-mysql-1.8.10-1.el6.noarch
> webconfig-php-mysql-5.3.3-27.v6.1.i686
> [  ~]#
>
>
> Here is mysqlclient:
> [ ipac-ng]# locate mysqlclient
> /usr/clearos/sandbox/usr/lib/mysql/libmysqlclient.so
> /usr/clearos/sandbox/usr/lib/mysql/libmysqlclient.so.16
> /usr/clearos/sandbox/usr/lib/mysql/libmysqlclient.so.16.0.0
> /usr/clearos/sandbox/usr/lib/mysql/libmysqlclient_r.so
> /usr/clearos/sandbox/usr/lib/mysql/libmysqlclient_r.so.16
> /usr/clearos/sandbox/usr/lib/mysql/libmysqlclient_r.so.16.0.0
> /usr/lib/mysql/libmysqlclient.so
> /usr/lib/mysql/libmysqlclient.so.16
> /usr/lib/mysql/libmysqlclient.so.16.0.0
> /usr/lib/mysql/libmysqlclient_r.so
> /usr/lib/mysql/libmysqlclient_r.so.16
> /usr/lib/mysql/libmysqlclient_r.so.16.0.0
> [ ipac-ng]#
>
>
>
> During the compile there were some conflicts and warnings:
> [ ipac-ng]# make
> gdbm.c:116: warning: initialization from incompatible pointer type
> gdbm.c:117: warning: initialization from incompatible pointer type
>
> make[2]: Entering directory `/root/ipac-ng/access/files'
> gcc -c -I. -I../.. -DHAVE_CONFIG_H -g -O2 -Wall -I/usr/include/pgsql
> files.c -o files.o
> bison -y -d -b rules -p rules rules.y
> conflicts: 1 shift/reduce, 4 reduce/reduce
> rules.y:59.15-62.13: warning: rule useless in parser due to conflicts:
> command: error
> gcc -c -I. -I../.. -DHAVE_CONFIG_H -g -O2 -Wall -I/usr/include/pgsql
> rules.tab.c -o rules.tab.o
> rules.y: In function âprint_extâ:
> rules.y:264: warning: initialization from incompatible pointer type
> rules.y: At top level:
> rules.y:262: warning: âprint_extâ defined but not used
>
> gcc -c -I. -I../.. -DHAVE_CONFIG_H -g -O2 -Wall -I/usr/include/pgsql
> rules.yy.c -o rules.yy.o
> rules.yy.c:1293: warning: âyyunputâ defined but not used
> rules.yy.c:1334: warning: âinputâ defined but not used
> rules.yy.c:1789: warning: âyy_top_stateâ defined but not used
>
> gcc -c -DHAVE_CONFIG_H -DINSTALLPATH=\"/usr/local/sbin\" -g -O2 -Wall
> -I/usr/include/pgsql batch.yy.c -o batch.yy.o
> batch.yy.c:1200: warning: âinputâ defined but not used
>
> gcc -c -DHAVE_CONFIG_H -DINSTALLPATH=\"/usr/local/sbin\" -g -O2 -Wall
> -I/usr/include/pgsql conffile.yy.c -o conffile.yy.o
> conffile.yy.c:1328: warning: âinputâ defined but not used
> [ ipac-ng]#
>
>
>
> Any help with this would be greatly appreciated.
>
> Thanking you,
> Matthew
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Ipac-ng-common mailing list
> Ipa...@li...
> https://lists.sourceforge.net/lists/listinfo/ipac-ng-common
>

Re: [Ipac-ng-common] ipac-ng-1.34.2 can't find mysql and other compile time conflicts and warnings

[Matthew <ipa...@wi...>]

In addition to the above, this was another configure warning:
configure: creating ./config.status
config.status: creating Makefile
config.status: WARNING:  'Makefile.in' seems to ignore the  
--datarootdir setting

[Ipac-ng-common] ipac-ng-1.34.2 can't find mysql and other compile time conflicts and warnings

[Matthew <ipa...@wi...>]

Hi,

I downloaded ipac-ng-1.34.2 and during the configure process it  
complains that it can't find mysql:
[ ipac-ng]# ./configure
checking for mysql_query in -lmysqlclient... no
configure: WARNING: mysql library not found!
         support for optional storage "mysql" will be disabled
checking for sqlite_get_table in -lsqlite... yes
[ ipac-ng]#



I've already installed almost all the mysql rpms using:
[ ~]# yum install `yum search mysql | grep noarch | grep -v zabbix |  
cut -d ":" -f 1`
^ I did something similar for the i686 rpms as well.


I'm using ClearOS 6.5.0 which is built on top of CentOS/RedHat. Here  
is a list of mysql rpms that I have installed:
[ ~]# rpm -qa | grep -i mysql | sort
app-mysql-1.7.0-1.v6.noarch
app-mysql-core-1.7.0-1.v6.noarch
apr-util-mysql-1.3.9-3.el6_0.1.i686
dmlite-plugins-mysql-0.7.5-1.el6.i686
dspam-mysql-3.10.2-7.el6.i686
holland-mysqldump-1.0.10-3.el6.noarch
holland-mysqllvm-1.0.10-3.el6.noarch
libdbi-dbd-mysql-0.8.3-5.1.el6.i686
libnss-mysql-1.5-12.el6.i686
libodb-mysql-2.3.0-1.el6.i686
libodb-mysql-devel-2.3.0-1.el6.i686
lua-sql-mysql-2.1.1-7.el6.i686
mod_auth_mysql-3.0.0-11.el6_0.1.i686
mysql++-3.0.9-3.el6.i686
mysql-5.1.73-5.el6_6.i686
mysql-bench-5.1.73-5.el6_6.i686
mysql-connector-java-5.1.17-6.el6.noarch
mysql-connector-odbc-5.1.5r1144-7.el6.i686
mysql-connector-python-1.1.6-1.el6.noarch
mysql++-devel-3.0.9-3.el6.i686
mysql-devel-5.1.73-5.el6_6.i686
mysql-embedded-5.1.73-5.el6_6.i686
mysql-embedded-devel-5.1.73-5.el6_6.i686
mysql-libs-5.1.73-5.el6_6.i686
mysql++-manuals-3.0.9-3.el6.i686
mysql-mmm-2.2.1-2.el6.noarch
mysql-mmm-agent-2.2.1-2.el6.noarch
mysql-mmm-monitor-2.2.1-2.el6.noarch
mysql-mmm-tools-2.2.1-2.el6.noarch
mysql-proxy-0.8.5-1.el6.i686
mysql-proxy-devel-0.8.5-1.el6.i686
MySQL-python-1.2.3-0.3.c1.1.el6.i686
mysqlreport-3.5-4.el6.noarch
mysql-server-5.1.73-5.el6_6.i686
mysql-test-5.1.73-5.el6_6.i686
mysqltuner-1.1.1-1.el6.noarch
mysql-utilities-1.3.6-1.el6.noarch
MySQL-zrm-3.0-6.el6.noarch
nagios-plugins-mysql-2.0.3-3.el6.i686
ndoutils-mysql-1.5.2-1.el6.i686
nodejs-mysql-2.0.0-alpha9.2.el6.2.noarch
opendbx-mysql-1.4.6-6.el6.i686
openscada-DB-MySQL-0.7.2-1.el6.i686
owncloud-mysql-7.0.11-1.el6.noarch
pam_mysql-0.7-0.12.rc1.el6.i686
perl-Class-DBI-mysql-1.00-7.el6.noarch
perl-Config-Extend-MySQL-0.04-1.el6.noarch
perl-DateTime-Format-MySQL-0.04-8.el6.noarch
perl-DBD-MySQL-4.013-3.el6.i686
perl-Test-mysqld-0.17-3.el6.noarch
perl-Time-Piece-MySQL-0.05-8.el6.noarch
php-mysql-5.3.3-46.el6_6.i686
php-pear-MDB2-Driver-mysql-1.5.0-0.8.b4.el6.noarch
php-pear-MDB2-Driver-mysqli-1.5.0-0.8.b4.el6.noarch
php-ZendFramework-Db-Adapter-Mysqli-1.12.13-1.el6.noarch
php-ZendFramework-Db-Adapter-Pdo-Mysql-1.12.13-1.el6.noarch
poco-mysql-1.4.2p1-2.el6.i686
pyicq-t-mysql-0.8.1.5-5.el6.noarch
qt3-MySQL-3.3.8b-30.el6.i686
qt5-qtbase-mysql-5.5.1-2.el6.i686
qt-mysql-4.6.2-28.el6_5.i686
rekall-mysql-2.4.6-13.el6.i686
ruby-mysql-2.8.2-1.el6.i686
soci-mysql-3.2.2-2.el6.i686
soci-mysql-devel-3.2.2-2.el6.i686
system-mysql-5.1.73-3.v6.1.i686
system-mysql-bench-5.1.73-3.v6.1.i686
system-mysql-devel-5.1.73-3.v6.1.i686
system-mysql-embedded-5.1.73-3.v6.1.i686
system-mysql-embedded-devel-5.1.73-3.v6.1.i686
system-mysql-libs-5.1.73-3.v6.1.i686
system-mysql-server-5.1.73-3.v6.1.i686
system-mysql-test-5.1.73-3.v6.1.i686
tcl-mysqltcl-3.05-8.el6.i686
trytond-mysql-1.8.10-1.el6.noarch
webconfig-php-mysql-5.3.3-27.v6.1.i686
[  ~]#


Here is mysqlclient:
[ ipac-ng]# locate mysqlclient
/usr/clearos/sandbox/usr/lib/mysql/libmysqlclient.so
/usr/clearos/sandbox/usr/lib/mysql/libmysqlclient.so.16
/usr/clearos/sandbox/usr/lib/mysql/libmysqlclient.so.16.0.0
/usr/clearos/sandbox/usr/lib/mysql/libmysqlclient_r.so
/usr/clearos/sandbox/usr/lib/mysql/libmysqlclient_r.so.16
/usr/clearos/sandbox/usr/lib/mysql/libmysqlclient_r.so.16.0.0
/usr/lib/mysql/libmysqlclient.so
/usr/lib/mysql/libmysqlclient.so.16
/usr/lib/mysql/libmysqlclient.so.16.0.0
/usr/lib/mysql/libmysqlclient_r.so
/usr/lib/mysql/libmysqlclient_r.so.16
/usr/lib/mysql/libmysqlclient_r.so.16.0.0
[ ipac-ng]#



During the compile there were some conflicts and warnings:
[ ipac-ng]# make
gdbm.c:116: warning: initialization from incompatible pointer type
gdbm.c:117: warning: initialization from incompatible pointer type

make[2]: Entering directory `/root/ipac-ng/access/files'
gcc -c -I. -I../.. -DHAVE_CONFIG_H -g -O2 -Wall -I/usr/include/pgsql  
files.c -o files.o
bison -y -d -b rules -p rules rules.y
conflicts: 1 shift/reduce, 4 reduce/reduce
rules.y:59.15-62.13: warning: rule useless in parser due to conflicts:  
command: error
gcc -c -I. -I../.. -DHAVE_CONFIG_H -g -O2 -Wall -I/usr/include/pgsql  
rules.tab.c -o rules.tab.o
rules.y: In function âprint_extâ:
rules.y:264: warning: initialization from incompatible pointer type
rules.y: At top level:
rules.y:262: warning: âprint_extâ defined but not used

gcc -c -I. -I../.. -DHAVE_CONFIG_H -g -O2 -Wall -I/usr/include/pgsql  
rules.yy.c -o rules.yy.o
rules.yy.c:1293: warning: âyyunputâ defined but not used
rules.yy.c:1334: warning: âinputâ defined but not used
rules.yy.c:1789: warning: âyy_top_stateâ defined but not used

gcc -c -DHAVE_CONFIG_H -DINSTALLPATH=\"/usr/local/sbin\" -g -O2 -Wall  
-I/usr/include/pgsql batch.yy.c -o batch.yy.o
batch.yy.c:1200: warning: âinputâ defined but not used

gcc -c -DHAVE_CONFIG_H -DINSTALLPATH=\"/usr/local/sbin\" -g -O2 -Wall  
-I/usr/include/pgsql conffile.yy.c -o conffile.yy.o
conffile.yy.c:1328: warning: âinputâ defined but not used
[ ipac-ng]#



Any help with this would be greatly appreciated.

Thanking you,
Matthew

Re: [Ipac-ng-common] unrecognized option '--mac-source' && sigsev...

[Marco G. <ga...@sv...>]

Mandi! Sergey Merzlikin
  In chel di` si favelave...

> The patch is in attachment.

...i can confirm that works, many thanks!!!

-- 
dott. Marco Gaiarin				        GNUPG Key ID: 240A3D66
  Associazione ``La Nostra Famiglia''                    http://www.sv.lnf.it/
  Polo FVG   -   Via della Bontà, 7 - 33078   -   San Vito al Tagliamento (PN)
  marco.gaiarin(at)lanostrafamiglia.it   t +39-0434-842711   f +39-0434-842797

		Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
    http://www.lanostrafamiglia.it/25/index.php/component/k2/item/123
	(cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)

Re: [Ipac-ng-common] unrecognized option '--mac-source' && sigsev...

[Sergey M. <sm...@sm...>]

Hello.

The patch is in attachment. It works for me with iptables 1.4.21. 
Compatibility with iptables older than 1.4.14 may be broken, I didn't 
check yet.

For some obscure reason --mark extension doesn't work for me (no changes 
in netfilter table at all when such rule is present in rules file 
without any error). It is for further investigation. --mac extension works.

I uploaded changed file to the CVS source repository.

Sergey Merzlikin

23.02.2015 15:03, Marco Gaiarin пишет:
> Mandi! Sergey Merzlikin
>    In chel di` si favelave...
>
>> I will try to see, but not now. Maybe next week...
>
> Many thanks!!! If you need some help, eg early testing of the software,
> please say me!!!
>

Re: [Ipac-ng-common] unrecognized option '--mac-source' && sigsev...

[Marco G. <ga...@sv...>]

Mandi! Sergey Merzlikin
  In chel di` si favelave...

> I will try to see, but not now. Maybe next week...

Many thanks!!! If you need some help, eg early testing of the software,
please say me!!!

-- 
dott. Marco Gaiarin				        GNUPG Key ID: 240A3D66
  Associazione ``La Nostra Famiglia''                    http://www.sv.lnf.it/
  Polo FVG   -   Via della Bontà, 7 - 33078   -   San Vito al Tagliamento (PN)
  marco.gaiarin(at)lanostrafamiglia.it   t +39-0434-842711   f +39-0434-842797

		Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
    http://www.lanostrafamiglia.it/25/index.php/component/k2/item/123
	(cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)

Re: [Ipac-ng-common] unrecognized option '--mac-source' && sigsev...

[Sergey M. <sm...@sm...>]

I will try to see, but not now. Maybe next week...

Sergey Merzlikin

20.02.2015 19:09, Marco Gaiarin пишет:
>
>> Attached also my version. If you can help me...
>
> I've tryed also to post a message in iptables-devel list:
>
> 	http://www.spinics.net/lists/netfilter-devel/msg35228.html
>
> but no one reply me. :-(((
>
>
> There's nothing more i can do? Thanks.
>

Re: [Ipac-ng-common] unrecognized option '--mac-source' && sigsev...

[Marco G. <ga...@sv...>]

> Attached also my version. If you can help me...

I've tryed also to post a message in iptables-devel list:

	http://www.spinics.net/lists/netfilter-devel/msg35228.html

but no one reply me. :-(((


There's nothing more i can do? Thanks.

-- 
dott. Marco Gaiarin				        GNUPG Key ID: 240A3D66
  Associazione ``La Nostra Famiglia''                    http://www.sv.lnf.it/
  Polo FVG   -   Via della Bontà, 7 - 33078   -   San Vito al Tagliamento (PN)
  marco.gaiarin(at)lanostrafamiglia.it   t +39-0434-842711   f +39-0434-842797

		Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
    http://www.lanostrafamiglia.it/25/index.php/component/k2/item/123
	(cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)

Re: [Ipac-ng-common] unrecognized option '--mac-source' && sigsev...

[Marco G. <ga...@sv...>]

Mandi! Sergey Merzlikin
  In chel di` si favelave...

> Yes, all files in iptables directory. A lot of code in these files was 
> copied from corresponding files of iptables project, so you may try to 
> compare sources of two iptables versions to understand what was changed, 
> and then move changed pieces of code to ipac-ng.

Attached a full diff of 'iptables.c' from 1.4.8 to 1.4.14.

I've noted, amongs other:

1) the function from where the code where copied change name from
 do_command() to do_command4(). But i think is totally unrelated.

2) some variable and data structures changed, seems to me irrilevant.

3) all the code for the 'm' case changed, substituted by a single
 function, command_match(). The function seems to me do the same thing
of the old code.

3) all the code for the 'default' case get substituted by the function
 command_default(). As above, the code seems to me the same.


Friday i've tried to add the missing functions and cleanup the code.
Now does not sigsev anymore. But still reply with 'unrecognized option'
as subject.

Attached also my version. If you can help me...

-- 
dott. Marco Gaiarin				        GNUPG Key ID: 240A3D66
  Associazione ``La Nostra Famiglia''                    http://www.sv.lnf.it/
  Polo FVG   -   Via della Bontà, 7 - 33078   -   San Vito al Tagliamento (PN)
  marco.gaiarin(at)lanostrafamiglia.it   t +39-0434-842711   f +39-0434-842797

		Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
    http://www.lanostrafamiglia.it/25/index.php/component/k2/item/123
	(cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)

Re: [Ipac-ng-common] unrecognized option '--mac-source' && sigsev...

[Sergey M. <sm...@sm...>]

Hello, Marco.

Yes, all files in iptables directory. A lot of code in these files was 
copied from corresponding files of iptables project, so you may try to 
compare sources of two iptables versions to understand what was changed, 
and then move changed pieces of code to ipac-ng.

Sergey Merzlikin

06.02.2015 13:35, Marco Gaiarin пишет:
> Mandi! Sergey Merzlikin
>    In chel di` si favelave...
>
>> Firstly, fetcipac must be recompiled (with correct iptables headers)
>> every time iptables version change because it depends on iptables libraries.
>
> You put me in doubt, so i've recompiled ipac-ng, but nothing changed.
>
> configure seems to me do the right job...
>
>   ./configure --prefix=/usr \
> 		--mandir=/usr/share/man \
> 		--datadir=/var/lib/ipac \
> 		--enable-default-storage=plain-file \
> 		--with-postgresql-inc=/usr/include/postgresql
>   [...]
>   checking xtables.h usability... yes
>   checking xtables.h presence... yes
>   checking for xtables.h... yes
>   checking libiptc/libiptc.h usability... yes
>   checking libiptc/libiptc.h presence... yes
>   checking for libiptc/libiptc.h... yes
>   checking for library containing xtables_init... -lxtables
>   checking for library containing iptc_init... -lip4tc
>   checking for default database name... ipac (default)
>   checking for default database port...  (default)
>   configure: creating ./config.status
>   [...]
>
>
>> Secondly, current version of ipac-ng was tested with iptables up to
>> 1.4.12-1. I'm not sure whether ipac-ng will work or not with newer
>> versions of iptables.
>> So, try to recompile. If it will not help, try to downgrade iptables.
>
> Downgrading iptables is really a no-options.
>
> There's something where i can look into to try to make a patch? Seems
> to me into agents/iptables/iptables.c, but i'm seeking feedback.
>
>
> Thanks.
>

Re: [Ipac-ng-common] unrecognized option '--mac-source' && sigsev...

[Marco G. <ga...@sv...>]

Mandi! Sergey Merzlikin
  In chel di` si favelave...

> Firstly, fetcipac must be recompiled (with correct iptables headers) 
> every time iptables version change because it depends on iptables libraries.

You put me in doubt, so i've recompiled ipac-ng, but nothing changed.

configure seems to me do the right job...

 ./configure --prefix=/usr \
		--mandir=/usr/share/man \
		--datadir=/var/lib/ipac \
		--enable-default-storage=plain-file \
		--with-postgresql-inc=/usr/include/postgresql
 [...]
 checking xtables.h usability... yes
 checking xtables.h presence... yes
 checking for xtables.h... yes
 checking libiptc/libiptc.h usability... yes
 checking libiptc/libiptc.h presence... yes
 checking for libiptc/libiptc.h... yes
 checking for library containing xtables_init... -lxtables
 checking for library containing iptc_init... -lip4tc
 checking for default database name... ipac (default)
 checking for default database port...  (default)
 configure: creating ./config.status
 [...]


> Secondly, current version of ipac-ng was tested with iptables up to 
> 1.4.12-1. I'm not sure whether ipac-ng will work or not with newer 
> versions of iptables.
> So, try to recompile. If it will not help, try to downgrade iptables.

Downgrading iptables is really a no-options.

There's something where i can look into to try to make a patch? Seems
to me into agents/iptables/iptables.c, but i'm seeking feedback.


Thanks.

-- 
dott. Marco Gaiarin				        GNUPG Key ID: 240A3D66
  Associazione ``La Nostra Famiglia''                    http://www.sv.lnf.it/
  Polo FVG   -   Via della Bontà, 7 - 33078   -   San Vito al Tagliamento (PN)
  marco.gaiarin(at)lanostrafamiglia.it   t +39-0434-842711   f +39-0434-842797

		Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
    http://www.lanostrafamiglia.it/25/index.php/component/k2/item/123
	(cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)

Re: [Ipac-ng-common] unrecognized option '--mac-source' && sigsev...

[Sergey M. <sm...@sm...>]

Hello.

Firstly, fetcipac must be recompiled (with correct iptables headers) 
every time iptables version change because it depends on iptables libraries.

Secondly, current version of ipac-ng was tested with iptables up to 
1.4.12-1. I'm not sure whether ipac-ng will work or not with newer 
versions of iptables.

So, try to recompile. If it will not help, try to downgrade iptables.

Sergey Merzlikin

05.02.2015 19:59, Marco Gaiarin пишет:
>
> I was using ipac-ng on a debian squeeze system (iptables 1.4.8-3), with
> extended options (mac source match).
>
> Now i've upgraded to debian wheezy (iptables 1.4.14-3.1) and ipac-ng
> (really, fetchipac) bump with the error at subject and sigsev.
> Runing under strace lead to:
>
> [...]
> open("/etc/ipac-ng/rules.conf", O_RDONLY) = 4
> ioctl(4, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbfb77898) = -1 ENOTTY (Inappropriate ioctl for device)
> fstat64(4, {st_mode=S_IFREG|0644, st_size=7804, ...}) = 0
> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7794000
> read(4, "# Debian default ipac-ng configu"..., 8192) = 7804
> read(4, "", 4096)                       = 0
> brk(0x871f000)                          = 0x871f000
> read(4, "", 8192)                       = 0
> ioctl(4, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbfb77888) = -1 ENOTTY (Inappropriate ioctl for device)
> close(4)                                = 0
> munmap(0xb7794000, 4096)                = 0
> write(2, "Setting up acc chains..\n", 24Setting up acc chains..
> ) = 24
> write(2, "Setup tables..\n", 15Setup tables..
> )        = 15
> write(2, "Setting up accounting rules..\n", 30Setting up accounting rules..
> ) = 30
> write(2, "Reading and parsing rules file \""..., 57Reading and parsing rules file "/etc/ipac-ng/rules.conf"
> ) = 57
> open("/var/run/ipac.rules", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 4
> fstat64(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7794000
> stat64("/lib/xtables/libxt_standard.so", {st_mode=S_IFREG|0644, st_size=5508, ...}) = 0
> futex(0xb71e806c, FUTEX_WAKE_PRIVATE, 2147483647) = 0
> open("/lib/xtables/libxt_standard.so", O_RDONLY) = 5
> read(5, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\320\4\0\0004\0\0\0"..., 512) = 512
> fstat64(5, {st_mode=S_IFREG|0644, st_size=5508, ...}) = 0
> mmap2(NULL, 8352, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 5, 0) = 0xb7791000
> mmap2(0xb7792000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 5, 0) = 0xb7792000
> close(5)                                = 0
> mprotect(0xb7792000, 4096, PROT_READ)   = 0
> stat64("/lib/xtables/libxt_mac.so", {st_mode=S_IFREG|0644, st_size=5556, ...}) = 0
> open("/lib/xtables/libxt_mac.so", O_RDONLY) = 5
> read(5, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220\5\0\0004\0\0\0"..., 512) = 512
> fstat64(5, {st_mode=S_IFREG|0644, st_size=5556, ...}) = 0
> mmap2(NULL, 8348, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 5, 0) = 0xb6f63000
> mmap2(0xb6f64000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 5, 0) = 0xb6f64000
> close(5)                                = 0
> mprotect(0xb6f64000, 4096, PROT_READ)   = 0
> write(2, "fetchipac: unrecognized option '"..., 46fetchipac: unrecognized option '--mac-source'
> ) = 46
> --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> +++ killed by SIGSEGV +++
>
> Seems to me that correctly load the libxt_mac.so extension library, but then hangs.
>
> I've comented out in /etc/ipac-ng/rules.conf the rules:
>
>   Totale ingresso MPLS A|ipac~o|vlan22|all|||mac --mac-source bc:16:65:5a:28:20|
>   Totale ingresso MPLS A|ipac~fi|vlan22|all|||mac --mac-source bc:16:65:5a:28:20|
>   Totale ingresso MPLS B|ipac~o|vlan22|all|||mac --mac-source bc:16:65:33:db:20|
>   Totale ingresso MPLS B|ipac~fi|vlan22|all|||mac --mac-source bc:16:65:33:db:20|
>
> and ipac-ng/fetchipac start flawlessy.
>
> seems to me there's no syntiax errors, eg:
>
>   fouc:/etc/ipac-ng# iptables -m mac -h
>   iptables v1.4.14
>
>   [...]
>
>   mac match options:
>   [!] --mac-source XX:XX:XX:XX:XX:XX
>   				Match source MAC address
>
>
> How can i fix it? Thanks.
>

[Ipac-ng-common] unrecognized option '--mac-source' && sigsev...

[Marco G. <ga...@sv...>]

I was using ipac-ng on a debian squeeze system (iptables 1.4.8-3), with
extended options (mac source match).

Now i've upgraded to debian wheezy (iptables 1.4.14-3.1) and ipac-ng
(really, fetchipac) bump with the error at subject and sigsev.
Runing under strace lead to:

[...]
open("/etc/ipac-ng/rules.conf", O_RDONLY) = 4
ioctl(4, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbfb77898) = -1 ENOTTY (Inappropriate ioctl for device)
fstat64(4, {st_mode=S_IFREG|0644, st_size=7804, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7794000
read(4, "# Debian default ipac-ng configu"..., 8192) = 7804
read(4, "", 4096)                       = 0
brk(0x871f000)                          = 0x871f000
read(4, "", 8192)                       = 0
ioctl(4, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbfb77888) = -1 ENOTTY (Inappropriate ioctl for device)
close(4)                                = 0
munmap(0xb7794000, 4096)                = 0
write(2, "Setting up acc chains..\n", 24Setting up acc chains..
) = 24
write(2, "Setup tables..\n", 15Setup tables..
)        = 15
write(2, "Setting up accounting rules..\n", 30Setting up accounting rules..
) = 30
write(2, "Reading and parsing rules file \""..., 57Reading and parsing rules file "/etc/ipac-ng/rules.conf"
) = 57
open("/var/run/ipac.rules", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 4
fstat64(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7794000
stat64("/lib/xtables/libxt_standard.so", {st_mode=S_IFREG|0644, st_size=5508, ...}) = 0
futex(0xb71e806c, FUTEX_WAKE_PRIVATE, 2147483647) = 0
open("/lib/xtables/libxt_standard.so", O_RDONLY) = 5
read(5, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\320\4\0\0004\0\0\0"..., 512) = 512
fstat64(5, {st_mode=S_IFREG|0644, st_size=5508, ...}) = 0
mmap2(NULL, 8352, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 5, 0) = 0xb7791000
mmap2(0xb7792000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 5, 0) = 0xb7792000
close(5)                                = 0
mprotect(0xb7792000, 4096, PROT_READ)   = 0
stat64("/lib/xtables/libxt_mac.so", {st_mode=S_IFREG|0644, st_size=5556, ...}) = 0
open("/lib/xtables/libxt_mac.so", O_RDONLY) = 5
read(5, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220\5\0\0004\0\0\0"..., 512) = 512
fstat64(5, {st_mode=S_IFREG|0644, st_size=5556, ...}) = 0
mmap2(NULL, 8348, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 5, 0) = 0xb6f63000
mmap2(0xb6f64000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 5, 0) = 0xb6f64000
close(5)                                = 0
mprotect(0xb6f64000, 4096, PROT_READ)   = 0
write(2, "fetchipac: unrecognized option '"..., 46fetchipac: unrecognized option '--mac-source'
) = 46
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

Seems to me that correctly load the libxt_mac.so extension library, but then hangs.

I've comented out in /etc/ipac-ng/rules.conf the rules:

 Totale ingresso MPLS A|ipac~o|vlan22|all|||mac --mac-source bc:16:65:5a:28:20|
 Totale ingresso MPLS A|ipac~fi|vlan22|all|||mac --mac-source bc:16:65:5a:28:20|
 Totale ingresso MPLS B|ipac~o|vlan22|all|||mac --mac-source bc:16:65:33:db:20|
 Totale ingresso MPLS B|ipac~fi|vlan22|all|||mac --mac-source bc:16:65:33:db:20|

and ipac-ng/fetchipac start flawlessy.

seems to me there's no syntiax errors, eg:

 fouc:/etc/ipac-ng# iptables -m mac -h
 iptables v1.4.14
 
 [...]
 
 mac match options:
 [!] --mac-source XX:XX:XX:XX:XX:XX
 				Match source MAC address


How can i fix it? Thanks.

-- 
dott. Marco Gaiarin				        GNUPG Key ID: 240A3D66
  Associazione ``La Nostra Famiglia''                    http://www.sv.lnf.it/
  Polo FVG   -   Via della Bontà, 7 - 33078   -   San Vito al Tagliamento (PN)
  marco.gaiarin(at)lanostrafamiglia.it   t +39-0434-842711   f +39-0434-842797

		Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
    http://www.lanostrafamiglia.it/25/index.php/component/k2/item/123
	(cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)

Re: [Ipac-ng-common] what are the required perl modules to run ipac-ng

[Sergey M. <sm...@sm...>]

Hello.

Here are requirements for ipacsum file:

use 5.000;
use Getopt::Long;
use Sys::Hostname;
use POSIX qw(strftime);
use Time::Local;
use Socket;
use IO::Handle;

Imaging part additionally uses GD library, but the script will not fail 
when this library is not installed.

There are some more Perl scripts in contrib folder. You may see their 
requirements at the beginning of each Perl file (see use statements).

Sergey Merzlikin

23.05.2014 1:51, Samitha Wijedasa пишет:
> Hi,
>
> What are the ncessary perl modules to run ipac-ng. I'm running ipac-ng
> in a embedded platform. Currently crosscompiling perl and doing a 'make
> install.perl' will occupy close to 15MB space. I want to use a custom
> installation target for perl  or disable unnecesseary modlules to
> ipac-ng. So I need to identify only the required modules to run ipac-ng.
> I do not need the imaging part associated with ipacsum as well.
>
> Thanks
>
> Samitha
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
>
>
>
> _______________________________________________
> Ipac-ng-common mailing list
> Ipa...@li...
> https://lists.sourceforge.net/lists/listinfo/ipac-ng-common
>

[Ipac-ng-common] what are the required perl modules to run ipac-ng

[Samitha W. <sam...@ya...>]

Hi,

What are the ncessary perl modules to run ipac-ng. I'm running ipac-ng in a embedded platform. Currently crosscompiling perl and doing a 'make install.perl' will occupy close to 15MB space. I want to use a custom installation target for perl  or disable unnecesseary modlules to ipac-ng. So I need to identify only the required modules to run ipac-ng. I do not need the imaging part associated with ipacsum as well.


Thanks

Samitha

Re: [Ipac-ng-common] cross compiling with arm-linux-gcc fails

[Sergey M. <sm...@sm...>]

Excellent.
You may check help files fetchipac.8, ipacsum.8, ipac-convert.8 for 
correctly substituted strings and replace them manually if required.
Strings for substitution look like "@<SOMETHING>@", the list of 
substitutions you may see in the file subst-config.
The file ipacsum currently doesn't contain strings for substitution, so 
only help files affected.

Sergey Merzlikin

11.05.2014 9:49, Samitha Wijedasa пишет:
> Hi,
>
> Thank you for the response. I would like to let you know ipac-ng was
> successfully cross-compiled along with the depending packages and
> integrated to one of our embedded platforms. I just commented out the
> following line in Makefile.IN and proceeded with cross-compiling.
>
> SUBSTFILES=ipacsum fetchipac.8 ipacsum.8 ipac-convert.8
>
> Thanks
>
> Samitha
> On Monday, 5 May 2014 1:32 PM, Sergey Merzlikin <sm...@sm...> wrote:
> Hello, Samitha.
>
> The program was not tested for cross-compiling, at least the last version.
>
> Try to clean your source directory running "make distclean", then run
> configure and make again. You may also regenerate configure script using
> autogen.
>
> If the problem persists please show files generated by configure script,
> I will try to find this bug in them.
>
> What version of iptables are you compiling for? Note, ipac-ng still not
> updated for some new versions of iptables.
>
>
> Sergey Merzlikin
>
> 05.05.2014 2:34, Samitha Wijedasa пишет:
>  > Hi,
>  >
>  > My cross compiling attempt fails and appreciate your help to proceed.
>  > The ./configure script log and the make command log are as follows.
>  > Also, I have attached the staging directory contetnts herewith.
>  >
>  > xxxxxxxx@L00095-ubu
> <mailto:xxxxxxxx@L00095-ubu>:~/ipnac-ng/cross/ipac-ng$ ./configure
>  > --host=arm-linux --prefix=/usr CFLAGS=-Os
>  > LDFLAGS="-L/home/IDERS/swijedasa/linux_sysbuild/_staging_/usr/lib"
>  > CPPFLAGS="-I/home/IDERS/swijedasa/linux_sysbuild/_staging_/usr/include"
>  > LIBS="-lrt"
>  > configure: WARNING: if you wanted to set the --build type, don't use
> --host.
>  >      If a cross compiler is detected then cross compile mode will be used
>  > checking for arm-linux-gcc... arm-linux-gcc
>  > checking whether the C compiler works... yes
>  > checking for C compiler default output file name... a.out
>  > checking for suffix of executables...
>  > checking whether we are cross compiling... yes
>  > checking for suffix of object files... o
>  > checking whether we are using the GNU C compiler... yes
>  > checking whether arm-linux-gcc accepts -g... yes
>  > checking for arm-linux-gcc option to accept ISO C89... none needed
>  > checking for an ANSI C-conforming const... yes
>  > checking how to run the C preprocessor... arm-linux-gcc -E
>  > checking for grep that handles long lines and -e... /bin/grep
>  > checking for egrep... /bin/grep -E
>  > checking for ANSI C header files... yes
>  > checking for sys/types.h... yes
>  > checking for sys/stat.h... yes
>  > checking for stdlib.h... yes
>  > checking for string.h... yes
>  > checking for memory.h... yes
>  > checking for strings.h... yes
>  > checking for inttypes.h... yes
>  > checking for stdint.h... yes
>  > checking for unistd.h... yes
>  > checking for size_t... yes
>  > checking for arm-linux-gcc... (cached) arm-linux-gcc
>  > checking whether we are using the GNU C compiler... (cached) yes
>  > checking whether arm-linux-gcc accepts -g... (cached) yes
>  > checking for arm-linux-gcc option to accept ISO C89... (cached) none
> needed
>  > checking for gawk... gawk
>  > checking for bison... bison -y
>  > checking for flex... flex
>  > checking lex output file root... lex.yy
>  > checking lex library... -lfl
>  > checking whether yytext is a pointer... yes
>  > checking for ipchains... no
>  > checking for iptables... /sbin/iptables
>  > checking for mktemp... /bin/mktemp
>  > checking for perl5... no
>  > checking for perl... /usr/bin/perl
>  > checking for PQexec in -lpq... no
>  > configure: WARNING: postgres library not found!
>  >      support for optional storage "postgre" will be disabled
>  >      hint: use the configure option '--with-postgresql-lib'
>  > checking for gdbm_open in -lgdbm... yes
>  > checking for mysql_query in -lmysqlclient... no
>  > configure: WARNING: mysql library not found!
>  >      support for optional storage "mysql" will be disabled
>  > checking for sqlite_get_table in -lsqlite... no
>  > configure: WARNING: sqlite library not found!
>  >      support for optional storage "sqlite" will be disabled
>  > checking gdbm.h usability... yes
>  > checking gdbm.h presence... yes
>  > checking for gdbm.h... yes
>  > checking for default data directory... /var/lib/ipac
>  > checking for default run file name... /var/run/ipac.rules
>  > checking for default pid file name... /var/run/ipac.pid
>  > checking for default flag file name... /var/lib/ipac/flag
>  > checking for default status file name... /var/run/ipac.status
>  > checking for default fetchipac lock file name... /var/lock/ipac.lck
>  > checking for tmp directory... /tmp
>  > checking for maximum rule name length... 32
>  > checking for available storage methods... gdbm plain-file
>  > checking for default storage method... gdbm (default)
>  > checking for available access agents... files
>  > checking for default access agent... files  (default)
>  > checking for default config directory... /etc/ipac-ng (default)
>  > checking for default config file... /etc/ipac-ng/ipac.conf (default)
>  > checking for available accounting agents...  ipchains iptables
>  > checking for default accounting agent... iptables (default)
>  > checking if ipacsum debugging is desired... no (default)
>  > checking if database debugging is desired... no (default)
>  > checking xtables.h usability... yes
>  > checking xtables.h presence... yes
>  > checking for xtables.h... yes
>  > checking libiptc/libiptc.h usability... yes
>  > checking libiptc/libiptc.h presence... yes
>  > checking for libiptc/libiptc.h... yes
>  > checking for library containing xtables_init... -lxtables
>  > checking for library containing iptc_init... -lip4tc
>  > checking for default database name... ipac (default)
>  > checking for default database port...  (default)
>  > configure: creating ./config.status
>  > config.status: creating Makefile
>  > config.status: WARNING:  'Makefile.in' seems to ignore the --datarootdir
>  > setting
>  > config.status: creating storage/Makefile
>  > config.status: creating agents/Makefile
>  > config.status: creating access/Makefile
>  > config.status: creating subst-config
>  > config.status: creating access/files/Makefile
>  > config.status: creating agents/iptables/Makefile
>  > config.status: creating storage/gdbm/Makefile
>  > config.status: creating storage/plain-file/Makefile
>  > config.status: creating ipactest
>  > config.status: creating config.h
>  > config.status: config.h is unchanged
>  >
>  >
>  > xxxxxxxx@L00095-ubu
> <mailto:xxxxxxxx@L00095-ubu>:~/ipnac-ng/cross/ipac-ng$ make all
>  > running subst on files: ipacsum fetchipac.8 ipacsum.8 ipac-convert.8...
>  > ./subst: 1: ./subst: Syntax error: word unexpected (expecting ")")
>  > make: *** [dosubst] Error 1
>  > swijedasa@L00095-ubu
> <mailto:swijedasa@L00095-ubu>:~/ipnac-ng/cross/ipac-ng$
>
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>  >
>  >
> ------------------------------------------------------------------------------
>  > "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
>  > Instantly run your Selenium tests across 300+ browser/OS combos.  Get
>  > unparalleled scalability from the best Selenium testing platform
> available.
>  > Simple to use. Nothing to install. Get started now for free."
>  > http://p.sf.net/sfu/SauceLabs
>  >
>  >
>  >
>  > _______________________________________________
>  > Ipac-ng-common mailing list
>  > Ipa...@li...
> <mailto:Ipa...@li...>
>  > https://lists.sourceforge.net/lists/listinfo/ipac-ng-common
>
>  >
>
>

Re: [Ipac-ng-common] cross compiling with arm-linux-gcc fails

[Samitha W. <sam...@ya...>]

Hi,

Thank you for the response. I would like to let you know ipac-ng was successfully cross-compiled along with the depending packages and integrated to one of our embedded platforms. I just commented out the following line in Makefile.IN and proceeded with cross-compiling.


SUBSTFILES=ipacsum fetchipac.8 ipacsum.8 ipac-convert.8

Thanks

Samitha

On Monday, 5 May 2014 1:32 PM, Sergey Merzlikin <sm...@sm...> wrote:
 
Hello, Samitha.

The program was not tested for cross-compiling, at least the last version.

Try to clean your source directory running "make distclean", then run 
configure and make again. You may also regenerate configure script using 
autogen.

If the problem persists please show files generated by configure script, 
I will try to find this bug in them.

What version of iptables are you compiling for? Note, ipac-ng still not 
updated for some new versions of iptables.


Sergey Merzlikin


05.05.2014 2:34, Samitha Wijedasa пишет:
> Hi,
>
> My cross compiling attempt fails and appreciate your help to proceed.
> The ./configure script log and the make command log are as follows.
> Also, I have attached the staging directory contetnts herewith.
>
> xxxxxxxx@L00095-ubu:~/ipnac-ng/cross/ipac-ng$ ./configure
> --host=arm-linux --prefix=/usr CFLAGS=-Os
> LDFLAGS="-L/home/IDERS/swijedasa/linux_sysbuild/_staging_/usr/lib"
> CPPFLAGS="-I/home/IDERS/swijedasa/linux_sysbuild/_staging_/usr/include"
> LIBS="-lrt"
> configure: WARNING: if you wanted to set the --build type, don't use --host.
>      If a cross compiler is detected then cross compile mode will be used
> checking for arm-linux-gcc... arm-linux-gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... yes
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether arm-linux-gcc accepts -g... yes
> checking for arm-linux-gcc option to accept ISO C89... none needed
> checking for an ANSI C-conforming const... yes
> checking how to run the C preprocessor... arm-linux-gcc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for size_t... yes
> checking for arm-linux-gcc... (cached) arm-linux-gcc
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether arm-linux-gcc accepts -g... (cached) yes
> checking for arm-linux-gcc option to accept ISO C89... (cached) none needed
> checking for gawk... gawk
> checking for bison... bison -y
> checking for flex... flex
> checking lex output file root... lex.yy
> checking lex library... -lfl
> checking whether yytext is a pointer... yes
> checking for ipchains... no
> checking for iptables... /sbin/iptables
> checking for mktemp... /bin/mktemp
> checking for perl5... no
> checking for perl... /usr/bin/perl
> checking for PQexec in -lpq... no
> configure: WARNING: postgres library not found!
>      support for optional storage "postgre" will be disabled
>      hint: use the configure option '--with-postgresql-lib'
> checking for gdbm_open in -lgdbm... yes
> checking for mysql_query in -lmysqlclient... no
> configure: WARNING: mysql library not found!
>      support for optional storage "mysql" will be disabled
> checking for sqlite_get_table in -lsqlite... no
> configure: WARNING: sqlite library not found!
>      support for optional storage "sqlite" will be disabled
> checking gdbm.h usability... yes
> checking gdbm.h presence... yes
> checking for gdbm.h... yes
> checking for default data directory... /var/lib/ipac
> checking for default run file name... /var/run/ipac.rules
> checking for default pid file name... /var/run/ipac.pid
> checking for default flag file name... /var/lib/ipac/flag
> checking for default status file name... /var/run/ipac.status
> checking for default fetchipac lock file name... /var/lock/ipac.lck
> checking for tmp directory... /tmp
> checking for maximum rule name length... 32
> checking for available storage methods... gdbm plain-file
> checking for default storage method... gdbm (default)
> checking for available access agents... files
> checking for default access agent... files  (default)
> checking for default config directory... /etc/ipac-ng (default)
> checking for default config file... /etc/ipac-ng/ipac.conf (default)
> checking for available accounting agents...  ipchains iptables
> checking for default accounting agent... iptables (default)
> checking if ipacsum debugging is desired... no (default)
> checking if database debugging is desired... no (default)
> checking xtables.h usability... yes
> checking xtables.h presence... yes
> checking for xtables.h... yes
> checking libiptc/libiptc.h usability... yes
> checking libiptc/libiptc.h presence... yes
> checking for libiptc/libiptc.h... yes
> checking for library containing xtables_init... -lxtables
> checking for library containing iptc_init... -lip4tc
> checking for default database name... ipac (default)
> checking for default database port...  (default)
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: WARNING:  'Makefile.in' seems to ignore the --datarootdir
> setting
> config.status: creating storage/Makefile
> config.status: creating agents/Makefile
> config.status: creating access/Makefile
> config.status: creating subst-config
> config.status: creating access/files/Makefile
> config.status: creating agents/iptables/Makefile
> config.status: creating storage/gdbm/Makefile
> config.status: creating storage/plain-file/Makefile
> config.status: creating ipactest
> config.status: creating config.h
> config.status: config.h is unchanged
>
>
> xxxxxxxx@L00095-ubu:~/ipnac-ng/cross/ipac-ng$ make all
> running subst on files: ipacsum fetchipac.8 ipacsum.8 ipac-convert.8...
> ./subst: 1: ./subst: Syntax error: word unexpected (expecting ")")
> make: *** [dosubst] Error 1
> swijedasa@L00095-ubu:~/ipnac-ng/cross/ipac-ng$
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
>
>
>
> _______________________________________________
> Ipac-ng-common mailing list
> Ipa...@li...
> https://lists.sourceforge.net/lists/listinfo/ipac-ng-common

>

Re: [Ipac-ng-common] cross compiling with arm-linux-gcc fails

[Sergey M. <sm...@sm...>]

Hello, Samitha.

The program was not tested for cross-compiling, at least the last version.

Try to clean your source directory running "make distclean", then run 
configure and make again. You may also regenerate configure script using 
autogen.

If the problem persists please show files generated by configure script, 
I will try to find this bug in them.

What version of iptables are you compiling for? Note, ipac-ng still not 
updated for some new versions of iptables.


Sergey Merzlikin

05.05.2014 2:34, Samitha Wijedasa пишет:
> Hi,
>
> My cross compiling attempt fails and appreciate your help to proceed.
> The ./configure script log and the make command log are as follows.
> Also, I have attached the staging directory contetnts herewith.
>
> xxxxxxxx@L00095-ubu:~/ipnac-ng/cross/ipac-ng$ ./configure
> --host=arm-linux --prefix=/usr CFLAGS=-Os
> LDFLAGS="-L/home/IDERS/swijedasa/linux_sysbuild/_staging_/usr/lib"
> CPPFLAGS="-I/home/IDERS/swijedasa/linux_sysbuild/_staging_/usr/include"
> LIBS="-lrt"
> configure: WARNING: if you wanted to set the --build type, don't use --host.
>      If a cross compiler is detected then cross compile mode will be used
> checking for arm-linux-gcc... arm-linux-gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... yes
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether arm-linux-gcc accepts -g... yes
> checking for arm-linux-gcc option to accept ISO C89... none needed
> checking for an ANSI C-conforming const... yes
> checking how to run the C preprocessor... arm-linux-gcc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for size_t... yes
> checking for arm-linux-gcc... (cached) arm-linux-gcc
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether arm-linux-gcc accepts -g... (cached) yes
> checking for arm-linux-gcc option to accept ISO C89... (cached) none needed
> checking for gawk... gawk
> checking for bison... bison -y
> checking for flex... flex
> checking lex output file root... lex.yy
> checking lex library... -lfl
> checking whether yytext is a pointer... yes
> checking for ipchains... no
> checking for iptables... /sbin/iptables
> checking for mktemp... /bin/mktemp
> checking for perl5... no
> checking for perl... /usr/bin/perl
> checking for PQexec in -lpq... no
> configure: WARNING: postgres library not found!
>      support for optional storage "postgre" will be disabled
>      hint: use the configure option '--with-postgresql-lib'
> checking for gdbm_open in -lgdbm... yes
> checking for mysql_query in -lmysqlclient... no
> configure: WARNING: mysql library not found!
>      support for optional storage "mysql" will be disabled
> checking for sqlite_get_table in -lsqlite... no
> configure: WARNING: sqlite library not found!
>      support for optional storage "sqlite" will be disabled
> checking gdbm.h usability... yes
> checking gdbm.h presence... yes
> checking for gdbm.h... yes
> checking for default data directory... /var/lib/ipac
> checking for default run file name... /var/run/ipac.rules
> checking for default pid file name... /var/run/ipac.pid
> checking for default flag file name... /var/lib/ipac/flag
> checking for default status file name... /var/run/ipac.status
> checking for default fetchipac lock file name... /var/lock/ipac.lck
> checking for tmp directory... /tmp
> checking for maximum rule name length... 32
> checking for available storage methods... gdbm plain-file
> checking for default storage method... gdbm (default)
> checking for available access agents... files
> checking for default access agent... files  (default)
> checking for default config directory... /etc/ipac-ng (default)
> checking for default config file... /etc/ipac-ng/ipac.conf (default)
> checking for available accounting agents...  ipchains iptables
> checking for default accounting agent... iptables (default)
> checking if ipacsum debugging is desired... no (default)
> checking if database debugging is desired... no (default)
> checking xtables.h usability... yes
> checking xtables.h presence... yes
> checking for xtables.h... yes
> checking libiptc/libiptc.h usability... yes
> checking libiptc/libiptc.h presence... yes
> checking for libiptc/libiptc.h... yes
> checking for library containing xtables_init... -lxtables
> checking for library containing iptc_init... -lip4tc
> checking for default database name... ipac (default)
> checking for default database port...  (default)
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: WARNING:  'Makefile.in' seems to ignore the --datarootdir
> setting
> config.status: creating storage/Makefile
> config.status: creating agents/Makefile
> config.status: creating access/Makefile
> config.status: creating subst-config
> config.status: creating access/files/Makefile
> config.status: creating agents/iptables/Makefile
> config.status: creating storage/gdbm/Makefile
> config.status: creating storage/plain-file/Makefile
> config.status: creating ipactest
> config.status: creating config.h
> config.status: config.h is unchanged
>
>
> xxxxxxxx@L00095-ubu:~/ipnac-ng/cross/ipac-ng$ make all
> running subst on files: ipacsum fetchipac.8 ipacsum.8 ipac-convert.8...
> ./subst: 1: ./subst: Syntax error: word unexpected (expecting ")")
> make: *** [dosubst] Error 1
> swijedasa@L00095-ubu:~/ipnac-ng/cross/ipac-ng$
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
>
>
>
> _______________________________________________
> Ipac-ng-common mailing list
> Ipa...@li...
> https://lists.sourceforge.net/lists/listinfo/ipac-ng-common
>

Re: [Ipac-ng-common] interface and port ranges

[Sergey M. <sm...@sm...>]

Hello, Ronny.

I just updated CVS storage of ipac-ng. Seems I fixed eth+ problem. Port 
ranges later...


Sergey Merzlikin
http://www.smsoft.ru

-----Исходное сообщение----- 
From: Ronny Seffner
Sent: Wednesday, November 09, 2011 1:28 AM
To: ipa...@li...
Subject: Re: [Ipac-ng-common] interface and port ranges

Hi Sergey,

> This feature (port ranges) was never implemented in ipac-ng or was removed
>
Yes, maybe it was a feature of ipac and not ipac-ng, but normally I would 
expect a *-ng project takes als the cool features over ;-)

> In last version I just removed it from documentation and added to known 
> problems.
>
Lucky is, who is able to read ...

> BTW, eth+ notation was never implemented (and documented) too.
>
Look at latest tar.bz2: in contrib/sample_configs/rules.conf.iptables and 
you'll find it.

> You may specify several ports separated by space. This works. And you may
>
This will help in my FTP example, thanks for this hint.

> specify empty interface name to include all interfaces to the rule.
>
In this case I also count traffic from/to loopback. In case of an mailserver 
e.g. with local filters this may multiply the traffic, so the admin has to 
think twice before use of this global thing in rules.conf. It's only one 
more char, the parser hast to accept, there is no magic to tell iptables 
what eth+ means - so maybe it is a simple patch only.


Thanks for your answers.


Mit freundlichen Grüßen / Kind regards
     Ronny Seffner
-- 
Ronny Seffner  |  Alter Viehweg 1  |  01665 Triebischtal

www.seffner.de  |  ro...@se...  |  +49 35245 72950


------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Ipac-ng-common mailing list
Ipa...@li...
https://lists.sourceforge.net/lists/listinfo/ipac-ng-common