<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Sure will, Jack<br>
<br>
jack wrote:
<blockquote cite="mid:1185195961.5736.13.camel@TMRK-Nebo" type="cite">
<pre wrap="">On Mon, 2007-07-23 at 08:52 -0400, jonathan wrote:
</pre>
<blockquote type="cite">
<pre wrap="">well done sorry that I wasn't much help.
jonathan hopley
deepak wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Disabled ipv6 completely, reinstalled iptables. So far, it seems to
</pre>
</blockquote>
<pre wrap="">be
</pre>
<blockquote type="cite">
<pre wrap="">working fine.
johan wrote:
</pre>
<blockquote type="cite">
<pre wrap="">My opinion too, I use shorewall, based on iptables. Removing
</pre>
</blockquote>
</blockquote>
<pre wrap="">iptables is
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">not an option. I will debug iptables a bit. Or programmers of
</pre>
</blockquote>
</blockquote>
<pre wrap="">iptable
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">here present in this mailinglist ?
Greetz,
Johan
jonathan wrote:
</pre>
<blockquote type="cite">
<pre wrap="">deepak you do know that iptables is the firewall for linux so
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">removing
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">it is not such a good idea.
deepak wrote:
</pre>
<blockquote type="cite">
<pre wrap="">What happened to me was similar. That's why I removed iptables,
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">and
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">there is no problem now.
johan wrote:
</pre>
<blockquote type="cite">
<pre wrap="">hi
since my last upgrade of iptables, file sending amsn doesn't
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">seem to
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">work very well anymore. After a few bytes of sending, the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">sending
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">blocks. Very strange. Also mismatches in packets sent (bytes)
greetz,
Johan
deepak wrote:
</pre>
<blockquote type="cite">
<pre wrap="">After the recent iptables update on my Feisty, my DSL
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">connection would
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">sleep after a few minutes. I tried downgrading it to the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">previous
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">version, but even that did not work. Ultimately, removing it
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">did.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">Any ideas?
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
</blockquote>
<pre wrap="">--
ubuntu-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ubuntu-users@lists.ubuntu.com">ubuntu-users@lists.ubuntu.com</a>
Modify settings or unsubscribe at:
<a class="moz-txt-link-freetext" href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-users">https://lists.ubuntu.com/mailman/listinfo/ubuntu-users</a>
</pre>
</blockquote>
<pre wrap=""><!---->Deepak~
I just saw this again and I have to ask -
What exactly does
</pre>
<blockquote type="cite">
<pre wrap="">">>>>> since my last upgrade of iptables, file sending amsn doesn't
</pre>
</blockquote>
<pre wrap=""><!---->seem to
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">work very well anymore. After a few bytes of sending, the
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="">sending
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">blocks. Very strange. Also mismatches in packets sent (bytes)"
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><!---->this mean?
In particular, what is 'amsn' ?
If it starts sending, and then hangs, it's probably not iptables
directly, since if there were a rule denying sending to a particular ip
address, subnet, net, etc., it would never start.
Mismatches in packets is also not a culprit directly of iptables that
I'm aware of...
I've heard that some people have had to remove ipv6 completely from
Ubuntu and its various implementations (kubuntu, xubuntu, etc) since
version 5, but it usually pointed to other problems which removing ipv6
happened to placate, but not really fix.
I would take a close look at your networking setup first, i.e. - if
you're running gnome, are you using network-manager ? ...
I would also look through the log files in /var/log and try running the
processes you are using from the commandline with a 2nd terminal window
watching the process and/or dmesg for other clues.
I looked back through the thread and didn't notice where you posted any
of your configuration info or output from commands like ifconfig,
netstat, hwinfo, etc to the list. These are usually very helpful in
assisting you with determining the root cause of a particular problem.
I'm glad it seems to be working for you now, but do have a look at the
suggestions above and see if you can discover any other possible
causes...
Jack
</pre>
</blockquote>
</body>
</html>