Topic: bond0 appears in server-gateway mode

[kevincallan]

I just upgraded to 7.5.1 from 7.4.  This box used to be in server-only mode but I have switched to server-gateway mode since my other sme server just bit the dust.  It served me well for years.  Thanks to the SME team!

Now, I noticed that the WAN interface is not working.  Went to command line and ifconfig.  It shows bond0 rather than eth1.  I fully expected to see eth0 and eth1.  Any ideas on how to get the bond0 to go away in favor of the eth mode?  I repeated the system configuration to be sure I had correctly made all the changes.  Sure enough, server-gateway mode is selected.

[cactus]

Issues like this should be investigated in the bug tracker as this seems to be a feature that just should work. Please report the issue there and post a reference here once done for future readers. Thanks in advance.

[janet]

kevincallan

This command may correct the settings, although it does not resolve why the problem happened initially.
Please report it to bugzilla. There have been some previous bonding problem reports in bugzilla, although IIRC previous issues were fixed, so search.

config setprop InternalInterface NICBonding disabled
signal-event post-upgrade
signal-event reboot

[kevincallan]

@cactus:

http://bugs.contribs.org/show_bug.cgi?id=6242

[kevincallan]

@mary:

config setprop InternalInterface NICBonding disabled
signal-event post-upgrade
signal-event reboot

This did not resolve the problem.

[CharlieBrady]

This command may correct the settings, although it does not resolve why the problem happened initially.

Worse than that, Mary, this changes the state of the system, and will interfere with investigation of the problem in the bugtracker.

Please do not provide workaround advice in the forum. Please leave that to us to do via the bug tracker (and come there and help us please). To help us to promptly and reliably fix any bugs, we need to collect all relevant evidence before it disappears.

Thanks.

[byte]

Locking thread - Please provide all followup details to the bug tracker. Thanks.