From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: feldmaus <feldmann_markus@gmx.de>
Cc: netdev@vger.kernel.org
Subject: Re: no IPv6 Routers present
Date: Fri, 13 Mar 2009 07:55:50 -0400 [thread overview]
Message-ID: <49BA49C6.2020007@hp.com> (raw)
In-Reply-To: <loom.20090313T082825-818@post.gmane.org>
feldmaus wrote:
> Vlad Yasevich <vladislav.yasevich <at> hp.com> writes:
>
>> You need to give more information about your interface configurations,
>> routes, and any firewall rules.
> Next Bug, but this one should refer to the kernel i think:
> This one works not. --> <http://nopaste.debianforum.de/19665>
>
> But this one works not --> <http://nopaste.debianforum.de/19664>
>
> I worked out the syslog messages and the differences:
> In the not working configuration i used <NOARP> for eth0.
> I don't know why, but i think it come from ppp0 which
> uses it:
> ########################################################################
> iface dsl-provider inet ppp
> pre-up /sbin/ifconfig eth0 up -arp 0 # line maintained by pppoeconf
> provider dsl-provider
> ########################################################################
>
> I also got some syslog Messages, this are for you:
> ########################################################################
> [ 775.402699] host used greatest stack depth: 5672 bytes left
> ########################################################################
>
> And i ran my <firewalllan> manually, so i got the following:
> ########################################################################
> iptables: Resource temporarily unavailable
> iptables: Resource temporarily unavailable
> iptables: Too many links
> iptables: Resource temporarily unavailable
> iptables: Too many links
> ########################################################################
>
> I think this all comes from NOARP ?
>
> Any Idea ?
You can't use NOARP on a normal network interface without some static neighbor
entries. PPP interfaces do not require ARP since they are point-to-point
and you already know everything about the destination. For ethernet interfaces,
you need arp to resolve the IP to MAC address mappings.
Get rid of NOARP in you eth0 case, and it should work.
-vlad
>
> Regards Markus
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-03-13 11:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 21:05 no IPv6 Routers present Markus Feldmann
2009-03-12 21:41 ` Markus Feldmann
2009-03-12 23:17 ` Vlad Yasevich
2009-03-12 23:32 ` feldmaus
2009-03-13 7:37 ` feldmaus
2009-03-13 8:12 ` feldmaus
2009-03-13 8:36 ` feldmaus
2009-03-13 11:55 ` Vlad Yasevich [this message]
2009-03-13 13:22 ` feldmaus
2009-03-13 15:43 ` Vlad Yasevich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49BA49C6.2020007@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=feldmann_markus@gmx.de \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).