disable ipv6 on slackware 13.1

[Durgesh O Mishra]

Hi Experts,

I have slackware 13.1 running on virtualbox. When I enable NAT mode
for network adaptor-1, I see ifconfig -a print the IPv4 as well as
IPv6 addresses.

However when I enable bridge mode for network adaptor-1, I see only
IPv6 address with ifconfig -a.


eth0 Link encap:Ethernet HWaddr 00:1c:c4:e2:18:52
inet6 addr: fe80::21c:c4ff:fee2:1852/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1948 (1.9 KiB)


How can I disable the IPv6 and enable IPv4 for bridged mode ?

Please help.

Kind Regards
Durgesh O Mishra

[Ron]

Make an automatic analysis of your slackware server:

http://java-apps.org/content/show.php/DatacenterManager?content=144298



Op 16-11-11 wk 46 14:11, Durgesh O Mishra schreef:

[Aragorn]

On Wednesday 16 November 2011 21:19, Ron conveyed the following to
alt.os.linux.slackware...

> Make an automatic analysis of your slackware server:
>
> http://java-apps.org/content/show.php/DatacenterManager?content=144298

Ron, I don't mean to be a netcop, and I appreciate the fact that you are
offering your software for free, but I'm afraid I'm going to have to be
giving you some friendly advice here, even if only because nobody has
done that so far.

1) Please stop top-posting. Use interleaved replying, like the rest
of us.

2) Please stop spamming just about every Usenet newsgroup I'm
subscribed to. Yes, I have looked at your software, and while it
may be good, there is no need for you to seek out random posts on
Usenet in both generic UNIX and GNU/Linux-specific newsgroups and
then offer your software as a miracle solution for everyone's
problems. Your software may be a valuable tool, but it doesn't
actually /solve/ the problem, and I have seen you advertise your
software to questions that had nothing to do with what your
software is intended for. As good as your software may be, if
you're going to be spamming for it, then you're going to be driving
people away from it, rather than towards it. I should think that
this is not your objective.

3) If you want to advertise your software in a less obtrusive way,
do it via your signature block, not in the body of the message.

Trust me. Being humble and helpful wil win you and your software more
sympathy than spamming the newsgroups.

Hope this was useful to you. Have a nice day.

--
= Aragorn =
(registered GNU/Linux user #223157)

[Ron]

Op 16-11-11 wk 46 22:07, Aragorn schreef:

Hi Aragorn,

I know and you're right, but if only unix users would know what power
that software has, it's just amazing.
I've solved datacenter wide performance issues in a couple of hours
where the admin's searched for years and couldn't find / solve it.

I'll try to be more specific in finding enthusiasts for my software.

I appreciate your politeness and thanks for trying DCM anyway!

Regards,

Ron

[Pascal Hambourg]

Hello,

Durgesh O Mishra a écrit :
> Hi Experts,

Experts only ? What about other readers ?

I am not going to answer your question because I think the issue you
describe is not related to IPv6. The link-local IPv6 address is present
regardless of the networking mode.

Usually, NAT mode provides a virtual DHCP server so that the virtual
guests can get an IPv4 address from DHCP. Bridged mode does not, so if
there is no DHCP server on the bridged network then virtual guests using
DHCP for IPv4 configuration won't get an IPv4 address.

[Jerry Peters]

# Disable ipv6:
if [ -e /proc/sys/net/ipv6/conf ]; then
for i in /proc/sys/net/ipv6/conf/*/disable_ipv6 ; do
echo -n '1' > "$i"
done
fi

Or if your kernel has a modular ipv6:

add "blacklist ipv6" somewhere in /etc/modprobe.d/


Jerry

[Kees Theunissen]

Jerry Peters wrote:
> # Disable ipv6:
> if [ -e /proc/sys/net/ipv6/conf ]; then
> for i in /proc/sys/net/ipv6/conf/*/disable_ipv6 ; do
> echo -n '1'> "$i"
> done
> fi

Or just specify "ipv6.disable=1" at boot time as a kernel parameter
for a kernel with ipv6 compiled in.
Look for "append=" and "addappend=" in the lilo.conf(5) manpage for
info about specifying kernel parameters.

>
> Or if your kernel has a modular ipv6:
>
> add "blacklist ipv6" somewhere in /etc/modprobe.d/

Regards,

Kees.

--
Kees Theunissen

[Ivan Shmakov]

The IPv6 address above in a link-local one, and it's not going
to interfere with IPv4 networking in any way. In particular, I
doubt that disabling IPv6 will bring any of the the magic
necessary to make IPv4 available.

As for the IPv4 availability, my guess is that configuring
VirtualBox to perform NAT also makes it pose as a DHCPv4 server
for the guest. On the contrary, when bridged access is
configured instead, VirtualBox assumes that the guest is going
to use an external DHCP server, thus its own internal one is
disabled. And if there's none, the guest is left unconfigured.

If it's indeed the case, then the solution to the problem would
be to either configure a DHCP server for the outer network, or
to configure the guest manually, as in, e. g.:

# ip addr add 192.0.2.34/24 dev eth0
# ip route add default via 192.0.2.1
#

Of course, IPv6 may be left enabled.

--
FSF associate member #7257