Opened 8 months ago

Closed 8 months ago

#964 closed System Defect (worksforme)

Control Panel/Network Configuration - serious issues!

Reported by: geostar Owned by: kenmoore
Priority: critical Milestone:
Component: Network Manager Version: 10.0-RELEASE
Keywords: networking lan Cc: trac-bugs@…

Description

GUI-Network Configuration completely broken, in my system.
Cannot set Dynamic, Static LAN/IP or DNS.
The input window for static LAN/IP does not retain entries.
The Network Configuration GUI hangs and freezes
Changes are not recorded in /etc/networks

My dmesg output is attached as sysinfo.txt, with this message.

Attachments (4)

sysinfo.txt (20.1 KB) - added by geostar 8 months ago.
dmesg output
sysinfo.zip (4.3 KB) - added by geostar 8 months ago.
dmesg zipped
sys-net-setup.zip (1.7 KB) - added by geostar 8 months ago.
net-conf.zip (32.2 KB) - added by geostar 8 months ago.

Download all attachments as: .zip

Change History (16)

Changed 8 months ago by geostar

dmesg output

Changed 8 months ago by geostar

dmesg zipped

comment:1 Changed 8 months ago by geostar

With reference to the original ticket #964, as above:

My other operating systems that run, ran or were tested on the computer system had/have no issues with the Ethernet interfaces or networking, under real or virtual operation modes. Those include:
MSOS-Windows7, PCBSD-9.1, OpenSUSE-13.1, in real machine mode.

Also, the same PCBSD-10_Release OS had no issues with networking, while running as the guest OS in Vbox-4.3.6.

comment:2 Changed 8 months ago by joshms

  • Owner set to kenmoore

comment:3 follow-up: Changed 8 months ago by kenmoore

It looks like it is working fine here.
How are you starting the utility? It needs root permissions in order to be able to save network configuration changes (the PC-BSD Control Panel uses "sudo" to start it). I am also not seeing any general stability/crashes, so additional information about what you were doing at the time would be helpful to narrow down any issues.

A couple notes:
The network settings are never saved to "/etc/networks" on FreeBSD. Instead general network settings (hostname, gateway, ipv4/ipv6) are saved in "/etc/rc.conf", while DNS information is saved in "/etc/dhclient.conf" or "/etc/resolv.conf".

comment:4 in reply to: ↑ 3 Changed 8 months ago by geostar

I think that all of my issues are related to configuration of user/access permissions, that are set during initial installation of the OS. The local user is set automatically as user with administration privileges.

Afterwards, all of my system-wide configuration was done in KDE, with password of the local user, that was created during initial installation of the OS. When I did any system configuration, I was asked to use password of the user with administration privileges, not root. Initially, I tried root password. But, the system utility would not accept it, as I thought it should. Though, it did take the local user password, with the admin. privileges - strange but true :)

I'm just basing all that when compared to PC-BSD 9.1, which I currently use. Although local user is set to have administration privileges, in 9.1, it must use root password to do any su or sudo system-wide level operations, while in KDE desktop or otherwise.

But again, I'm not doing anything different in PCBSD-10, regarding Network Configuration, than in PCBSD-9.1 or Linux. I have only issues in PC-BSD 10 Release, at the moment :(
You should have noticed the looping messages:

msk1: link state changed to DOWN
428 msk1: link state changed to UP
429 msk1: watchdog timeout

It's in my "dmesg". The Ethernet is connecting and disconnecting, unable to make LAN connection, since it's not configured correctly.

Moreover, I have the same issues, related to network configuration with dynamic or static LAN/IP and DNS, during OS installation, when I try to configure my Ethernet(s), prior to installation of HD partitions, meta packages and the rest.

Replying to kenmoore:

It looks like it is working fine here.
How are you starting the utility? It needs root permissions in order to be able to save network configuration changes (the PC-BSD Control Panel uses "sudo" to start it). I am also not seeing any general stability/crashes, so additional information about what you were doing at the time would be helpful to narrow down any issues.

