[SOLVED] second NIC does not accept IP-Address

[drnicolas]

A few months ago, I started a post about problems with the second NIC which should connect directly to a vsphere-machine via cross-over cable.

But after each reboot, I see that the second NIC has no IP-adress assigned.
Today, I upgraded to the latest firmware (embedded), but no change

The screenshot attached shows the result of the diagnostics page and another the settings for the second NIC. They are different! And I have no explanation fr that.!




Merry Christmas!

[raulfg3]

Post your OPT config

[drnicolas]

What does that mean? I think , I posted already the config for the second NIC as you can see

[octave]

hi

you have on gui network interface manager to adding all nic to could setup it
so after you will have
lan interface
opt1 for second one
opt2 if you have more
opt3 ..

[drnicolas]

This is what I have ... Hope that helps
Merry christmas!

[raulfg3]

Change name from LAN2 -cross-over to OPT and reset NAS. Then try to assing New IP.

If not work. Try the same from shell. Option 1. Reset andres Then Option 2.

[drnicolas]

No change after changing name (which seems only to be a description to "OPT".
Assigning an IP again and restarting still no change

See the attached screenshot.
Isn't that funny? I just recognized that the status page does not give the Ip-adress, even not from the LAN1 interface - only the gateway

Also MTU is listed as 1500 while the settings page clearly says 6000!

[raulfg3]

Em0 is Intel and support MTU 9000.

What max MTU support bge?

[drnicolas]

It should be a realtek chip on my N54L. AFAIK MTU max is 6000

[raulfg3]

See: https://forums.freebsd.org/threads/28053/

[drnicolas]

This is what I did the last minutes:
- deleted OPT1
-reboot
-setup OPT1 again, assign 10.0.0.1 as shown in the screenshot
-reboot

-No change

this is the output from ifconfig

Code: Select all

hp-nas: ~# ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 6000
        options=4319b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MCAST,WOL_MAGIC,VLAN_HWTSO>
        ether 68:05:ca:1a:4b:81
        inet 192.168.1.252 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=c019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE>
        ether 28:92:4a:32:03:e7
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex,master>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        groups: lo
hp-nas: ~#

bge0 constantly regrets to accept the IP-adress!
Now, manually:

Code: Select all

hp-nas: ~# ifconfig bge0 inet 10.0.0.1 netmask 0xffffff00
hp-nas: ~# ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 6000
        options=4319b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MCAST,WOL_MAGIC,VLAN_HWTSO>
        ether 68:05:ca:1a:4b:81
        inet 192.168.1.252 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=c019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE>
        ether 28:92:4a:32:03:e7
        inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex,master>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        groups: lo
hp-nas: ~#

This works, but only for the moment. After a reboot, the IP is lost again!

[xr4t3d]

drnicolas,

I just noticed this thread, I saw the CLI you entered initially and thought this may be the reason its not working. The Subnetmask characters your using may be incorrect. Depending on your LAN Network Configurations, this will dictate what your Subnet should be. Check your router and advise what your LAN Subnet Mask is? Or if you have another computer on the same LAN, check that PC and see what the SubnetMask is.

ifconfig bge0 inet 10.0.0.1 netmask 0xffffff00 < --- This is what you had...

ifconfig bge0 inet 10.0.0.1 netmask 255.255.255.0 < --- Thinking this is what it should be or something similar, depending on what you may have setup in your router.

Let me know if this helps!


Regards,

John

[drnicolas]

In fact, the second NIC should only be linkes to my vSphere machine via a cross-link cable - no router.

As you can see, I have configured the NICs both by GUI, but the second does not get an IP attached at boot.
As a consequence, iSCSI does not work

But I can manually attach the IP via comandline. I will try your command, but I don't think that this fixes the problem that GUI settings are not applied at boot.

[xr4t3d]

Can you check your router for the LAN IP Network Settings? Or check another functional computer and check the IP and Subnet of that computer. Please post that, its should be a Local IP so it shouldnt be that much of a risk. Your IP Address should be a private IP..

[drnicolas]

it is now several months since my last posting for the initial problem:

The second NIC does not get the intended IP-address assigned on a reboot.

I have upgraded my NAS4Free through half a dozen versions now and it stays always the same:

According to the Web-GUI my second NIC (which is bge0) has IP 10.0.0.1/24 and it is named OPT1

But after a reboot ifconfig shows correct values for em0, but no IP for bge0!

Code: Select all

ifconfig bge0 inet 10.0.0.1 netmask 255.255.255.0

cures the problem.

Also, I have to send

Code: Select all

/etc/rc.d/isci-target restart

via command-line.
The second NIC with 10.0.0.1 is exclusively dedicated to my iscsi-target which serves as a datastore for my ESXi 6.5.

Therefore each reboot of my NAS kills some of the VMs running on the ESXi until I do the manual configuration for the second NIC

In the meantime I found, that /ect/rc.conf contains a line

Code: Select all

ifconfig_bge0="10.0.0.1/24 mtu 5000

.
Sounds okay?

[drnicolas]

I have found a solution for my Problem:

AFAIK this behaviour is caused by the MTU Setting in /etc/rc.conf:

Code: Select all

ifconfig_bge0="10.0.0.1/24 mtu 5000"

Providing a wrong mtu causes the whole line to fail. This Setting Comes from the Web-GUI!

Trying to set mtu manually via commandline ifconfig causes an error "invalid Argument" which may be related to my NIC!
Actually, my built-in NIC does not accept any mtu-value - not 9000, not 6000 or anything else than 1500.

Solution: Try out a suitable mtu-value from command-line with "ifconfig" and THEN set this value within the Web-GUI accordingly.
Now the Setting survives a reboot.

But it is unknown for me, why the mtu cannot be set to at least 6000.

Feature request: Check the mtu value directly for correctness directly from Web-GUI