Page 3 of 3 FirstFirst 123
Results 21 to 27 of 27

Thread: Confused newbie with network problems

  1. #21
    Quote Originally Posted by durks View Post
    That all seems fine. Your router - when it's acting as DHCP server - will have addresses in the range .2 to .249, That means you're allowed to pick .250 as a fixed IP address for your Vortexbox: that'll work, and you have no danger of an address conflict.

    But I'm confused here. Can you confirm that:

    1. Your Vortexbox is active on 192.168.1.2 (i.e. that you reach your Vortexbox when you go to http://192.168.1.2); and that
    2. Its web 'network configuration' still reports a static address of 192.168.1.250.

    If that's *still* the case, then can you tell us what happens when you *reboot* the Vortexbox? What's its address then?
    1. Right, on 192.168.1.2 I reach VB and
    2. in VB network config it reads 192.168.1.250 after reboot.
    Attached Images Attached Images  
    Last edited by Janaka; 07-12-2012 at 04:36 PM.

  2. #22
    Senior Member
    Join Date
    Nov 2011
    Location
    Scotland
    Posts
    163
    Aha. The problem, I think, is that the MAC address in your /etc/sysconfig/network-scripts/ifcfg-eth0 file is incorrect.

    Looking at your earlier postings, you wrote:

    cat /etc/sysconfig/network-scripts/ifcfg-eth0
    ...[snip]...
    HWADDR=00:21:85:C4:14:00
    ...[snip]...

    but

    /sbin/ifconfig eth0
    ...[snip]...
    eth0 Link encap:Ethernet HWaddr 00:21:9B:7E:FA:41
    ...[snip]...

    Those two MAC addresses should be the same if this is to make any sense.

    I don't know why this has happened on your machine (do you have multiple physical interfaces?), but my suggestion is to edit (by hand) the file /etc/sysconfig/network-scripts/ifcfg-eth0, replace the line

    HWADDR=00:21:85:C4:14:00

    by

    HWADDR=00:21:9B:7E:FA:41

    then reboot, and see what happens.

  3. #23
    After reboot VB welcome screen says web GUI URL is: 192.168.1.2.
    ifconfig eth0 says inet addr is: 192.168.1.250 - which also work i web GUI.
    So I guess I'm happy now because VB i up and running and ripping.
    But still I don't understand why the addresses differ...
    Thank you all guys for helping me out - here in Sweden - VB is great!!!

  4. #24
    After reboot VB welcome screen says web GUI URL is: 192.168.1.2.
    ifconfig eth0 says inet addr is: 192.168.1.250 - which also work i web GUI.
    So I guess I'm happy now because VB i up and running and ripping.
    But still I don't understand why the addresses differ...
    Thank you all guys for helping me out - here in Sweden - VB is great!!!

  5. #25
    Senior Member
    Join Date
    Nov 2011
    Location
    Scotland
    Posts
    163
    Quote Originally Posted by Janaka View Post
    After reboot VB welcome screen says web GUI URL is: 192.168.1.2.
    ifconfig eth0 says inet addr is: 192.168.1.250 - which also work i web GUI.
    Just to confirm: that's a reboot *after* you editted the /etc/sysconfig/network-scripts/ifcfg-eth0 file as suggested above - correct?

    If so, your system now sounds correctly configured, and has the static IP address 192.168.1.250.

    Ignore that 'welcome' screen: I *think* there must be a minor bug somewhere in the VB code that means that an old address acquired by DHCP can get reported on that screen, even though the actual IP address is now different. In fact, I see that same effect on my own system. I've been ignoring up until now because it's harmless but, since you've reminded me, I might try to figure out what's causing it, and correct it. If I do, I'll post back.

  6. #26
    Yes, thats after.
    Thanx again!

  7. #27
    Quote Originally Posted by durks View Post

    Ignore that 'welcome' screen: I *think* there must be a minor bug somewhere in the VB code that means that an old address acquired by DHCP can get reported on that screen, even though the actual IP address is now different. In fact, I see that same effect on my own system. I've been ignoring up until now because it's harmless but, since you've reminded me, I might try to figure out what's causing it, and correct it. If I do, I'll post back.
    This minor bug is caused by starting the script networkcheck.sh in the background, I've explained the issue in my post in "General".

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •