hej,
is it possible to predefine the field hardware with the Linux standard names, e.g. br0, br1, br2, when creating a bridge?
hej,
is it possible to predefine the field hardware with the Linux standard names, e.g. br0, br1, br2, when creating a bridge?
Just to be sure: The Hardware name here is the name of the Interface on Linux.
So if you create a Bridge, it will be this name in ifconfig etc.
Example:
SFVUNL_VM01_SFOS 18.0.0 EAP1# ifconfig MyBridge
MyBridge Link encap:Ethernet HWaddr 00:0C:29:C8:3A:66
inet6 addr: fe80::20c:29ff:fec8:3a66/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1712 (1.6 KiB)
So to put brX in this would be only necessary, if you want to stay in this name convention.
__________________________________________________________________________________________________________________
As you can name it "brX" yourself, isn't this unnecessary?
Good naming conventions can be implemented here but as Sophos has diverged greatly from the standard naming conventions in networking on the XG, i don't think this is appropriate?
All my bridges are named BR_ or LAN_BRIDGE
Emile
Well, I'd find it easier if that value was preset. If someone wants to change it, he can do it of course.
With best regards,
Steppenwolf
Hi Steppenwolf,
Unfortunately, you'll probably find an equal amount of people who may not want it pre-configured or pre-set/preceeding.
I know I am in the latter camp, I prefer real names not hardware names but those of a heavily Linux or historically CLI based admin may prefer them to be the hardware names.
At least you have the option of being in either camp :)
Emile
Yes, it is. There are certainly also some who reject a preset.
I would simply like it better if the preset were done automatically, similar to the wireless networks (wlnet1, wlnet2,...).
With best regards,
Steppenwolf