My bad, sorry :(
Out of frustration, I just dropped in the /etc/networks. I know better howto configure my net the old fashioned way, as I do when the GUI automagic scripts fail and inside my jail(s)

A couple notes:
The network settings are never saved to "/etc/networks" on FreeBSD. Instead general network settings (hostname, gateway, ipv4/ipv6) are saved in "/etc/rc.conf", while DNS information is saved in "/etc/dhclient.conf" or "/etc/resolv.conf".

Last edited 8 months ago by geostar (previous) (diff)

comment:5 follow-up: Changed 8 months ago by kenmoore

User and Root Passwords
Between PC-BSD 9.1 and 9.2 we switched to using "sudo" for getting administrator privileges rather than "su". This means that it now only requires the user to be in the allowed groups, and then you just need the user password. If you want to set it up to use the root password instead, just run "visudo" and modify your sudo rules appropriately.

System Administration
What KDE tools are you using to administrate the system? KDE is written for Linux, so quite often their tools do not work properly on a FreeBSD system if you are trying to modify aspects of the base OS. This is why we provide the PC-BSD Control panel with utilities for doing system administration (like changing/modifying users) on a FreeBSD system. I suppose it is possible that something you did with a KDE tool is impacting general user permissions on the system, but we would need more information before we could say that with any certainty.

Device State
It looks like your network device (Marvell Yukon 88E8057 Gigabit Ethernet) is supported by the msk driver[1], so I am not seeing anything out of the ordinary there. Is there a possibility that your network card is starting to fail on the hardware level? Do you have another card lying around that you can plug in to see if this is the case?

[1] http://www.freebsd.org/cgi/man.cgi?query=msk&sektion=4

comment:6 follow-up: Changed 8 months ago by kenmoore

  • Status changed from new to assigned

Getting back to the original PC-BSD Network Manager issues you mentioned:
I need you to verify a couple issues you mentioned but I cannot reproduce:

1) Does your /etc/[rc.conf, resolv.conf, dhclient.conf] get modified appropriately when you save your changes in the GUI?

2) Did your network get restarted properly after making the changes?

Additional:
Just to make sure, you are using the PC-BSD Network Manager[1] and not some KDE network utility?

[1] http://wiki.pcbsd.org/index.php/PC-BSD%C2%AE_Users_Handbook/10.0
See section 8.18 - Network Configuration

comment:7 in reply to: ↑ 5 Changed 8 months ago by geostar

Thank you for you prompt replies, information and suggestions. My feedback is included between the lines, below.

Replying to kenmoore:

Sorry, I did not take time to read about the sudo implementation in PC-BSD 9.2 and 10. Though, even with the sudo, I did have issues with Warden in GUI, using local user account with administrator privileges, as stated in my ticket #961

User and Root Passwords
Between PC-BSD 9.1 and 9.2 we switched to using "sudo" for getting administrator privileges rather than "su". This means that it now only requires the user to be in the allowed groups, and then you just need the user password. If you want to set it up to use the root password instead, just run "visudo" and modify your sudo rules appropriately.

Let me correct the "System Administration" in KDE. I use PC-BSD Control Panel and its utilities, in KDE desktop. I do not use any KDE utilities for system configuration or network configuration.

PC-BSD Control Panel utility such as the Network Configuration is what did not work for me. The automagic configuration, during initial system setup, wasn't able to configure my Ethernet to use dynamic LAN/IP, default GW or DNS. After completing the installation, I couldn't setup simple static LAN/IP or re-set all to Dynamic IP with Network Configuration, in PC-BSD 10 Control Panel. So, I did not have any network connectivity

System Administration
What KDE tools are you using to administrate the system? KDE is written for Linux, so quite often their tools do not work properly on a FreeBSD system if you are trying to modify aspects of the base OS. This is why we provide the PC-BSD Control panel with utilities for doing system administration (like changing/modifying users) on a FreeBSD system. I suppose it is possible that something you did with a KDE tool is impacting general user permissions on the system, but we would need more information before we could say that with any certainty.

