Menu
▾
▴
webadmin-list
|
From: ѽ҉ᶬḳ℠ <vt...@gm...> - 2018-06-08 20:37:07
|
Ubuntu Linux 18.04 Webmin 1.881 Authentic Theme 19.19 Having the lo iface assigned a non-public ip (172.23.120.98) and trying to bind Webmin (/webmin/edit_bind.cgi?xnavigation=1) to that ip produces -> Failed to change address : The IP address 172.23.120.98 is not active on this system, and so cannot be used setting 'bind=172.23.122.98' in "/etc/webmin/miniserv.conf" and a restart of Webmin gets it working though. |
|
From: Jamie C. <jca...@we...> - 2018-06-09 18:00:19
|
On 08/Jun/2018 13:36 ѽ҉ᶬḳ℠ <vt...@gm...> wrote .. > Ubuntu Linux 18.04 > Webmin 1.881 > Authentic Theme 19.19 > > Having the lo iface assigned a non-public ip (172.23.120.98) and trying > to bind Webmin (/webmin/edit_bind.cgi?xnavigation=1) to that ip produces > -> Failed to change address : The IP address 172.23.120.98 is not active > on this system, and so cannot be used > > setting 'bind=172.23.122.98' in "/etc/webmin/miniserv.conf" and a > restart of Webmin gets it working though. So you're setting the IP of the "lo" (loopback) interface to something other than 127.0.0.1 ? I don't think that's going to work .. |
|
From: ѽ҉ᶬḳ℠ <vt...@gm...> - 2018-06-09 19:09:42
|
>> Having the lo iface assigned a non-public ip (172.23.120.98) and trying >> to bind Webmin (/webmin/edit_bind.cgi?xnavigation=1) to that ip produces >> -> Failed to change address : The IP address 172.23.120.98 is not active >> on this system, and so cannot be used >> >> setting 'bind=172.23.122.98' in "/etc/webmin/miniserv.conf" and a >> restart of Webmin gets it working though. > So you're setting the IP of the "lo" (loopback) interface to something > other than 127.0.0.1 ? I don't think that's going to work .. There is no issue for the lo iface to be assigned various other ip addresses on top of 127.0.0.1 and neither for services/sockets to bind to any of those additional ips and be available to other system components. At the moment I am running ssh, netdata, exim, dnsmasq and webmin each on a separate lo iface ip. Like mentioned earlier Webmin is currently bind and running on the lo iface with ip 172.23.122.98, which though was not possible to set via the Webmin gui but via 'bind=172.23.122.98' in "/etc/webmin/miniserv.conf". |
|
From: Jamie C. <jca...@we...> - 2018-06-10 17:37:38
|
On 09/Jun/2018 12:09 ѽ҉ᶬḳ℠ <vt...@gm...> wrote .. > > >> Having the lo iface assigned a non-public ip (172.23.120.98) and trying > >> to bind Webmin (/webmin/edit_bind.cgi?xnavigation=1) to that ip produces > >> -> Failed to change address : The IP address 172.23.120.98 is not active > >> on this system, and so cannot be used > >> > >> setting 'bind=172.23.122.98' in "/etc/webmin/miniserv.conf" and a > >> restart of Webmin gets it working though. > > So you're setting the IP of the "lo" (loopback) interface to something > > other than 127.0.0.1 ? I don't think that's going to work .. > > There is no issue for the lo iface to be assigned various other ip > addresses on top of 127.0.0.1 and neither for services/sockets to bind > to any of those additional ips and be available to other system > components. At the moment I am running ssh, netdata, exim, dnsmasq and > webmin each on a separate lo iface ip. > Like mentioned earlier Webmin is currently bind and running on the lo > iface with ip 172.23.122.98, which though was not possible to set via > the Webmin gui but via 'bind=172.23.122.98' in "/etc/webmin/miniserv.conf". I'm surprising that having non-local IPs on the "lo" interface works .. but even so, Webmin should allow this. If you go to Hardware -> Network Configuration -> Network Interfaces, does that IP show up? |
|
From: ѽ҉ᶬḳ℠ <vt...@gm...> - 2018-06-10 17:51:41
|
> I'm surprising that having non-local IPs on the "lo" interface works .. but > even so, Webmin should allow this. > > If you go to Hardware -> Network Configuration -> Network Interfaces, does > that IP show up? The additional lo ips do not show on Active Now, only the last additional ip (172.23.124.98) is showing at Activated at Boot. The system is running iproute2 and ifupdown2, ifupdown is removed. lo config: iface lo inet loopback address 172.23.120.98/32 address 172.23.121.98/32 address 172.23.122.98/32 address 172.23.123.98/32 address 172.23.124.98/32 Output from -> ip a ls lo: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet 172.23.120.98/32 scope global lo valid_lft forever preferred_lft forever inet 172.23.121.98/32 scope global lo valid_lft forever preferred_lft forever inet 172.23.122.98/32 scope global lo valid_lft forever preferred_lft forever inet 172.23.123.98/32 scope global lo valid_lft forever preferred_lft forever inet 172.23.124.98/32 scope global lo valid_lft forever preferred_lft forever |
|
From: Jamie C. <jca...@we...> - 2018-06-10 18:08:41
|
On 10/Jun/2018 10:51 ѽ҉ᶬḳ℠ <vt...@gm...> wrote .. > > > I'm surprising that having non-local IPs on the "lo" interface works .. but > > even so, Webmin should allow this. > > > > If you go to Hardware -> Network Configuration -> Network Interfaces, does > > that IP show up? > > The additional lo ips do not show on Active Now, only the last > additional ip (172.23.124.98) is showing at Activated at Boot. > > The system is running iproute2 and ifupdown2, ifupdown is removed. lo > config: > > iface lo inet loopback > address 172.23.120.98/32 > address 172.23.121.98/32 > address 172.23.122.98/32 > address 172.23.123.98/32 > address 172.23.124.98/32 > > Output from -> ip a ls lo: > > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN > group default qlen 1000 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet 172.23.120.98/32 scope global lo > valid_lft forever preferred_lft forever > inet 172.23.121.98/32 scope global lo > valid_lft forever preferred_lft forever > inet 172.23.122.98/32 scope global lo > valid_lft forever preferred_lft forever > inet 172.23.123.98/32 scope global lo > valid_lft forever preferred_lft forever > inet 172.23.124.98/32 scope global lo > valid_lft forever preferred_lft forever What output do you get if you run "ip addr" or "ifconfig -a" |
|
From: ѽ҉ᶬḳ℠ <vt...@gm...> - 2018-06-10 18:23:30
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#f5f5f5" bgcolor="#272a36">
<br>
<blockquote type="cite" cite="mid:152...@we...">
<pre class="moz-quote-pre" wrap="">
What output do you get if you run "ip addr" or "ifconfig -a"</pre>
</blockquote>
<br>
"ip addr" being the long version of shorthand "ip a" and thus the
output for lo is the same as previously stated.<br>
<br>
"ifconfig lo" output though is not showing the additional ips but
only:<br>
<br>
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536<br>
inet 127.0.0.1 netmask 255.0.0.0<br>
loop txqueuelen 1000 (Local Loopback)<br>
<br>
</body>
</html>
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X