On 2012-11-24, Gilles LAMIRAL gilles.lami...@laposte.net wrote:
When I do two tcpdump on each interface I see that
when it fails the ping -I are just going on the wrong interface
even if the routing table indicates the contrary.
Routes depend on the *destination* address only. Source address
On 2012-11-24, bofh goodb...@gmail.com wrote:
On Thu, Nov 22, 2012 at 10:08 AM, Nick Holland
n...@holland-consulting.net wrote:
On 11/22/12 09:58, bofh wrote:
Can I just run install - upgrade and install everything but etc.tgz
and xetc.tgz? Any post installation stuff I have to worry about?
(cc'ing misc instead of tech)
On Sat, Nov 24, 2012 at 7:21 PM, William Ahern
will...@25thandclement.com wrote:
On Thu, Nov 22, 2012 at 01:27:46PM -0430, Andres Perera wrote:
On Thu, Nov 22, 2012 at 11:58 AM, Kevin Chadwick ma1l1i...@yahoo.co.uk
wrote:
On Thu, 22 Nov 2012 09:30:41 -0430
Hi,
Spoke with Sebastian and Reyk an they helped me to solve the issue.
You have to apply the following patch Sebastian provided.
This is the message from Sebastian with the fix:
Hi,
the problem is that strtonum() can only handle a maximum of LLONG_MAX in
maxval.
(file: 4GB-fix-llu.patch)
Hello,
Do you have any explanation for this routing inversion
or a workaround/good practice to have a ping -I always working as intended?
This is working as intended..
The ping always work without the -I for the same destination,
no pf, no multiple route tables. just a classic routing
On Tue, Nov 20, 2012 at 10:24:26PM -0500, Michael W. Lucas wrote:
Hi,
login.conf includes the following:
...
rpasswdRequest a password and check it against the password in
the rpasswd.db file.
...
It seems that there's no reference to rpasswd.db in the
after instaling ladvd, in ifconfig i've got description from lldp
this is so cool ...
# ifconfig ix
ix0:
flags=28b43UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST,NOINET6
mtu 1500
lladdr 90:e2:ba:19:29:a8
description: connected to Srce1 (1:14)
priority: 0
Quick update. It seems to be a nat problem. If I just test by pinging either
the 192.168.1.32 interface or the 192.168.0.13 interface it works fine and
snort sees the packets. Its only when the traffic is NATed that it fails.
-Original Message-
From: owner-m...@openbsd.org
On 25/11/2012 16:53, Raindy Long wrote:
It seems that libiconv is not in the base package , right ?
libiconv is in packages/ports
Port: libiconv-1.14
Path: converters/libiconv
Info: character set conversion library
Maint: Brad Smith b...@comstyle.com
Index: converters devel
L-deps:
9 matches
Mail list logo