Setting Static IP creates tons of problems

Bug #156087 reported by Mito Tranin
4
Affects Status Importance Assigned to Milestone
Mythbuntu
Fix Released
Critical
Unassigned

Bug Description

When you setup the machine with a static IP after the VNC server and MySQL server (for remote connections) are setup, both the VNC server and MySQL service no longer accept connections.

To reproduce: Install system and setup with VNC service and remote-frontend ability, and restart. After restart, exit the frontend, open the network config and setup for a static IP. Restart again or simply restart the networking to allow proper network connections. From now on, the system no longer accepts VNC connections (because it was listening to the old IP... one thought here: would a change in IP caused via DHCP result in the same problem?) and remote opperations such as MythWeb and a remote front-end no longer work either.

Revision history for this message
Mito Tranin (mito-im) wrote :

Additional comment I forgot to include:

When you disable the MySQL service in an attempt to fix the solution, the mysql-server package is set to be removed. Oddly however, after this is completed, there is still a mysql-server package installed, and the backend is still functional, however the option in the MCC is now disabled (as in greyed out). At this point it has sofar been impossible to re-enable the MySQL option in the MCC, and it is unsure as to why the mysql-server package is listed to be removed, yet it is still there after the removal...

Revision history for this message
Mito Tranin (mito-im) wrote :

As requested, the comment above has been reported as a separate bug. bug 156089 : mysql-server removed when it shouldn't

Revision history for this message
David Morris (dave-greenacre) wrote :

I guess we need a small script to change all these files after the ip address has been changed. Perhaps changing the ip address can be added to the m-c-c?

Changed in mythbuntu:
milestone: none → 8.04-alpha1
Revision history for this message
Mito Tranin (mito-im) wrote :

I think having the IP address setting in the MCC would be a great addition. As it is right now, you have to exit MythTV altogether to do it, and that's one of the very few, if not the only thing that you have to leave the MCC to do for a basic setup.

Revision history for this message
David Morris (dave-greenacre) wrote :

laga, can we add changing IP address to the m-c-c with some code/scripts to update the settings used by the various programs which bind to the IP

Changed in mythbuntu:
assignee: nobody → laga
importance: Undecided → Medium
Revision history for this message
laga (laga) wrote :

Giving this back since it's a bit bigger than what I want to do right now.

Changed in mythbuntu:
assignee: laga → nobody
importance: Medium → High
Revision history for this message
bobo (uszko) wrote :

I confirm this behaviour for the Beta version: After installing the Beta fresh on a new system (only as master backend) I configured all in the MCC (Mysql and vnc). Then I changed the IP adress to a static one. Now I cannot access the system via vnc when the logon screen is there. As soon as I am logged in I can also access the system via vnc. BTW the change could only be done in the network file, since the management interface does not allow me to unlock it.

Revision history for this message
Mario Limonciello (superm1) wrote : Re: [Bug 156087] Re: Setting Static IP creates tons of problems

bobo,

Are these the only issues you ran into with a static IP? VNC isn't
activated until you are logged in for 8.04 (unfortunate side effect of
switching to x11vnc since RealVNC is broke).

On Tue, Mar 25, 2008 at 4:57 PM, bobo <email address hidden> wrote:

> I confirm this behaviour for the Beta version: After installing the Beta
> fresh on a new system (only as master backend) I configured all in the
> MCC (Mysql and vnc). Then I changed the IP adress to a static one. Now I
> cannot access the system via vnc when the logon screen is there. As soon
> as I am logged in I can also access the system via vnc. BTW the change
> could only be done in the network file, since the management interface
> does not allow me to unlock it.
>
> --
> Setting Static IP creates tons of problems
> https://bugs.launchpad.net/bugs/156087
> You received this bug notification because you are a member of
> Mythbuntu, which is subscribed to Mythbuntu.
>

--
Mario Limonciello
<email address hidden>

Revision history for this message
pdragon (pdragon) wrote :

Working on a new Mythbuntu system and did a fresh install from the Beta ISO. If I set it to static IP, it does not have an IP address listed in ifconfig when first booted up. I have to change to DHCP then back to static again to get the IP I want. Have to do this every time I reboot on the new system.
It's working fine on the old system I have that was upgraded from 7.10 to 8.04beta, but I'm having other sound and performance issues I was hoping the newer system would fix.

Revision history for this message
pdragon (pdragon) wrote :

Reinstalled with the Release Candidate and the major problem I've had is cleared up, but it's not working perfectly yet.

When it's first installed, "Roaming Mode" is checked in the Network Manager. I want a static IP, so I uncheck it and set the Static IP option. The settings all stay there, but the network connection does not work until I force a reload (/etc/init.d/networking restart) or restart the computer. Everything is working fine after that (settings are kept and work after rebooting). Just doesn't work right when it's first set.

Thomas Mashos (tgm4883)
Changed in mythbuntu:
importance: High → Critical
status: New → Confirmed
Revision history for this message
Nick Fox (nickj-fox) wrote :

This bug was actually caused by Network-Manager and has since been resolved.

On Thu, Aug 7, 2008 at 12:01 PM, Thomas Mashos <email address hidden>wrote:

> ** Changed in: mythbuntu
> Importance: High => Critical
> Status: New => Confirmed
>
> --
> Setting Static IP creates tons of problems
> https://bugs.launchpad.net/bugs/156087
> You received this bug notification because you are a member of
> Mythbuntu, which is subscribed to Mythbuntu.
>

Thomas Mashos (tgm4883)
Changed in mythbuntu:
status: Confirmed → Fix Released
Revision history for this message
Nick Fox (nickj-fox) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.