Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 31 Jul 2017 17:54:03 +0200 (CEST)
From:      =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no>
To:        Mike Tancsa <mike@sentex.net>
Cc:        freebsd-questions <freebsd-questions@freebsd.org>
Subject:   Re: default route via SLAAC not working ?
Message-ID:  <alpine.BSF.2.21.1707311753200.1133@mail.fig.ol.no>
In-Reply-To: <3e0e0362-d8c8-5f85-46dc-f4e103f78fc2@sentex.net>
References:  <96b09a19-01e1-e182-e9c0-d1526a12373f@sentex.net> <alpine.BSF.2.21.1707311727060.1133@mail.fig.ol.no> <3e0e0362-d8c8-5f85-46dc-f4e103f78fc2@sentex.net>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Mon, 31 Jul 2017 11:52-0400, Mike Tancsa wrote:

> On 7/31/2017 11:31 AM, Trond Endrestøl wrote:
> > 
> > I haven't tried USB Ethernet, maybe there's an IPv6 issue with ue(4), 
> > I hope not.
> > 
> > Anyway, in /etc/rc.conf, your interface lines should look something 
> > like:
> > 
> > ifconfig_em0_ipv6="inet6 accept_rtadv"
> > 
> > Also, ipv6_defaultrouter must be empty for SLAAC to work.
> > 
> 
> Hi,
> 	Thanks for the reply.  Yes, I have
> 
> # egrep "ue0|ipv6" /etc/rc.conf
> 
> ifconfig_ue0="DHCP"
> ifconfig_ue0_ipv6="inet6 accept_rtadv"
> ipv6_network_interfaces="ue0"
> 
> Is there a way to manually force a solicitation by the interface ?

rtsol(8), e.g. rtsol ue0 or rtsol -a.

-- 
Trond.
From owner-freebsd-questions@freebsd.org  Mon Jul 31 16:00:54 2017
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 46621DB2D50
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Mon, 31 Jul 2017 16:00:54 +0000 (UTC)
 (envelope-from freebsd@edvax.de)
Received: from mailrelay15.qsc.de (mailrelay15.qsc.de [212.99.187.254])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.antispameurope.com",
 Issuer "TeleSec ServerPass DE-2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 869BC81C59
 for <freebsd-questions@freebsd.org>; Mon, 31 Jul 2017 16:00:52 +0000 (UTC)
 (envelope-from freebsd@edvax.de)
Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay15.qsc.de;
 Mon, 31 Jul 2017 18:00:44 +0200
Received: from r56.edvax.de (port-92-195-203-176.dynamic.qsc.de
 [92.195.203.176])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx01.qsc.de (Postfix) with ESMTPS id E61963CC3F;
 Mon, 31 Jul 2017 18:00:41 +0200 (CEST)
Received: from r56.edvax.de (localhost [127.0.0.1])
 by r56.edvax.de (8.14.5/8.14.5) with SMTP id v6VG0foJ002996;
 Mon, 31 Jul 2017 18:00:41 +0200 (CEST)
 (envelope-from freebsd@edvax.de)
Date: Mon, 31 Jul 2017 18:00:41 +0200
From: Polytropon <freebsd@edvax.de>
To: byrnejb@harte-lyne.ca
Cc: freebsd-questions@freebsd.org
Subject: Re: Unable to mount USB Flash memory created on CentOS
Message-Id: <20170731180041.d8ed6af0.freebsd@edvax.de>
In-Reply-To: <72688c988dae728f8fe92593aa464dc7.squirrel@webmail.harte-lyne.ca>
References: <a491848b72ef4dc2282175cccf09e115.squirrel@webmail.harte-lyne.ca>
 <20170728223744.a94ce254.freebsd@edvax.de>
 <fc164e1b20c58429cb8f5dbb5ae876b5.squirrel@webmail.harte-lyne.ca>
 <20170729110144.1cce7c70.freebsd@edvax.de>
 <72688c988dae728f8fe92593aa464dc7.squirrel@webmail.harte-lyne.ca>
Reply-To: Polytropon <freebsd@edvax.de>
Organization: EDVAX
X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-cloud-security-sender: freebsd@edvax.de
X-cloud-security-recipient: freebsd-questions@freebsd.org
X-cloud-security-Virusscan: CLEAN
X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on
 mailrelay15.qsc.de with 90B526834F7
X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14
X-cloud-security: scantime:.4101
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>;
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Jul 2017 16:00:54 -0000

On Mon, 31 Jul 2017 11:49:52 -0400, James B. Byrne wrote:
> When I try to verify the flash drives I see this:
> 
> # e2fsck /dev/da1
> e2fsck 1.43.4 (31-Jan-2017)
> ext2fs_open2: Bad magic number in super-block
> e2fsck: Superblock invalid, trying backup blocks...
> e2fsck: Bad magic number in super-block while trying to open /dev/da1
> . . .
> 
> So I redid the command using the partition values instead:

Fully correct. You need to specify the "thing" that holds the
ext2 file system, in this case, a partition (slice).



> # e2fsck /dev/da0s1
> e2fsck 1.43.4 (31-Jan-2017)
> CA_HLL_2016_BKUP has gone 267 days without being checked, check forced.
> Pass 1: Checking inodes, blocks, and sizes
> Pass 2: Checking directory structure
> Pass 3: Checking directory connectivity
> Pass 4: Checking reference counts
> Pass 5: Checking group summary information
> Error writing file system info: Invalid argument
> 
> CA_HLL_2016_BKUP: ***** FILE SYSTEM WAS MODIFIED *****
> 
> However, the device remains unmountable in Mate.

Why "however"? The file system hasn't been repaired, and that's
why it cannot be mounted. I think there should have been an
additional message saying something like "file system still
dirty, re-run fsck".

But I _highly_ recommend using a Linux _native_ fsck program,
maybe even from a live system CD, DVD, or USB stick. The ext2
tools on FreeBSD aren't that advanced or "stable" that I would
trust them with lower-level file system repairs.

After the file system has been repaired _and_ marked clean,
you should be able to mount it. Do _not_ expect it to work in
the current inconsistent state.



> This issue is not critical as I am able to manually mount both devices
> and have successfully moved their contents onto new media.  But I do
> find it annoying that Mate, or whatever process caused the initial
> problem, was able to create the problem and yet there is no
> self-evident way of correcting whatever injury was done to the
> filesystems.

I think the automounter buried within the desktop system is
responsible here, but there is no way to really be sure.



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.21.1707311753200.1133>