[fedora-arm] Re: pcduino3_nano networking problem.

[Rance Hall]

On Fri, Aug 11, 2017 at 10:03 AM, Peter Robinson <pbrobinson(a)gmail.com&gt;
wrote:

>  On Thu, Aug 10, 2017 at 10:28 PM, Rance Hall <ranceh(a)gmail.com&gt;
> wrote:
>  > Fedora Arm Team:
>  >
>  <snip>
>  >
>  > I don't understand why two different os'es report 2 different mac
>  addresses
>  > for the same physical nic.  I know you can spoof nics, but I've not set
>  this
>  > up so it shouldnt be happening.
>
>  I'm not particularly surprised, in both cases the "stable" MAC is
>  generated based on information in the SoC and I believe the algorithm
>  did change for some reason. Is it stable on that address between
>  reboots of Fedora?
>  
Under Fedora 25, it appeared that the mac address changed when the hostname
changed (like during the first boot wizard).

Under Fedora 26, I didn't notice this behavior so all I can say is that the
reported mac address is stable across reboots, but may not be stable across
other changes.  (not convinced yet, at least).


>  > Also under Fedora 26 the nic can obtain an ip address via dhcp,
> but I've
>  yet
>  > to find a network task it can perform once configured.  It can't ping,
>  use
>  > the tcp stack browse the web, or any other task I tried.
>
>  Is the firewall blocking? What does "iptables -L" show?
>
>  <snip> 
One of the first things I did when troubleshooting was to stop and disable
firewalld with systemctl.

Currently iptables -L reports:

Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination


Thanks for your time.

>  > Rance
>  >
>  > _______________________________________________
>  > arm mailing list -- arm(a)lists.fedoraproject.org
>  > To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>  >
>