There's absolutely nothing wrong with my Marvell Yukon 88E8057 Gigabit Ethernet(s). Btw, my EVGA-P67 motherboard has two of those on-board, dual NIC(s). They are flawless while providing LAN and WAN connectivity and communication, for dissimilar LAN segments with help of my DrayTek? (multi-WAN/LAN) router, in MSOS, *nix-like and *BSD OS'es. The computer is used as a test platform that runs three (3) different operating systems (one at the time), each with dedicated HD and it's own boot sector(s), with no issues. The only issue, related to network configuration and connectivity, came up while I was testing the PC-BSD 10-RELEASE.

Device State
It looks like your network device (Marvell Yukon 88E8057 Gigabit Ethernet) is supported by the msk driver[1], so I am not seeing anything out of the ordinary there. Is there a possibility that your network card is starting to fail on the hardware level? Do you have another card lying around that you can plug in to see if this is the case?

[1] http://www.freebsd.org/cgi/man.cgi?query=msk&sektion=4

Last edited 8 months ago by geostar (previous) (diff)

Changed 8 months ago by geostar

comment:8 in reply to: ↑ 6 Changed 8 months ago by geostar

1) Does your /etc/[rc.conf, resolv.conf, dhclient.conf] get modified appropriately when you save your changes in the GUI? - NO

2) Did your network get restarted properly after making the changes? - NO

Just to make sure, you are using the PC-BSD Network Manager[1] and not some KDE network utility?

I use PC-BSD Control Panel/Network? Configuration GUI util. There's no GUI utility, in PCBSD Control Panel, called "Network Manager." .But, I think that we're referring to the same thing :)
There's a CLI util. called "pc-netmanager", that invokes the GUI "Network Configuration" :)

I attached a new zipped file that contains the "rc.conf, resolv.conf, dhclient.conf and hosts" and their content, right after installation of a fresh PC-BSD 10-RELASE OS (ver. in my original dmesg attachement) with KDE desktop option - as a default in the install. No configuration or edits (of any kind) were made, after the installation. Although, "ifconfig" shows dynamic LAN/IP assigned to the msk1 interface, there's no network connectivity to the GW/LAN IP. The network interface (msk1) IP is on the same LAN segment as the router that provided the IP. Somehow the msk1 obtained the dynamic IP from the router, but rest of the network configuration failed.

As additional note: I also tested PCBSD10-STABLE-p7-01-06-2014-x64*.iso, in the same system. That distribution had no issue with automagic configuration of networking with dynamic LAN/IP, during initial installation. But, after the installation, I did experience same issues, as in PCBSD10-RELEASE, while trying to set-up static LAN/IP through PC-BSD Control Panel with the Network Configuration util. But, at least the LAN/WAN networking in "STABLE" distribution was functioning OK, when set automagically with dynamic LAN/IP, during initial installation.

  • Update related to the "STABLE" distribution of PCBSD10-STABLE-*, as above:

During first installation of the "STABLE" distribution, I had only one network cable attached to my dual Ethernets, the "msk1", and my router. I did not want to confuse installation process of the OS with two live LAN connections. Since the install did a good job of auto configuring networking with single Ethernet LAN connection to the router, I re-installed the "STABLE" version with two live network connections to my LAN/router. After that, I had no issues with setting of static LAN IP(s) on either of the network interface, msk0 or msk1, each on different LAN segment/subnet - ea. msk0-192.168.2.10 and msk1-192.168.1.10 (both routed through the same LAN/GW/IP or each through a different LAN/GW/IP(s), with automagic help of my mutli-port WAN/LAN router)

But, the same process and tests did not bring positive results in PCBSD10-RELEASE. So, the auto configuration of networking during initial installation and my attempt to configure networking after the installation, with single or dual LAN connection failed, in PCBSD10-RELEASE, while using PCBSD Control Panel/GUI-Network Configuration.

Replying to kenmoore:

