Warning about dynamic ip addresses - Ubuntu

This is a discussion on Warning about dynamic ip addresses - Ubuntu ; After I got all the 253 updates installed, there were a couple of problems so I thought I'd share them. 1) After a reboot, NONE of the following entries in my grub boot would work title Ubuntu gutsy (development branch), ...

+ Reply to Thread
Results 1 to 11 of 11

Thread: Warning about dynamic ip addresses

  1. Warning about dynamic ip addresses

    After I got all the 253 updates installed, there were a couple of problems
    so I thought I'd share them.

    1) After a reboot, NONE of the following entries in my grub boot would
    work

    title Ubuntu gutsy (development branch), kernel 2.6.22-13-server
    root (hd1,1)
    kernel /boot/vmlinuz-2.6.22-13-server root=UUID=c9f2e32f-304d-48bb-9c1a
    -f44b49d0bbac ro quiet splash
    initrd /boot/initrd.img-2.6.22-13-server
    quiet

    title Ubuntu gutsy (development branch), kernel 2.6.22-13-server (reco
    very mode)
    root (hd1,1)
    kernel /boot/vmlinuz-2.6.22-13-server root=UUID=c9f2e32f-304d-48bb-9c1a
    -f44b49d0bbac ro single
    initrd /boot/initrd.img-2.6.22-13-server

    The first one gave me an X config error and would not start up.
    The second simply booted me into a command line. There's probably a way
    to get X to start but I didn't want to spend the time. Besides, the
    third option worked. I haven't tested my openSuse boot yet.

    2) My IP address changed from xxx.xxx.x.100 to xxx.xxx.x.102 which meant having
    to go into my router config and changing all the IP addresses which pointed
    to my GG server.

    A`
    A
    A
    A
    A
    A
    A
    A
    A
    A


    --
    PSK - RLU 452647 http://improve-usenet.org
    Killing GG on Ubuntu, openSUSE, Vista and XP with slrn and Xnews
    ~Nick: People are pigs.
    ~Grissom: Don't insult the pigs, Nick. They're actually very clean.

  2. Re: Warning about dynamic ip addresses

    On 2007-10-06, Pseudo Silk Kimono wrote:
    > After I got all the 253 updates installed, there were a couple of problems
    > so I thought I'd share them.
    >
    > 1) After a reboot, NONE of the following entries in my grub boot would
    > work
    >
    > title Ubuntu gutsy (development branch), kernel 2.6.22-13-server
    > root (hd1,1)
    > kernel /boot/vmlinuz-2.6.22-13-server root=UUID=c9f2e32f-304d-48bb-9c1a
    > -f44b49d0bbac ro quiet splash
    > initrd /boot/initrd.img-2.6.22-13-server
    > quiet
    >
    > title Ubuntu gutsy (development branch), kernel 2.6.22-13-server (reco
    > very mode)
    > root (hd1,1)
    > kernel /boot/vmlinuz-2.6.22-13-server root=UUID=c9f2e32f-304d-48bb-9c1a
    > -f44b49d0bbac ro single
    > initrd /boot/initrd.img-2.6.22-13-server
    >
    > The first one gave me an X config error and would not start up.
    > The second simply booted me into a command line. There's probably a way
    > to get X to start but I didn't want to spend the time. Besides, the
    > third option worked. I haven't tested my openSuse boot yet.
    >
    > 2) My IP address changed from xxx.xxx.x.100 to xxx.xxx.x.102 which meant having
    > to go into my router config and changing all the IP addresses which pointed
    > to my GG server.
    >

    Just a bit more information about these this issue with X:

    title Ubuntu gutsy (development branch), kernel 2.6.22-13-server
    root (hd1,1)
    kernel /boot/vmlinuz-2.6.22-13-server root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro quiet splash
    initrd /boot/initrd.img-2.6.22-13-server
    quiet

    Fails with the following:

    Failed to start the X server (your graphical interface). It is likely that it is not set up correctly. Would you like to view the X server output to diagnose the problem

    I said but it made no sense to me except for a piece that was complaining about the nvidia drivers. This would make me suspect that the kernel update blew away my restricted drivers.

    title Ubuntu gutsy (development branch), kernel 2.6.22-13-server (recovery mode)
    root (hd1,1)
    kernel /boot/vmlinuz-2.6.22-13-server root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro single
    initrd /boot/initrd.img-2.6.22-13-server

    Fine... but no GDM... cli only.

    title Ubuntu gutsy (development branch), kernel 2.6.22-13-rt
    root (hd1,1)
    kernel /boot/vmlinuz-2.6.22-13-rt root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro quiet splash
    initrd /boot/initrd.img-2.6.22-13-rt
    quiet

    Failed..same message as before

    title Ubuntu gutsy (development branch), kernel 2.6.22-13-rt (recovery mode)
    root (hd1,1)
    kernel /boot/vmlinuz-2.6.22-13-rt root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro single
    initrd /boot/initrd.img-2.6.22-13-rt

    Didn't bother with this, I would assume it would boot me into a cli as well.

    Which leaves me with:

    title Ubuntu gutsy (development branch), kernel 2.6.22-12-386
    root (hd1,1)
    kernel /boot/vmlinuz-2.6.22-12-386 root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro quiet splash
    initrd /boot/initrd.img-2.6.22-12-386
    quiet

    And that's fine. But I would like to be able to get the first one working since it appears to be a more recent kernel and is the "server" version.


    --
    PSK - RLU 452647 http://improve-usenet.org
    Killing GG on Ubuntu, openSUSE, Vista and XP with slrn and Xnews
    ~Nick: People are pigs.
    ~Grissom: Don't insult the pigs, Nick. They're actually very clean.

  3. Re: Warning about dynamic ip addresses

    Pseudo Silk Kimono wrote:
    > On 2007-10-06, Pseudo Silk Kimono wrote:
    >> After I got all the 253 updates installed, there were a couple of problems
    >> so I thought I'd share them.
    >>
    >> 1) After a reboot, NONE of the following entries in my grub boot would
    >> work
    >>
    >> title Ubuntu gutsy (development branch), kernel 2.6.22-13-server
    >> root (hd1,1)
    >> kernel /boot/vmlinuz-2.6.22-13-server root=UUID=c9f2e32f-304d-48bb-9c1a
    >> -f44b49d0bbac ro quiet splash
    >> initrd /boot/initrd.img-2.6.22-13-server
    >> quiet
    >>
    >> title Ubuntu gutsy (development branch), kernel 2.6.22-13-server (reco
    >> very mode)
    >> root (hd1,1)
    >> kernel /boot/vmlinuz-2.6.22-13-server root=UUID=c9f2e32f-304d-48bb-9c1a
    >> -f44b49d0bbac ro single
    >> initrd /boot/initrd.img-2.6.22-13-server
    >>
    >> The first one gave me an X config error and would not start up.
    >> The second simply booted me into a command line. There's probably a way
    >> to get X to start but I didn't want to spend the time. Besides, the
    >> third option worked. I haven't tested my openSuse boot yet.
    >>
    >> 2) My IP address changed from xxx.xxx.x.100 to xxx.xxx.x.102 which meant having
    >> to go into my router config and changing all the IP addresses which pointed
    >> to my GG server.
    >>

    > Just a bit more information about these this issue with X:
    >
    > title Ubuntu gutsy (development branch), kernel 2.6.22-13-server
    > root (hd1,1)
    > kernel /boot/vmlinuz-2.6.22-13-server root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro quiet splash
    > initrd /boot/initrd.img-2.6.22-13-server
    > quiet
    >
    > Fails with the following:
    >
    > Failed to start the X server (your graphical interface). It is likely that it is not set up correctly. Would you like to view the X server output to diagnose the problem
    >
    > I said but it made no sense to me except for a piece that was complaining about the nvidia drivers. This would make me suspect that the kernel update blew away my restricted drivers.
    >
    > title Ubuntu gutsy (development branch), kernel 2.6.22-13-server (recovery mode)
    > root (hd1,1)
    > kernel /boot/vmlinuz-2.6.22-13-server root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro single
    > initrd /boot/initrd.img-2.6.22-13-server
    >
    > Fine... but no GDM... cli only.
    >
    > title Ubuntu gutsy (development branch), kernel 2.6.22-13-rt
    > root (hd1,1)
    > kernel /boot/vmlinuz-2.6.22-13-rt root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro quiet splash
    > initrd /boot/initrd.img-2.6.22-13-rt
    > quiet
    >
    > Failed..same message as before
    >
    > title Ubuntu gutsy (development branch), kernel 2.6.22-13-rt (recovery mode)
    > root (hd1,1)
    > kernel /boot/vmlinuz-2.6.22-13-rt root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro single
    > initrd /boot/initrd.img-2.6.22-13-rt
    >
    > Didn't bother with this, I would assume it would boot me into a cli as well.
    >
    > Which leaves me with:
    >
    > title Ubuntu gutsy (development branch), kernel 2.6.22-12-386
    > root (hd1,1)
    > kernel /boot/vmlinuz-2.6.22-12-386 root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro quiet splash
    > initrd /boot/initrd.img-2.6.22-12-386
    > quiet
    >
    > And that's fine. But I would like to be able to get the first one working since it appears to be a more recent kernel and is the "server" version.
    >
    >


    Hello.

    You're a little mistaken, the second entry in grub works fine, it is
    supposed to take you to a command line as root. It's intended to be the
    last hope if you blew up your system.

    But that thing with the X can be surely changed very quick. Let it boot,
    and change to a terminal (Strg+Alt+F1), login and rebuild the xorg.conf
    with the command
    sudo dpkg-reconfigure xserver-xorg
    When you get asked about the drivers for your card, select vesa, this
    will sure work, you can also try nvidia or nv, maybe it works.

    Rob

  4. Re: Warning about dynamic ip addresses

    On 2007-10-06, Robert Zenz wrote:
    > Pseudo Silk Kimono wrote:
    >> On 2007-10-06, Pseudo Silk Kimono wrote:
    >>> After I got all the 253 updates installed, there were a couple of problems
    >>> so I thought I'd share them.
    >>>
    >>> 1) After a reboot, NONE of the following entries in my grub boot would
    >>> work
    >>>
    >>> title Ubuntu gutsy (development branch), kernel 2.6.22-13-server
    >>> root (hd1,1)
    >>> kernel /boot/vmlinuz-2.6.22-13-server root=UUID=c9f2e32f-304d-48bb-9c1a
    >>> -f44b49d0bbac ro quiet splash
    >>> initrd /boot/initrd.img-2.6.22-13-server
    >>> quiet
    >>>
    >>> title Ubuntu gutsy (development branch), kernel 2.6.22-13-server (reco
    >>> very mode)
    >>> root (hd1,1)
    >>> kernel /boot/vmlinuz-2.6.22-13-server root=UUID=c9f2e32f-304d-48bb-9c1a
    >>> -f44b49d0bbac ro single
    >>> initrd /boot/initrd.img-2.6.22-13-server
    >>>
    >>> The first one gave me an X config error and would not start up.
    >>> The second simply booted me into a command line. There's probably a way
    >>> to get X to start but I didn't want to spend the time. Besides, the
    >>> third option worked. I haven't tested my openSuse boot yet.
    >>>
    >>> 2) My IP address changed from xxx.xxx.x.100 to xxx.xxx.x.102 which meant having
    >>> to go into my router config and changing all the IP addresses which pointed
    >>> to my GG server.
    >>>

    >> Just a bit more information about these this issue with X:
    >>
    >> title Ubuntu gutsy (development branch), kernel 2.6.22-13-server
    >> root (hd1,1)
    >> kernel /boot/vmlinuz-2.6.22-13-server root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro quiet splash
    >> initrd /boot/initrd.img-2.6.22-13-server
    >> quiet
    >>
    >> Fails with the following:
    >>
    >> Failed to start the X server (your graphical interface). It is likely that it is not set up correctly. Would you like to view the X server output to diagnose the problem
    >>
    >> I said but it made no sense to me except for a piece that was complaining about the nvidia drivers. This would make me suspect that the kernel update blew away my restricted drivers.
    >>
    >> title Ubuntu gutsy (development branch), kernel 2.6.22-13-server (recovery mode)
    >> root (hd1,1)
    >> kernel /boot/vmlinuz-2.6.22-13-server root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro single
    >> initrd /boot/initrd.img-2.6.22-13-server
    >>
    >> Fine... but no GDM... cli only.
    >>
    >> title Ubuntu gutsy (development branch), kernel 2.6.22-13-rt
    >> root (hd1,1)
    >> kernel /boot/vmlinuz-2.6.22-13-rt root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro quiet splash
    >> initrd /boot/initrd.img-2.6.22-13-rt
    >> quiet
    >>
    >> Failed..same message as before
    >>
    >> title Ubuntu gutsy (development branch), kernel 2.6.22-13-rt (recovery mode)
    >> root (hd1,1)
    >> kernel /boot/vmlinuz-2.6.22-13-rt root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro single
    >> initrd /boot/initrd.img-2.6.22-13-rt
    >>
    >> Didn't bother with this, I would assume it would boot me into a cli as well.
    >>
    >> Which leaves me with:
    >>
    >> title Ubuntu gutsy (development branch), kernel 2.6.22-12-386
    >> root (hd1,1)
    >> kernel /boot/vmlinuz-2.6.22-12-386 root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro quiet splash
    >> initrd /boot/initrd.img-2.6.22-12-386
    >> quiet
    >>
    >> And that's fine. But I would like to be able to get the first one working since it appears to be a more recent kernel and is the "server" version.
    >>
    >>

    >
    > Hello.
    >
    > You're a little mistaken, the second entry in grub works fine, it is
    > supposed to take you to a command line as root. It's intended to be the
    > last hope if you blew up your system.


    Yeah, I know. I was just pissed off.

    >
    > But that thing with the X can be surely changed very quick. Let it boot,
    > and change to a terminal (Strg+Alt+F1), login and rebuild the xorg.conf
    > with the command
    > sudo dpkg-reconfigure xserver-xorg
    > When you get asked about the drivers for your card, select vesa, this
    > will sure work, you can also try nvidia or nv, maybe it works.
    >
    > Rob


    Thanks, and just before I read your message I found the exact same thing
    on one of the Ubuntu forums. Going to try it now.


    --
    PSK - RLU 452647 http://improve-usenet.org
    Killing GG on Ubuntu, openSUSE, Vista and XP with slrn and Xnews
    ~Nick: People are pigs.
    ~Grissom: Don't insult the pigs, Nick. They're actually very clean.

  5. Re: Warning about dynamic ip addresses

    On 2007-10-06, Robert Zenz wrote:
    > Pseudo Silk Kimono wrote:
    >> On 2007-10-06, Pseudo Silk Kimono wrote:
    >>> After I got all the 253 updates installed, there were a couple of problems
    >>> so I thought I'd share them.
    >>>
    >>> 1) After a reboot, NONE of the following entries in my grub boot would
    >>> work
    >>>
    >>> title Ubuntu gutsy (development branch), kernel 2.6.22-13-server
    >>> root (hd1,1)
    >>> kernel /boot/vmlinuz-2.6.22-13-server root=UUID=c9f2e32f-304d-48bb-9c1a
    >>> -f44b49d0bbac ro quiet splash
    >>> initrd /boot/initrd.img-2.6.22-13-server
    >>> quiet
    >>>
    >>> title Ubuntu gutsy (development branch), kernel 2.6.22-13-server (reco
    >>> very mode)
    >>> root (hd1,1)
    >>> kernel /boot/vmlinuz-2.6.22-13-server root=UUID=c9f2e32f-304d-48bb-9c1a
    >>> -f44b49d0bbac ro single
    >>> initrd /boot/initrd.img-2.6.22-13-server
    >>>
    >>> The first one gave me an X config error and would not start up.
    >>> The second simply booted me into a command line. There's probably a way
    >>> to get X to start but I didn't want to spend the time. Besides, the
    >>> third option worked. I haven't tested my openSuse boot yet.
    >>>
    >>> 2) My IP address changed from xxx.xxx.x.100 to xxx.xxx.x.102 which meant having
    >>> to go into my router config and changing all the IP addresses which pointed
    >>> to my GG server.
    >>>

    >> Just a bit more information about these this issue with X:
    >>
    >> title Ubuntu gutsy (development branch), kernel 2.6.22-13-server
    >> root (hd1,1)
    >> kernel /boot/vmlinuz-2.6.22-13-server root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro quiet splash
    >> initrd /boot/initrd.img-2.6.22-13-server
    >> quiet
    >>
    >> Fails with the following:
    >>
    >> Failed to start the X server (your graphical interface). It is likely that it is not set up correctly. Would you like to view the X server output to diagnose the problem
    >>
    >> I said but it made no sense to me except for a piece that was complaining about the nvidia drivers. This would make me suspect that the kernel update blew away my restricted drivers.
    >>
    >> title Ubuntu gutsy (development branch), kernel 2.6.22-13-server (recovery mode)
    >> root (hd1,1)
    >> kernel /boot/vmlinuz-2.6.22-13-server root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro single
    >> initrd /boot/initrd.img-2.6.22-13-server
    >>
    >> Fine... but no GDM... cli only.
    >>
    >> title Ubuntu gutsy (development branch), kernel 2.6.22-13-rt
    >> root (hd1,1)
    >> kernel /boot/vmlinuz-2.6.22-13-rt root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro quiet splash
    >> initrd /boot/initrd.img-2.6.22-13-rt
    >> quiet
    >>
    >> Failed..same message as before
    >>
    >> title Ubuntu gutsy (development branch), kernel 2.6.22-13-rt (recovery mode)
    >> root (hd1,1)
    >> kernel /boot/vmlinuz-2.6.22-13-rt root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro single
    >> initrd /boot/initrd.img-2.6.22-13-rt
    >>
    >> Didn't bother with this, I would assume it would boot me into a cli as well.
    >>
    >> Which leaves me with:
    >>
    >> title Ubuntu gutsy (development branch), kernel 2.6.22-12-386
    >> root (hd1,1)
    >> kernel /boot/vmlinuz-2.6.22-12-386 root=UUID=c9f2e32f-304d-48bb-9c1a-f44b49d0bbac ro quiet splash
    >> initrd /boot/initrd.img-2.6.22-12-386
    >> quiet
    >>
    >> And that's fine. But I would like to be able to get the first one working since it appears to be a more recent kernel and is the "server" version.
    >>
    >>

    >
    > Hello.
    >
    > You're a little mistaken, the second entry in grub works fine, it is
    > supposed to take you to a command line as root. It's intended to be the
    > last hope if you blew up your system.
    >
    > But that thing with the X can be surely changed very quick. Let it boot,
    > and change to a terminal (Strg+Alt+F1), login and rebuild the xorg.conf
    > with the command
    > sudo dpkg-reconfigure xserver-xorg
    > When you get asked about the drivers for your card, select vesa, this
    > will sure work, you can also try nvidia or nv, maybe it works.
    >
    > Rob


    Thank you. I was able to get it to work using vesa.
    --
    PSK - RLU 452647 http://improve-usenet.org
    Killing GG on Ubuntu, openSUSE, Vista and XP with slrn and Xnews
    ~Nick: People are pigs.
    ~Grissom: Don't insult the pigs, Nick. They're actually very clean.

  6. Re: Warning about dynamic ip addresses

    Pseudo Silk Kimono wrote:
    > After I got all the 253 updates installed, there were a couple of problems
    > so I thought I'd share them.
    >
    > 1) After a reboot, NONE of the following entries in my grub boot would
    > work


    ------------ bunch of non-working items snipped ----------------

    > 2) My IP address changed from xxx.xxx.x.100 to xxx.xxx.x.102


    Are you sure this was Ubuntu? nah, say it ain't so?




  7. Re: Warning about dynamic ip addresses

    On 2007-10-06, Motley Guy wrote:
    > Pseudo Silk Kimono wrote:
    >> After I got all the 253 updates installed, there were a couple of problems
    >> so I thought I'd share them.
    >>
    >> 1) After a reboot, NONE of the following entries in my grub boot would
    >> work

    >
    > ------------ bunch of non-working items snipped ----------------
    >
    >> 2) My IP address changed from xxx.xxx.x.100 to xxx.xxx.x.102

    >
    > Are you sure this was Ubuntu? nah, say it ain't so?
    >
    >
    >



    Thought about it... it could have been my router assigning the IP
    address since I don't use static IPs. But, it's never done this
    before. Normally, the only IP that changes is the IP my ISP
    assigns to my router, and I did check the IP address of my
    router and it had not changed, so I was not suspicious of my router.


    --
    PSK - RLU 452647 http://improve-usenet.org
    Killing GG on Ubuntu, openSUSE, Vista and XP with slrn and Xnews
    ~Nick: People are pigs.
    ~Grissom: Don't insult the pigs, Nick. They're actually very clean.

  8. Re: Warning about dynamic ip addresses

    Pseudo Silk Kimono wrote:
    > On 2007-10-06, Motley Guy wrote:
    >
    >> Pseudo Silk Kimono wrote:
    >>
    >>> After I got all the 253 updates installed, there were a couple of problems
    >>> so I thought I'd share them.
    >>>
    >>> 1) After a reboot, NONE of the following entries in my grub boot would
    >>> work
    >>>

    >> ------------ bunch of non-working items snipped ----------------
    >>
    >>
    >>> 2) My IP address changed from xxx.xxx.x.100 to xxx.xxx.x.102
    >>>

    >> Are you sure this was Ubuntu? nah, say it ain't so?
    >>
    >>
    >>
    >>

    >
    >
    > Thought about it... it could have been my router assigning the IP
    > address since I don't use static IPs. But, it's never done this
    > before. Normally, the only IP that changes is the IP my ISP
    > assigns to my router, and I did check the IP address of my
    > router and it had not changed, so I was not suspicious of my router.



    You shouldn't be suspicious of your router. It's faithfully obeying your
    preferences.

    However you should use a *static* IP in your server(s) so they can be found.


    --
    John

    No Microsoft products were used in the preparation or transmission of this message.

    The EULA sounds like it was written by a team of lawyers who want to tell me what I can't do. The GPL sounds like it was written by a human being, who wants me to know what I can do.

  9. Re: Warning about dynamic ip addresses

    John F. Morse wrote:
    > Pseudo Silk Kimono wrote:
    >> On 2007-10-06, Motley Guy wrote:
    >>
    >>> Pseudo Silk Kimono wrote:
    >>>
    >>>> After I got all the 253 updates installed, there were a couple of
    >>>> problems
    >>>> so I thought I'd share them.
    >>>>
    >>>> 1) After a reboot, NONE of the following entries in my grub boot would
    >>>> work
    >>>>
    >>> ------------ bunch of non-working items snipped ----------------
    >>>
    >>>
    >>>> 2) My IP address changed from xxx.xxx.x.100 to xxx.xxx.x.102
    >>> Are you sure this was Ubuntu? nah, say it ain't so?
    >>>
    >>>
    >>>
    >>>

    >>
    >>
    >> Thought about it... it could have been my router assigning the IP
    >> address since I don't use static IPs. But, it's never done this
    >> before. Normally, the only IP that changes is the IP my ISP
    >> assigns to my router, and I did check the IP address of my
    >> router and it had not changed, so I was not suspicious of my router.

    >
    >
    > You shouldn't be suspicious of your router. It's faithfully obeying your
    > preferences.
    >
    > However you should use a *static* IP in your server(s) so they can be
    > found.
    >
    >



    I tried dynamic and never could get it to work.
    Using 3 boxes on lan. 1 xp for my daughter for school, 1 Feisty, 1
    Whatever Linux for testing.Now Gutsy. Static always works.
    caver1

  10. Re: Warning about dynamic ip addresses

    On 2007-10-06, John F. Morse wrote:
    >
    > However you should use a *static* IP in your server(s) so they can be found.
    >
    >

    Thanks for the advice. I switched my networking to use a static IP address.
    I guess I did it right (at least for now) since I can get online.
    System -> Administration -> Network
    Highlight wired connection
    Click properties
    Switch Configuration to "Static IP Address"
    Enter IP address
    Enter Subnet mask: 255.255.255.0
    Enter Gateway address: 192.168.0.1

    sudo /etc/init.d/networking restarting
    ifconfig
    eth0 Link encap:Ethernet HWaddr 00:134:1E0:0A
    inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0
    inet6 addr: fe80::213:d4ff:fe1e:d00a/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:1662416 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1264654 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1625645700 (1.5 GB) TX bytes:300042034 (286.1 MB)
    Interrupt:19 Base address:0xe000

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:232 errors:0 dropped:0 overruns:0 frame:0
    TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:36343 (35.4 KB) TX bytes:36343 (35.4 KB)

    Sound or look right?

    --
    PSK - RLU 452647 http://improve-usenet.org
    Killing GG on Ubuntu, openSUSE, Vista and XP with slrn and Xnews
    ~Nick: People are pigs.
    ~Grissom: Don't insult the pigs, Nick. They're actually very clean.

  11. Re: Warning about dynamic ip addresses

    Pseudo Silk Kimono wrote:
    > On 2007-10-06, John F. Morse wrote:
    >
    >> However you should use a *static* IP in your server(s) so they can be found.
    >>
    >>
    >>

    > Thanks for the advice. I switched my networking to use a static IP address.
    > I guess I did it right (at least for now) since I can get online.
    > System -> Administration -> Network
    > Highlight wired connection
    > Click properties
    > Switch Configuration to "Static IP Address"
    > Enter IP address
    > Enter Subnet mask: 255.255.255.0
    > Enter Gateway address: 192.168.0.1
    >
    > sudo /etc/init.d/networking restarting
    > ifconfig
    > eth0 Link encap:Ethernet HWaddr 00:134:1E0:0A
    > inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0
    > inet6 addr: fe80::213:d4ff:fe1e:d00a/64 Scope:Link
    > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    > RX packets:1662416 errors:0 dropped:0 overruns:0 frame:0
    > TX packets:1264654 errors:0 dropped:0 overruns:0 carrier:0
    > collisions:0 txqueuelen:1000
    > RX bytes:1625645700 (1.5 GB) TX bytes:300042034 (286.1 MB)
    > Interrupt:19 Base address:0xe000
    >
    > lo Link encap:Local Loopback
    > inet addr:127.0.0.1 Mask:255.0.0.0
    > inet6 addr: ::1/128 Scope:Host
    > UP LOOPBACK RUNNING MTU:16436 Metric:1
    > RX packets:232 errors:0 dropped:0 overruns:0 frame:0
    > TX packets:232 errors:0 dropped:0 overruns:0 carrier:0
    > collisions:0 txqueuelen:0
    > RX bytes:36343 (35.4 KB) TX bytes:36343 (35.4 KB)
    >
    > Sound or look right?



    I don't hear anything, but it looks like it should work. ;-)

    The IP for that PC is the "inet addr:" 192.168.0.102, which is
    changeable from ifconfig if you ever want to do it (see man ifconfig).
    Some GUI network program also can do this, as you found.

    Also check /etc/resolv.conf to be sure it has the IP of the DNS server,
    which in your case would be the router's IP, 192.168.0.1 (DNS then goes
    out to your ISP's DNS server).

    Since you are now using a static IP that won't change, you can always
    find the computer.

    You can also put an IP and a hostname into the /etc/hosts file and be
    able to connect to another PC by using its hostname. The form is:
    IP_address canonical_hostname [aliases...]

    Examples:


    127.0.0.1 localhost ad.doubleclick.net
    192.168.0.101 son.mydomain.org son
    192.168.0.102 psk.mydomain.org psk
    192.168.0.103 wife.mydomain.org wife

    The first one will stop those pesky doubleclick ads and banners. See
    "man hosts" for more info.

    --
    John

    No Microsoft products were used in the preparation or transmission of this message.

    The EULA sounds like it was written by a team of lawyers who want to tell me what I can't do. The GPL sounds like it was written by a human being, who wants me to know what I can do.

+ Reply to Thread