Hi,
If I have a SOCK_STREAM that is connected and working, is/should it be
possible to change the TTL before sending the next packet? (C++
applicatiom)
If I have to I'll resort to SOCK_RAW, but I don't want to have to deal
with all of the required headache of setting up a TCP conne
On 23.03.2017 14:14, Greg Wooledge wrote:
Run "uname -a" (and also "uptime") and post the results.
You a right. I didn't do a restart after last kernel update.
After a restart, TTL problem didn't occur anymore.
Also I've noted that the particular vm had
On Thu, Mar 23, 2017 at 08:36:38AM +0200, Mimiko wrote:
> Well, doing regulat apt-get update && apt-get upgrade, I fought that kernel
> is also upgraded. I've seen this several times. How comes it wasn't updated
> to 3.2.86-1.
Run "uname -a" (and also "uptime") and post the results. After a ker
On 21.03.2017 02:25, david...@freevolt.org wrote:
It is not clear to me whether your question
I regularly do apt-get upgrade, but not to next Debian version. So, how this
kernel be old for Debian 7?
is a request for information, or merely rhetorical (ie, an assertion
that your kernel is in f
On Mon, 20 Mar 2017, Mimiko wrote:
On 18.03.2017 07:22, Igor Cicimov wrote:
>uname -a
Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.84-1 x86_64 GNU/Linux
That's an really old kernel, I don't start anything virtual these days
without at least 3.13.x kernel.
I regularly do apt-get upgrade, but
On 18.03.2017 07:22, Igor Cicimov wrote:
>uname -a
Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.84-1 x86_64 GNU/Linux
That's an really old kernel, I don't start anything virtual these days without
at least 3.13.x kernel.
I regularly do apt-get upgrade, but not to next Debian version. So, how
On 17.03.2017 13:21, Dominik George wrote:
iptables -L FORWARD -nv
Chain FORWARD (policy DROP 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
XX ACCEPT all -- br0br0 0.0.0.0/0
0.0.0.0/0
What is that supposed to do?
Forwarding on the IP
prot opt in out source
> destination
> XX ACCEPT all -- br0br0 0.0.0.0/0
> 0.0.0.0/0
>
> Most virtuals does not have networking problems, but some times they can't
> be reached. For now only one virtual machines have this problem:
> From
Hi,
> >iptables -L FORWARD -nv
>Chain FORWARD (policy DROP 0 packets, 0 bytes)
>pkts bytes target prot opt in out source
>destination
>XX ACCEPT all -- br0br0 0.0.0.0/0
>0.0.0.0/0
What is that supposed to do?
Forwarding on the IP layer,
hine ping virtual machine:
>ping 10.10.10.3
Reply from 10.10.10.10: TTL expired in transit.
Reply from 10.10.10.10: TTL expired in transit.
Reply from 10.10.10.10: TTL expired in transit.
Reply from 10.10.10.10: TTL expired in transit.
Request timed out.
Request timed out.
Request timed out.
Requ
On Wed, Nov 09, 2005 at 11:18:07AM -0500, Tony Heal wrote:
> I have a DNS server (Debian woody, bind v8.3.3-2.0woody2) that I need to
> move. It has been suggested that I change the TTL to an hour so that all
> name servers with anything cached will expire during the physical move of my
I have a DNS server
(Debian woody, bind v8.3.3-2.0woody2) that I need to move. It has been suggested
that I change the TTL to an hour so that all name servers with anything cached
will expire during the physical move of my server. Thus reducing my downtime to
the time it take to move the
Shaun Lipscombe wrote:
IIRC You need CONFIG_IP_NF_TARGET_TOS=y to add the TTL target, not the
TTL matching module (which you already have).
Which should of course say CONFIG_IP_NF_TARGET_TTL! Doh!
I'm sure you guessed that though, right? ;-)
eris:/usr/share/doc/kernel-source-2.4.27
Shaun Lipscombe wrote:
* Mart Frauenlob wrote:
eris:~# iptables -t mangle -A PREROUTING -i eth1 -s 192.168.13.0/24 -j
TTL --ttl-inc 1
iptables: No chain/target/match by that name
Do you have module table_mangle loaded ?
modprobe table_mangle
and also these modules:
ipt_TTL for the target
Hello,
i'm running a debian sarge with a self compiled 2.4.27 (debian) kernel
as firewall / router.
What i'm trying to do is to increase the TTL of packets leaving a
certain subnet by one.
Reading the iptables man page this should be able with something like this:
eris:~# i
>>"Nathan" == Nathan E Norman <[EMAIL PROTECTED]> writes:
Nathan> Or just say "to hell with BIND; it's buggy and insecure" and use
Nathan> djbdns instead.
I would, if only it were free.
manoj
--
Speaking as someone who has delved into the intricacies of PL/I, I am
sure that on
On Sun, Feb 11, 2001 at 09:14:44PM -0500, MaD dUCK wrote:
[ snip ]
> ps: look at TTL, retry, refresh, expire, negative TTL, and then join
> in into our chant to paul vixie: "make it intuitive in bind 10! make
> it intuitive in bind 10"!
Or just say "to hell with BIND; it&#
alright, let's clear up this issue...
TTL is time to live, you knew that. time to live is a 32 bit integer
telling resolver caches how long (seconds) to keep an RR in memory.
negative TTL is telling them how long to store errors (no such
domain, minimum 3 hours).
TTL is really time to live
thanks! ill try it out, i still find it odd that it did this for only 2
domains ...these may be the only 2 since i upgraded bind, but i got about
55 others that do not give this error..i suppose i should change all them
as well and add the $TTL at the top of the file as well..
thanks again both
Try adding a value like this to the top of your zone files:
$TTL
a note from the isc states -
(http://www.isc.org/products/BIND/docs/config_hints.html)
config hints for bind 8.2.2:
In BIND 8.2.1, the TTL value in the SOA record now applies to negative
responses only. Add a line "$TTL
hi ya nate
Add the following BEFORE your soa record below
$TTL1
@ IN SOA ns1.firetrail.com. hostmaster.mail.firetrail.com. (
blah blah...
have fun
alvin
> im really not sure what is causing this ..i just added 2 new domains to my
> named and both of them the syste
im really not sure what is causing this ..i just added 2 new domains to my
named and both of them the system says:
Zone "shadowsystem.com" (file primary/db.shadowsystem.com): No default TTL
set using SOA minimum instead
master zone "shadowsystem.com" (IN) loaded (se
22 matches
Mail list logo
