I would love to, but it's the property of Datacenter :D All I can do is to
adapt my box to it.
On Wed, Sep 28, 2016 at 8:09 PM, Jack Vogel wrote:
> So, time to ditch the DLink I'd say :)
>
> On Wed, Sep 28, 2016 at 9:29 AM, Andrew Savchenko
> wrote:
>
>> I've been using this particular NIC unde
So, time to ditch the DLink I'd say :)
On Wed, Sep 28, 2016 at 9:29 AM, Andrew Savchenko
wrote:
> I've been using this particular NIC under FreeBSD 10.0-REL connected via
> cross cable to another Intel NIC / two different routers / TP-Link switch
> without any similar issues. The problem shows o
I've been using this particular NIC under FreeBSD 10.0-REL connected via
cross cable to another Intel NIC / two different routers / TP-Link switch
without any similar issues. The problem shows only with the mentioned DLink
switch.
On Wed, Sep 28, 2016 at 7:20 PM, Jack Vogel wrote:
> So, I would
So, I would check into the link partner, often times it can be the culprit,
try the nic
in a simple back-to-back setup and see if it makes a diff, etc. etc...
Jack
On Wed, Sep 28, 2016 at 9:03 AM, Andrew Savchenko
wrote:
> Nope, unfortunately they stay dead (aka "no carrier") until `netif
> re
Nope, unfortunately they stay dead (aka "no carrier") until `netif restart`.
On Wed, Sep 28, 2016 at 6:12 PM, Freddie Cash wrote:
> On Wed, Sep 28, 2016 at 8:02 AM, Andrew Savchenko
> wrote:
>
>> MAC's and IP's are abviously changed.
>> For the moment being I have "solved" this by a tiny script
On Wed, Sep 28, 2016 at 8:02 AM, Andrew Savchenko
wrote:
> MAC's and IP's are abviously changed.
> For the moment being I have "solved" this by a tiny script in /etc/rc.d/
> that restarts networking & routing after the system boot:
>
Do the NICs eventually pick up carrier status if you leave it
Doesn't seem like a valid MAC.
>
> Jeff
> -Original Message-
> From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-...@freebsd.org]
> On Behalf Of Steven Hartland
> Sent: Wednesday, September 28, 2016 5:00 AM
> To: freebsd-net@freebsd.org
> Subject: Re: "i
"igb" interfaces aren't picking up media on boot
Try assigning an IP to the interface or manually up it.
On 28/09/2016 12:13, Andrew Savchenko wrote:
> Dear All,
>
> I've moved my lovely server to the datacenter and now pulling my hair out
> while trying to
> un
Try assigning an IP to the interface or manually up it.
On 28/09/2016 12:13, Andrew Savchenko wrote:
Dear All,
I've moved my lovely server to the datacenter and now pulling my hair out
while trying to
understand why both of /dev/igb interfaces aren't picking up Ethernet
connection on boot.
Test
