15 Feb
2013
15 Feb
'13
11:59 a.m.
** Andy Smith <andy(a)bitfolk.com> [2013-02-12 15:03]:
Note that accept_ra is set to 1 for both "eth0" and "all". I'm
not
sure if that's enough to turn autoconfiguration on, but it does
indicate that the above commands weren't run.
Hmm, interesting.
Not so much a good thing, no. The same config is bringing IPv6 up on the other box
(admittedly a later Ubuntu version). This will be irrelevant once I've upgraded this
box too (I hope!), but is a curiousity.
That was the plan. Becoming a moot point now, but still a ciriousity that I may come back
to so I understand it - I do so hate using one solution and not understanding another
potential solution properly!
On Tue, Feb 12, 2013 at 12:29:10PM +0000, Paul Tansom
wrote:
Yup, although I've only just noticed that there's a variable in there for $IFACE!
That copy and paste was a late night 'what the heck I'll try this' type
scenario, which is fine as the server is both local and non-critical :)
If this is in an /etc/network/interfaces file (or script called from
there), then $IFACE is literally correct as it is substituted for
the interface name, e.g. "eth0", that is being worked on.
It won't work if it is called from the command line of course
(unless you set IFACE first).
Yes, run from /etc/network/interfaces
> > post-up echo
"/proc/sys/net/ipv6/conf/default/forwarding=0" && echo 0 >
/proc/sys/net/ipv6/conf/default/forwarding || true
> > post-up echo "/proc/sys/net/ipv6/conf/all/forwarding=0"
&& echo 0 > /proc/sys/net/ipv6/conf/all/forwarding || true
> > post-up echo "/proc/sys/net/ipv6/conf/default/accept_ra=0"
&& echo 0 > /proc/sys/net/ipv6/conf/default/accept_ra || true
> > post-up echo "/proc/sys/net/ipv6/conf/all/accept_ra=0"
&& echo 0 > /proc/sys/net/ipv6/conf/all/accept_ra || true
> > post-up echo "/proc/sys/net/ipv6/conf/$IFACE/accept_ra=0"
&& echo 0 > /proc/sys/net/ipv6/conf/$IFACE/accept_ra || true
> > post-up echo "/proc/sys/net/ipv6/conf/default/autoconf=0"
&& echo 0 > /proc/sys/net/ipv6/conf/default/autoconf || true
> > post-up echo "/proc/sys/net/ipv6/conf/all/autoconf=0"
&& echo 0 > /proc/sys/net/ipv6/conf/all/autoconf || true
> > post-up echo "/proc/sys/net/ipv6/conf/$IFACE/autoconf=0"
&& echo 0 > /proc/sys/net/ipv6/conf/$IFACE/autoconf || true
> > So you're saying you have all the above lines in your
> > /etc/network/interfaces but still end up with a default route to an
> > fe80 address set up by RA? Okay, what is the output of:
$ grep . /proc/sys/net/ipv6/conf/*/{forwarding,accept_ra,autoconf}
please?
For my two servers I have:
paul@humpback:~$ grep . /proc/sys/net/ipv6/conf/*/{forwarding,accept_ra,autoconf}
/proc/sys/net/ipv6/conf/all/forwarding:0
/proc/sys/net/ipv6/conf/default/forwarding:0
/proc/sys/net/ipv6/conf/eth0/forwarding:0
/proc/sys/net/ipv6/conf/lo/forwarding:0
/proc/sys/net/ipv6/conf/all/accept_ra:1
/proc/sys/net/ipv6/conf/default/accept_ra:0
/proc/sys/net/ipv6/conf/eth0/accept_ra:1
/proc/sys/net/ipv6/conf/lo/accept_ra:1
/proc/sys/net/ipv6/conf/all/autoconf:1
/proc/sys/net/ipv6/conf/default/autoconf:1
/proc/sys/net/ipv6/conf/eth0/autoconf:0
/proc/sys/net/ipv6/conf/lo/autoconf:1 paul@minke:~$
grep . /proc/sys/net/ipv6/conf/*/{forwarding,accept_ra,autoconf}
/proc/sys/net/ipv6/conf/all/forwarding:0
/proc/sys/net/ipv6/conf/default/forwarding:0
/proc/sys/net/ipv6/conf/eth0/forwarding:0
/proc/sys/net/ipv6/conf/lo/forwarding:0
/proc/sys/net/ipv6/conf/all/accept_ra:1
/proc/sys/net/ipv6/conf/default/accept_ra:0
/proc/sys/net/ipv6/conf/eth0/accept_ra:1
/proc/sys/net/ipv6/conf/lo/accept_ra:1
/proc/sys/net/ipv6/conf/all/autoconf:1
/proc/sys/net/ipv6/conf/default/autoconf:1
/proc/sys/net/ipv6/conf/eth0/autoconf:1
/proc/sys/net/ipv6/conf/lo/autoconf:1
minke is the one that doesn't bring up the IPv6 on eth0 automatically. The only
difference I've noted here is the eth0/autoconf:1 line.
When you say "doesn't bring up the IPv6 on eth0 automatically" do
you mean that as a good thing, i.e. it is doing the static
configuration that you expect? Note again that some accept_ra and autoconf are set to
1 there so
that still hasn't been disabled like the above commands would do,
although has maybe been disabled "enough".
Anyway, on whichever server is misbehaving, if you went through and set
the above all to 0 where they are 1 I expect you would find that
after a minute or two the global scope v6 address and default route
would disappear.
Both servers are misbehaving, or rather were, both are now playing nicely, but this is
down to the router config change that for some reason has now picked up (it may be the
lack of a reboot, but I'm pretty sure both that is an instant change and that the
router has been rebooted).
... and it
would appear it takes a full reboot of the sever rather than just an ifdown/ifup to sort
things out!
What new settings were you trying to put into effect with ifdown/ifup? Making it run the
post-up commands again?
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
** end quote [Andy Smith]
--
Paul Tansom | Aptanet Ltd. | http://www.aptanet.com/ | 023 9238 0001
======================================================================
Registered in England | Company No: 4905028 | Registered Office:
Crawford House, Hambledon Road, Denmead, Waterlooville, Hants, PO7 6NU