Getting back to the original PC-BSD Network Manager issues you mentioned:
I need you to verify a couple issues you mentioned but I cannot reproduce:

1) Does your /etc/[rc.conf, resolv.conf, dhclient.conf] get modified appropriately when you save your changes in the GUI?

2) Did your network get restarted properly after making the changes?

Additional:
Just to make sure, you are using the PC-BSD Network Manager[1] and not some KDE network utility?

[1] http://wiki.pcbsd.org/index.php/PC-BSD%C2%AE_Users_Handbook/10.0
See section 8.18 - Network Configuration

Last edited 8 months ago by geostar (previous) (diff)

comment:9 follow-up: Changed 8 months ago by kenmoore

  • Status changed from assigned to new

OK, I have been doing a bunch of checks on this, but I am still unable to reproduce your bugs.
Try this (one step at a time) and report what happens please:
1) Open a console and run (as user) "sudo cp /etc/rc.conf /etc/rc.conf.old. Give your user password when prompted. This just makes a copy of your current configuration for comparison later.
2)Run "sudo pc-netmanager" (also as user). This will start up the network manager the exact same way the PC-BSD Control Panel does, but also let you see some debugging information in the console.
3) Make a few changes in the main network config UI -> Network Configuration tab, (such as putting in a custom gateway, change hostname, or enable ipv6 support with custom gateway) then click the "Save" button at the bottom.
4) After saving your changes, you should see a little window pop-up saying that it is restarting the network (the text changes depending on which step of the restart operation it is on).
5) Close the network manager, and see if there is any strange debugging output in the console.
6) Run "diff /etc/rc.conf /etc/rc.conf.old" to see any changes to your configuration (it should match the changes you saved within the GUI).
7) Re-run steps 3->6 but this time make/save your changes within the device configuration sub-GUI fro your particular device (assign static IP or IPv6 address in this case, since that will make changes to rc.conf).

I am not looking for whether your configuration settings are correct (in that you have an active internet connection afterwards), but simply whether the utility is making the appropriate changes to your configuration file at the moment.

comment:10 Changed 8 months ago by kenmoore

  • Status changed from new to assigned

Oops, accidentally reset the status of this ticket to new. Re-assigning it back to me.

Changed 8 months ago by geostar

comment:11 in reply to: ↑ 9 Changed 8 months ago by geostar

This is my third and last attempt in trying to debug or resolve issues related to the Ethernet and network configuration in my system, while testing the PCBSD10-RELEASE-p5*.iso. Despite your help and my best efforts, I cannot do anything to fix the network configuration and lack of network connectivity.

I'm not a *BSD hacker, script coder or CL programmer, but I do use common sense and practical approach when certain issues arise in computer systems-hardware or software. I don't know what was changed or updated (other than release dates), in PCBSD10-STABLE vs. PCBS10-RELEASE, that made "STABLE" work and the "RELEASE" not, regarding network configuration. I can only guess that there maybe some IRQ/DMA conflict(s), due to changes in hardware drivers, that prevent my Ethernet(s) to function correctly in PCBSD10-RELEASE-p5. So, here is my last feedback with attachments that indicate what I did and what it is - "as is". In net-conf.zp attachment.

I did not see any unusual or error messages, during configuration, in pc-netmanager console's output, while using the utility, as follow:

1) After two tries, I was finally able to enter/change Custom DNS and Gateway IP(s) with Network Manager and the content was updated in:
/etc/resolv.conf - updated with the new DNS IP(s)
/etc/rc.conf - update with new "defaultrouter" IP
(msk0 and msk1 had "DHCP" settings in etc/rc.conf (default from initial install - each had assigned dynammic IP, verified with "ifconfig")

The pc-netmanager console provided the following output, after updates of GW/IP and DNS/IP: - (Locale: "en")

When I was done entering/changing (valid) DNS/IP(s) or GW/IP(s), in Network Manager window, I was also testing all with ping to my router and FQDNS hosts. In each case, even when I was able to ping my router, I was unable to resolve the hosts (no DNS), despite the fact that there were valid DNS IP entries in /etc/resolv.conf, and "defaultrouter" - in /etc/rc.conf

While doing the above, I also noticed that the msk1 was loosing connection.

2) Next, I tried several times, but was unable to update/change my msk0 or msk1 interface's IP number(s), because the GUI "msk configuration" input window would freeze and hang, after I pressed "OK" or "Apply" button. I waited a minute or so, and then I did Ctrl-C, in pc-netmanager console, to end the session. There wasn't any output message in pc-netmanager's console and nothing got updated in /etc/rc.conf.

