If you were trying to ping both of your BGP peers (and failing), I'm
guessing both are on directly connected subnets as per eBGP rules.
As they are directly connected, routing protocols shouldn't have been
an issue so it was probably the firewall.
If I remember correctly, if you block outboun
Hello misc.
Please provide any hints how to get amount of
Internet traffic per each IP in LAN for period of
time month.
Suppose I have such simple rules to share Internet connection
for :
table { 192.168.5.0/24 }
match out on $ext_if inet proto tcp from to any nat-to em1
pass in on $int_if in
On 2014-04-15 10:27, lilit-aibolit wrote:
Hello misc.
Please provide any hints how to get amount of
Internet traffic per each IP in LAN for period of
time month.
Suppose I have such simple rules to share Internet connection
for :
table { 192.168.5.0/24 }
match out on $ext_if inet proto tcp fr
As a quick sanity check, the ftp-proxy daemon in OpenBSD 5.4 through
-current does NOT listen on IPv4 and IPv6 simultaneously?
In order to support FTP over IPv4 and IPv6, two running ftp-proxy
daemons would be required, one with the -6 flag?
If so, I do not see an immediate way to fire two ftp-pr
John Jasen writes:
> As a quick sanity check, the ftp-proxy daemon in OpenBSD 5.4 through
> -current does NOT listen on IPv4 and IPv6 simultaneously?
As documented.
> In order to support FTP over IPv4 and IPv6, two running ftp-proxy
> daemons would be required, one with the -6 flag?
Yup. Well
Em 15-04-2014 11:27, lilit-aibolit escreveu:
> Hello misc.
> Please provide any hints how to get amount of
> Internet traffic per each IP in LAN for period of
> time month.
>
> Suppose I have such simple rules to share Internet connection
> for :
>
> table { 192.168.5.0/24 }
> match out on $ext_i
On 04/15/2014 11:27 AM, Jérémie Courrèges-Anglas wrote:
> John Jasen writes:
>
>> As a quick sanity check, the ftp-proxy daemon in OpenBSD 5.4 through
>> -current does NOT listen on IPv4 and IPv6 simultaneously?
>
> As documented.
Yes, forgive me for not mentioning that.
It is buried under -6
Hey, Thanks! yes, it looks like the sys.tar.gz was missing.. I created a
small howto for it (for patching 5.4):
cd /root && ftp http://ftp.openbsd.org/pub/OpenBSD/`uname -r`/src.tar.gz &&
tar -xvzf /root/src.tar.gz -C /usr/src; ftp
http://ftp.openbsd.org/pub/OpenBSD/`uname -r`/sys.tar.gz && tar -xv
Em 15-04-2014 13:51, Peter N. M. Hansteen escreveu:
> Giancarlo Razzolini writes:
>
>> I use the mentioned solution using pflow + nfsen. But, if you want to
>> have accounting for billing purposes, I suggest you use a more robust
>> method, using radius.
> Why would radius be a more robust method
On 14 avril 2014 17:57:53 CEST, Tristan PILAT wrote:
>match from any community 64514:888 set nexthop blackhole
>
Hi,
Make sure you dont accept from any but eg from group customers, make sure the
address *does* belong to your customers space (to avoid a customer installing a
blackhole route on
On 2014-04-15, Jérémie Courrèges-Anglas wrote:
> * if it had to be integrated with rc.d(8), that would mean adding
> a ftpproxy6 script, hooking it in /etc/rc and adding a -4 flag to
> ftpproxy so that the daemons command lines differ properly for rc.d(8)
> signalling.
It needs handling one
Em 15-04-2014 14:43, Peter N. M. Hansteen escreveu:
> Giancarlo Razzolini writes:
>
>> Because using radius you can have a control per user, and accountability
>> per user, not per IP.
> Yes, of course, for the per user or per customer case I agee totally.
> For the OP's scenario it seems the IP
Stuart Henderson writes:
> On 2014-04-15, Jérémie Courrèges-Anglas wrote:
>> * if it had to be integrated with rc.d(8), that would mean adding
>> a ftpproxy6 script, hooking it in /etc/rc and adding a -4 flag to
>> ftpproxy so that the daemons command lines differ properly for rc.d(8)
>> s
On 15.04.2014 17:27, lilit-aibolit wrote:
> Hello misc.
> Please provide any hints how to get amount of
> Internet traffic per each IP in LAN for period of
> time month.
>
> Suppose I have such simple rules to share Internet connection
> for :
>
> table { 192.168.5.0/24 }
> match out on $ext_if
Em 15-04-2014 15:51, Stefan Sieg escreveu:
>
> Hello,
>
> with the already mentioned netflow solution you will not see connections
> that are not expired. So you will not see "long live" connections like vpn or
> ssh
> in your statistics at the appointed date.
You see them as "ongoing" flows and
previously on this list Steve Quinn contributed:
> The acpitz3 shutdown issue remains.
I haven't tried the latest patch however I have an nc6220 with the
issue but whilst I don't use this laptop daily personally I believe it
has never occurred if you remove the battery and power before each
boot,
16 matches
Mail list logo
