Gargoyle Forum

Posted: **Thu Sep 12, 2019 4:32 am**

Little step forward, the eth1 is ok, but when I configure a PPPoe connection (as openwrt), gargoyle trunk any connection and is no more reachable in lan.
The router give a loop error in console about the eth0 IPv6 (that I don't need):
IPv6: ADDCONF (NETDEV_UP): eth0: link is not ready
8021q: addin VLAN 0 to HW filter on device eth0
e1000 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

In your esxi instance I think don't you have this issue, what version of Gargoyle do you use?
Have you some others suggestion to solve the issue?
Thank you for your time

Code: Select all

Gargoyle version 1.11.X   | OpenWrt 18.06 branch               |
| Gargoyle revision 54be0a9e| OpenWrt commit 70255e3             |
| Built August 19, 2018     | Target  x86/x64                    |
------------------------------------------------------------------
root@GargoyleESXI:~# ifconfig
br-lan    Link encap:Ethernet  HWaddr 00:0C:29:C6:E4:F1
          inet addr:192.168.10.154  Bcast:192.168.10.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:fec6:e4f1/64 Scope:Link
          inet6 addr: fdb1:36ba:f5f4::1/60 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:174 errors:0 dropped:0 overruns:0 frame:0
          TX packets:162 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:19099 (18.6 KiB)  TX bytes:25616 (25.0 KiB)

eth0      Link encap:Ethernet  HWaddr 00:0C:29:C6:E4:F1
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:174 errors:0 dropped:0 overruns:0 frame:0
          TX packets:162 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:21535 (21.0 KiB)  TX bytes:25742 (25.1 KiB)

eth1      Link encap:Ethernet  HWaddr 00:0C:29:C6:E4:FB
          inet6 addr: fe80::20c:29ff:fec6:e4fb/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:286 (286.0 B)  TX bytes:5272 (5.1 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2201 (2.1 KiB)  TX bytes:2201 (2.1 KiB)

Posted: **Thu Sep 12, 2019 5:31 am**

Are you using the Gargoyle GUI to configure it?
Can you post a copy of your /etc/config/network, as well as the contents of /etc/gargoyle_default_ifs

Posted: **Thu Sep 12, 2019 5:50 am**

For the PPPoE connection I use the webgui.
I have restored the snapshot before the PPPoE connection but with the eth1 functional.
The problem is with the file /etc/gargoyle_default_ifs.
Do you think that this issue is only for ESXI or the x86 profile must be fixed for all baremetal?
Thank you very much for your support

Changed to

Code: Select all

default_lan_if	eth0
default_wan_if	eth1
default_wan_mac	00:0C:29:FA:06:24

Now work like a charm.

Code: Select all

eth0      Link encap:Ethernet  HWaddr 00:0C:29:C6:E4:F1
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6779 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5913 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:638761 (623.7 KiB)  TX bytes:1387066 (1.3 MiB)

eth1      Link encap:Ethernet  HWaddr 00:0C:29:C6:E4:FB
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:279 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1216 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:99127 (96.8 KiB)  TX bytes:383328 (374.3 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:38 errors:0 dropped:0 overruns:0 frame:0
          TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3043 (2.9 KiB)  TX bytes:3043 (2.9 KiB)

pppoe-wan Link encap:Point-to-Point Protocol
          inet addr:*.*.*.37  P-t-P:192.168.100.1  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
          RX packets:89 errors:0 dropped:0 overruns:0 frame:0
          TX packets:97 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:83431 (81.4 KiB)  TX bytes:6208 (6.0 KiB)

/etc/config/network

Code: Select all

config interface 'loopback'
	option ifname 'lo'
	option proto 'static'
	option ipaddr '127.0.0.1'
	option netmask '255.0.0.0'

config globals 'globals'
	option ula_prefix 'fdb1:36ba:f5f4::/48'

config interface 'lan'
	option type 'bridge'
	option ifname 'eth0'
	option proto 'static'
	option netmask '255.255.255.0'
	option ip6assign '60'
	option dns '8.8.8.8 8.8.4.4'
	option ipaddr '192.168.10.154'
	option gateway '192.168.10.254'

config interface 'wan'
	option ifname 'eth1'
	option proto 'dhcp'

/etc/gargoyle_default_ifs

Code: Select all

default_lan_if	eth0
default_wan_if	eth0
default_wan_mac	00:0C:29:FA:06:24

Posted: **Thu Sep 12, 2019 7:00 am**

As long as you are now sorted, that's a good outcome.

The fact that the setup script never ran or was missing is a concern, which I will look into.
There's also a possibility that if that script doesn't run early enough that the default ifs file gets the wrong data. Will need to look at that also.

Basically you've given me quite a few things to look at, and they're probably relevant to all x86, not just ESXi.

Thanks for your patience.

Posted: **Thu Sep 12, 2019 7:08 am**

Thanks to you for your work and your passion for this project.

Posted: **Fri Sep 13, 2019 12:43 pm**

Just for info, with the latest firmware x86/64 combined ext4 of 30 July from ispyisail the eth1 work correctly without any additional config.

Posted: **Fri Sep 13, 2019 6:34 pm**

Great, I was seeing the same behaviour.

Gargoyle Forum

Gargoyle on ESXI 6.7 eth1 issue

Re: Gargoyle on ESXI 6.7 eth1 issue

Re: Gargoyle on ESXI 6.7 eth1 issue

Re: Gargoyle on ESXI 6.7 eth1 issue

Re: Gargoyle on ESXI 6.7 eth1 issue

Re: Gargoyle on ESXI 6.7 eth1 issue

Re: Gargoyle on ESXI 6.7 eth1 issue

Re: Gargoyle on ESXI 6.7 eth1 issue