GUI Network Config?

l008com

l008com

I know you guys are going to hate this question.

But I got xfce4 running but I was surprised how limited the system settings are.

Is there any GUI app for setting up networking/tcpip settings?
I know, its freebsd, ya'll do everything via command line and .conf files. But please, humor me :)
 
Hrmmm, I have used webmin in the past but I'd rather not use it here, I'd prefer something more traditional.
And networkmgr does seem to work, but in a very odd way.
I have a feeling I'll be learning how to setup more advanced network features via the command line :/
 
Basic IP address, mask, router, for each interface. But also additional connections for each interface. This is ultimately going to be a server with two ethernet ports with two physical connections, each one being used a little differently than the other.
 
l008com said:
Basic IP address, mask, router, for each interface. But also additional connections for each interface. This is ultimately going to be a server with two ethernet ports with two physical connections, each one being used a little differently than the other.
Click to expand...
Do you have a DHCP server?

What does ifconfig show?
 
Well I DO have a dhcp server but I will be setting up a static LAN IP temporarily and then some static public IPs on the final, real server.
 
Basic command; ifconfig <interface> inet <ip address> netmask <subnet mask>, for example; ifconfig em0 inet 1.2.3.4 netmask 255.255.255.0

Or, in rc.conf:
Code: 
ifconfig_em0="inet 1.2.3.4 netmask 255.255.255.0"
 
l008com said:
Well I DO have a dhcp server but I will be setting up a static LAN IP temporarily and then some static public IPs on the final, real server.
Click to expand...
You can set up a dhcp server to serve IP address based on MAC address in which case you only need to specify

ifconfig_emX="DHCP"

in /etc/rc.conf on your FreeBSD system.

You need to replace emX with whatever your system assigns as your interface name.
 
SirDice said:
Basic command; ifconfig <interface> inet <ip address> netmask <subnet mask>, for example; ifconfig em0 inet 1.2.3.4 netmask 255.255.255.0

Or, in rc.conf:
Code: 
ifconfig_em0="inet 1.2.3.4 netmask 255.255.255.0"
Click to expand...

So is the way this works, that the command only works until a reboot, and the rc.conf line works 'permanently'?

Also, how would I set up two separate IPs on the same interface?
 
l008com said:
I have a feeling I'll be learning how to setup more advanced network features via the command line :/
Click to expand...
Yep, that's basically what is going to happen, but in the end it's not a bad thing because it helps a bit to understand what you do.

l008com said:
Basic IP address, mask, router, for each interface. But also additional connections for each interface. This is ultimately going to be a server with two ethernet ports with two physical connections, each one being used a little differently than the other.
Click to expand...
Additionally to what SirDice said you'll likely find lot of information in the handbook, there is a network section with examples and explanations:
docs.freebsd.org

Chapter 7. Network

This chapter delves into the topic of network configuration and performance, showcasing the robust networking capabilities of the FreeBSD operating system.
docs.freebsd.org docs.freebsd.org
 
Another helpful thing is the man(8) ifconfig() page. It has examples. For instance, you ask about two addresses on one interface, in the man page, search for alias. You'd want something like (using re0 as interface),
Code: 
ifconfig_re0_alias0="192.168.1.5 netmask 255.255.255.255"
under the line giving it its main address, in /etc/rc.conf
.
 
Don't forget to set a gateway if you go the static IP route (pun definitely intended). Or you will not be able to reach anything beyond your subnet.

On the CLI: route add default 1.2.3.4
In rc.conf: defaultrouter="1.2.3.4"

Or a specific static route: route add -net 10.0.0.0/8 192.168.10.1
rc.conf
Code: 
static_routes="myroute"
route_myroute="-net 10.0.0.0/8 192.168.10.1"

On FreeBSD the gateway address MUST be reachable on any of the directly connected networks (in other words, be on the same subnet as your interfaces).

DNS settings are done in /etc/resolv.conf, there's no CLI command to set this. Changes are immediately active, nothing needs to be restarted.

Code: 
nameserver 1.1.1.1
nameserver 8.8.8.8

Needs at least one nameserver and can have a maximum of 3 nameserver entries. Each will be queried in the order they appear. The second (or third) will only be queried when a request to the first timed out.

You typically also want to set domain or search so resolving "short" names works as expected.
 
Someof the DEs don't install everything that they could. Basically lots of plugins that may be pulled in automatically on a Linux distro you need to manually do on FreeBSD.
Now, a GUI to manipulate network interfaces: I start at "do you need to? If so why? Is system config not good enough?"
If you find a GUI that does everything you need, I would ask "is it doing so for only this user or for the system at large?"
Yes, I'm a "can't stand GUI for a lot of stuff" but I understand if some want it.
 
Now understanding what op wants to do (multi-homed server config) I think the "correct" way is with command line and conf files. It has been my experience that network config GUIs are more focused on convenience for single homed DHCP workstations or managing WIFI connections on laptops. Anyway, just my opinion based on personal experience.
 
DanielBowman said:
Works very well. With wifi and all. It is the GUI network manager in GhostBSD after all.
But...you need to add it to STARTUP applications in XFCE (SEESION MANAGER?) manually.
And the user thus needs to be in Operator group (I think).
Click to expand...
No need to add to startup application, it must be inserted in the panel (panel plugin). Click on it to display a menu for enable/disable network card(s) and configure them.

netmgr.jpg
 
You must log in or register to reply here.
Back
Top