Bug 13053 - draknfs can only export nfs on one eth, and it may be the wrong one
Summary: draknfs can only export nfs on one eth, and it may be the wrong one
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-19 22:51 CET by Thomas Spuhler
Modified: 2015-10-27 06:57 CET (History)
1 user (show)

See Also:
Source RPM: draknfs
CVE:
Status comment:


Attachments

Description Thomas Spuhler 2014-03-19 22:51:47 CET
Description of problem:
I tried to configure an NFS export, but it gave my only on choice in the Access filed,  (actually 3) *, *.mydomain and 10.0.0.2. But I need the local network 192.168.0.0/24

Version-Release number of selected component (if applicable):
Mageia 4 (maybe 3 too) and cauldron.

Unfortunately, I couldn't find anything where the config file is to edit it manually (IRC helped, it's /etc/exports




Reproducible: 

Steps to Reproduce:
Comment 1 Morgan Leijström 2014-06-14 00:41:09 CEST
Can you reproduce now on updated mageia?
I could select 192.168.0.0/24 in the dropdown. (mga4)

# draknfs --version
Drakxtools version 16.26.8

CC: (none) => fri

Comment 2 Thomas Spuhler 2014-06-15 00:22:05 CEST
No there is no change. The dropdown (Access) only shows:
*
*/btspuhler.com
10.0.0.0/8
10.0.0.0/24

but I need on the other Ethernet card
192.168.0.0/24 and this doesn't show
(maybe because I already had added it manually?)
Comment 3 Morgan Leijström 2014-06-15 00:53:44 CEST
I think it should offer options for all interfaces.

i have # cat /etc/exports
/mnt/Arkivet 192.168.0.0/24(no_all_squash,async,secure,no_subtree_check,rw)

And dropdown shows 192. choices.
It is easy to edit /etc/exports, but the darktools should work anyway...
- they are beatiful when they do :)
Comment 4 Thomas Spuhler 2014-06-15 01:13:31 CEST
I have:
$ cat /etc/exports
# generated by drakhosts.pl
/home/brigitte 192.168.0.0/24(no_all_squash,async,secure,no_subtree_check,rw) 
/home/thomas 192.168.0.0/24(no_all_squash,async,secure,no_subtree_check,rw) 

but dropdown doesn't shows these as choices.
One could argue, that few have tow interfaces and those can do the entries manually.
Comment 5 Samuel Verschelde 2015-09-21 13:20:22 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 6 Marja Van Waes 2015-10-27 06:57:36 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.