Later, I copied /etc/rc.conf.old to /etc/rc.conf and rebooted the system. I tried again with pc-netmanager (msk1 and msk0) configuration with static LAN IP(s). This time it worked - /etc/rc.conf got updated with static IP(s). But again, no network connectivity!

This is when I decided to give-up :)


Replying to kenmoore:

OK, I have been doing a bunch of checks on this, but I am still unable to reproduce your bugs.
Try this (one step at a time) and report what happens please:
1) Open a console and run (as user) "sudo cp /etc/rc.conf /etc/rc.conf.old. Give your user password when prompted. This just makes a copy of your current configuration for comparison later.
2)Run "sudo pc-netmanager" (also as user). This will start up the network manager the exact same way the PC-BSD Control Panel does, but also let you see some debugging information in the console.
3) Make a few changes in the main network config UI -> Network Configuration tab, (such as putting in a custom gateway, change hostname, or enable ipv6 support with custom gateway) then click the "Save" button at the bottom.
4) After saving your changes, you should see a little window pop-up saying that it is restarting the network (the text changes depending on which step of the restart operation it is on).
5) Close the network manager, and see if there is any strange debugging output in the console.
6) Run "diff /etc/rc.conf /etc/rc.conf.old" to see any changes to your configuration (it should match the changes you saved within the GUI).
7) Re-run steps 3->6 but this time make/save your changes within the device configuration sub-GUI fro your particular device (assign static IP or IPv6 address in this case, since that will make changes to rc.conf).

I am not looking for whether your configuration settings are correct (in that you have an active internet connection afterwards), but simply whether the utility is making the appropriate changes to your configuration file at the moment.

Last edited 8 months ago by geostar (previous) (diff)

comment:12 Changed 8 months ago by kenmoore

  • Resolution set to worksforme
  • Status changed from assigned to closed

This was actually a lot more helpful than you were probably expecting... :-)

I think this narrows down the issue(s) specifically to a hardware/driver issue. This seems to make the most sense because of the following things you mentioned:
1) The GUI only hangs when trying to load the msk device information or change the msk device configuration (not the config file, but restarting/accessing the device with the new configuration).
2) Even with correct configuration settings, you msk device still does not function properly (dropping connection).
3) This seems to correspond to the "watchdog timeout" errors that you noticed in your initial report.
4) This seems to explain why it works perfectly fine on my systems but not on yours (since I do not have an msk network device).

I did find a bit of information about the "msk" family of devices just from doing some google searches on it, and apparently there are many variants of the same supported msk device chipsets that can cause different levels of support with the FreeBSD msk driver. So while your particular device is listed as supported, it might actually be one of those variants and is having issues because of it.

The main "solutions" that I found were this:
1) Get a different network card. This was the most common answer that I found, with a lot of people saying they just bought a cheap Intel (em) or Realtek (re) card and it worked fine with that new card.
2) Check your network cable. A few people said that replacing the network cable connected to their card fixed the issue (but I don't think this is that likely for you since you could ping the router just fine).
3) Contact the FreeBSD driver developers mailing list[1] and work with one of them to find the issue and get it fixed. This would be the most helpful to the community, but I understand if you don't have the time.

In the meantime, I am going to close this ticket as "works for me" since it specifically deals with the GUI utility.

Thank you for all your time and energy in trying to work out what was going on with your system.

[1] http://lists.freebsd.org/mailman/listinfo/freebsd-drivers

Note: See TracTickets for help on using tickets.