I'm having the "link state changed to DOWN/UP" problem on a GigE link
between two FreeBSD re(4) devices. Both systems are releng/10.0.
It is flapping a lot... as much as several times a minute. The link
is down for 3 seconds, when it comes up dhclient takes a bit longer
to re-init the IP. It is
It seems we have no driver for the Realtek RTL8191SE/RTL8192SE WiFi
chipset.
Tried using NDIS with the Windows driver, but no luck there, either.
Attaching the pciconf info for this device. Anyone working in this
area?
Thanks,
-jr
toshiba_l675.pci
Description: Binary data
_
Folks,
I have implemented IPv6 DNS autoconfiguration using the method described
in RFC6106 which describes RDNSS and DNSSL options on ICMPv6 router
advertisements.
This implementation involves:
- updates to rtadvd to send RDDNS and DNSSL options
- updates to rtsold to receive the
On Fri, 18 Mar 2011 19:48:11 +0500, "Eugene M. Zheganin"
wrote:
>
> I have a working rtadvd on a router, and a working DHCPv6 setup.
> But my client FreeBSD still gets 64 prefix length, with or without
> running rtsold.
> Since DHCPv6 doesn't advertise any routing information at all (including
On Thu, 17 Mar 2011 13:45:14 -0400, "J.R. Oldroyd" wrote:
>
> I have implemented IPv6 DNS autoconfiguration using the method
> described in RFC6106 which describes RDNSS and DNSSL options on
> ICMPv6 router advertisements.
>
I see this has been downloaded a bunch of tim
I have updated the rtadvd patch to allow greater flexibility in configuring
DNS servers and search domains in rtadvd.conf.
The new patch allows comma-separated values in the "rdnss=" and "dnssl="
entries and now sends separate RA RDNSS and DNSSL options for each such
entry. This allows separate l
On Thu, 21 Apr 2011 02:45:15 +0400, Lev Serebryakov wrote:
>
> Hello, Freebsd-net.
>
> Is here any stateless dhcp6 solution for FreeBSD?
>
> I need only distribute IPv6 DNS server addresses to clients, but not
> prefixes or address information.
>
DHCP is stateful. If you want stateless,
On Thu, 04 Aug 2011 23:52:54 -0700, Doug Barton wrote:
>
> On 08/04/2011 22:59, Mattia Rossi wrote:
> > I've finally patched my 8.2 IPv6 gateway with the RDNSS/DNSSL patches
> > The script anyhow overwrites my previous manual entries in
> > /etc/resolv.conf which I need for my manual IPv4 setup...
On Mon, 08 Aug 2011 10:46:16 +1000, Mattia Rossi wrote:
>
> I'm using the patches from your website on my 8.2 box, which is the IPv6
> gateway and runs rtadvd. The problem with the resolv.conf is happening
> on my client though, which is a box running HEAD, so I'll try to follow
> Doug's advic
On Tue, 7 Apr 2015 14:53:54 + Brooks Davis wrote:
>
> On Mon, Apr 06, 2015 at 08:13:56PM -0700, Yuri wrote:
> > I am observing what dhclient sends to the server. Source IP of the
> > packet it sends is the previous DHCP lease. This address doesn't exist
> > any more, because I manually delet
On Wed, 8 Apr 2015 20:47:56 -0700 Kevin Oberman wrote:
>
The
> idea is that a system should attempt to maintain the same address, if
> possible. That is why the dhclient.leases files are there. Even if a system
> has its interface shut down or is rebooted, the file contains the last
> assigned add
On Thu, 9 Apr 2015 10:40:17 +0200 "J.R. Oldroyd" wrote:
>
>
> The fix appears to be pretty trivial:
I have submitted PR 199378 with this patch.
-jr
pgpH2wUWpRqmW.pgp
Description: OpenPGP digital signature
I have just had occasion to use a vge(4) as an interface to as DSL
modem.
When using the same DSL link with an fxp(4), a dc(4) or an axe(4)
interface, various DSL speed tests on the net show the line at its
correct speed of 1536/384 (up/down).
But on the vge(4) interface downloads are noticably s
On Tue, 18 Oct 2016 14:43:13 +0300 "Zeus Panchenko" wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I'm using lagg(4) in failover to set up roaming between wired and
> wireless networks, just as manual describes (last example) and all
> was working perfectly on 11-CURRENT
>
> now
An em(4) interface configured with fixed media/mediatype settings, as in:
ifconfig em0 media 100baseTX mediatype full-duplex
does not respond to autonegotiation from the switch it is connected to.
(Actually, it does for 1000base but not for 100base or 10base.) As a
result, the switch may e
On Wed, 2 Mar 2022 17:21:22 +0100 Lutz Donnerhacke wrote:
>
> On Wed, Mar 02, 2022 at 04:40:38PM +0100, tue...@freebsd.org wrote:
> > Is that what is expected? When using the above command I would expect
> > that 100MBit/sec is used, not that the card negotiates with the peer
> > something else. B
16 matches
Mail list logo
