how to disable 'sending IPv6 router solicitation'

[Saifi Khan]

Hi:

How to disable 'sending IPv6 router solicitation' ?

I'm using NetBSD current on AMD64 box with Atheros NIC that connects to a IPv4 router for DHCP assigned address.

x53u# dhcpcd -d -g -L -n -w re0

dhcpcd[23650]: version 5.6.1 starting
dhcpcd[23650]: re0: using hwaddr 10:bf:48:57:16:27
dhcpcd[23650]: re0: executing `/libexec/dhcpcd-run-hooks', reason PREINIT
dhcpcd[23650]: re0: executing `/libexec/dhcpcd-run-hooks', reason CARRIER
dhcpcd[23650]: re0: sending IPv6 Router Solicitation
dhcpcd[23650]: re0: broadcasting for a lease
dhcpcd[23650]: re0: sending DISCOVER (xid 0xfe71caf0), next in 3.20 seconds
dhcpcd[23650]: re0: sending DISCOVER (xid 0xfe71caf0), next in 8.90 seconds
dhcpcd[23650]: re0: sending IPv6 Router Solicitation
dhcpcd[23650]: re0: sending IPv6 Router Solicitation
dhcpcd[23650]: re0: sending DISCOVER (xid 0xfe71caf0), next in 15.87 seconds
dhcpcd[23650]: re0: sending IPv6 Router Solicitation
dhcpcd[23650]: re0: no IPv6 Routers available
dhcpcd[23650]: re0: sending DISCOVER (xid 0xfe71caf0), next in 32.40 seconds
dhcpcd[23650]: timed out

I don't want IPv6 and Zeroconf, rather just plain ipv4 DHCP address.

If i 'reboot' the system, it is able to acquire a ipv4 address, but if i boot the system with no networking (consider it no carrier available), and later attempt the following
# /etc/rc.d/network restart
# dhcpcd -d -g -L -n -w re0
then dhcpcd is not able to acquire the ipv4 address at all.

Any suggestions ?


thanks
Saifi.

[Gary Duzan]

In Message <alpine.NEB.2.00....@localhost.localdomain>,
Saifi Khan <saifi...@fastpath.in>wrote:

=>Hi:
=>
=>How to disable 'sending IPv6 router solicitation' ?

Check to see if you have ip6mode=autohost or rtsol{,d}=YES in /etc/rc.conf .
Comment out those entries if you find them and reboot.

Gary Duzan

[Roy Marples]

On 28/10/2012 14:55, Saifi Khan wrote:
> How to disable 'sending IPv6 router solicitation' ?
>
> I'm using NetBSD current on AMD64 box with Atheros NIC that connects
> to a IPv4 router for DHCP assigned address.
>
> x53u# dhcpcd -d -g -L -n -w re0
>

> I don't want IPv6 and Zeroconf, rather just plain ipv4 DHCP address.

Add noipv6rs to dhcpcd.conf(5)
The next major dhcpcd release will sport the more familiar -4 and -6
options.

> If i 'reboot' the system, it is able to acquire a ipv4 address, but
> if i boot the system with no networking (consider it no carrier
> available), and later attempt the following
> # /etc/rc.d/network restart
> # dhcpcd -d -g -L -n -w re0
> then dhcpcd is not able to acquire the ipv4 address at all.
>
> Any suggestions ?

Don't use -g

Thanks

Roy

[Saifi Khan]

Gary thanks for your reply.

there is no such entry in /etc/rc.conf as i edited every entry in the file myself.

However, the entries in /etc/defaults/rc.conf are

ip6mode=host
rtsol=NO
rtsold=NO

Is there any other option that could possibly trigger 'IPv6 router solicitation' ?


thanks
Saifi.

[Saifi Khan]

Roy thanks for highlighting the option to use.

in fact for me, both the options 'noipv4all' and 'noip6rs' came in handy.

As a long time Gentoo user ;-) i was wondering how is that with just one line entry in /etc/conf.d/net

ifconfig_eth0="dhcp"

the ipv6 router solicitation does not get triggered.

With the focus back to the options in dhcpcd.conf, the behaviour is less magicaland helps keep things straight.


thanks
Saifi.

[Roy Marples]

On 29/10/2012 16:28, Saifi Khan wrote:
> As a long time Gentoo user ;-) i was wondering how is that with just
> one line entry in /etc/conf.d/net
>
> ifconfig_eth0="dhcp"
>
> the ipv6 router solicitation does not get triggered.

It probably does, but it needs dhcpcd-5.6.x or newer to work and that
isn't in the Gentoo stable tree.
Also, depending on how you rolled your kernel you might disable enough
to stop IPv6 functioning at all so dhcpcd won't try it.

> With the focus back to the options in dhcpcd.conf, the behaviour is
> less magicaland helps keep things straight.

Glad to have helped, but out of curiosity why disable IPv6 RS? It just
sends a few ICMP packets during the init phase and then stops dead until
the link resets so it's hardly a burden on the network unlike the
constant polling of DHCPv4 if it's not present.

Thanks

Roy