On 06/03/2016 09:51 PM, James Knott wrote:
On 06/03/2016 08:01 PM, Jeremy Baker wrote:
On 06/03/2016 05:59 PM, James Knott wrote:
On 06/03/2016 05:52 PM, Jeremy Baker wrote:
On 06/03/2016 05:28 PM, James Knott wrote:
On 06/03/2016 04:23 PM, Jeremy Baker wrote:
I had no trouble getting dhcpcd to work on Leap, but my connection was pppoe with teksavvy and handled entirely outside of the standard suse configuration - wicked only know about the underlying network interface, not ppp0 How did you get your prefix?
my /etc/ppp/ip-up script was as follows
echo 2 > /proc/sys/net/ipv6/conf/ppp0/accept_ra echo 1 > /proc/sys/net/ipv6/conf/ppp0/forwarding dhcpcd -6 --noipv4ll -t 0 ppp0 & sleep 20 service radvd restart
So you're not using dhcpv6-pd.
Yes I am. What makes you think I'm not?
Well, you said:
I had no trouble getting dhcpcd to work on Leap, but my connection was pppoe with teksavvy and handled entirely outside of the standard suse configuration - wicked only know about the underlying network interface, not ppp0 Implying that something else was doing it.
What I was attempting to imply was that I was using dhcpcd to get my
ipv6 prefix delegation, but it was happening outside of suse's
"automated" configuration. The only part of my config that was done
with yast was for the underlying ethernet interface that is connected to
my dsl modem. Since suse no longer has a dsl option in yast, even my
call to pppd to setup my adsl connection is done from a script I wrote.
--
Jeremy Baker