1. Forum
  2. FidoNet
  3. ALT.OS.LINUX.MAGEIA

  • network address conflict

    From faeychild@2:250/1 to All on Tue Dec 1 00:06:46 2020


    I have a pop up from the network center that states

    Network is up on interface Wired (Ethernet)
    (enp0s31f6)
    IPv6 Address: 192.168.20.4
    IP Address: 192.168.20.20
    Gateway: 192.168.20.1
    DNS: 8.8.8.8



    ]# ifconfig -a
    enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.20.20 netmask 255.255.255.0 broadcast 192.168.20.255
    ether 1c:1b:0d:a4:b2:8f txqueuelen 1000 (Ethernet)
    RX packets 71191 bytes 91877589 (87.6 MiB)
    RX errors 0 dropped 91 overruns 0 frame 0
    TX packets 40491 bytes 3755512 (3.5 MiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    device interrupt 16 memory 0xf7700000-f7720000


    I am considering assigning static addresses to the NIC and printer on
    the new router and I noticed that a few numbers don't appear to add up

    Network is currently up and running

    --
    faeychild
    Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Tue Dec 1 00:50:47 2020
    On Mon, 30 Nov 2020 19:06:46 -0500, faeychild <[email protected]> wrote:
    I have a pop up from the network center that states
    Network is up on interface Wired (Ethernet)
    (enp0s31f6)
    IPv6 Address: 192.168.20.4
    IP Address: 192.168.20.20
    Gateway: 192.168.20.1
    DNS: 8.8.8.8
    ]# ifconfig -a
    enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.20.20 netmask 255.255.255.0 broadcast 192.168.20.255
    ether 1c:1b:0d:a4:b2:8f txqueuelen 1000 (Ethernet)
    RX packets 71191 bytes 91877589 (87.6 MiB)
    RX errors 0 dropped 91 overruns 0 frame 0
    TX packets 40491 bytes 3755512 (3.5 MiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    device interrupt 16 memory 0xf7700000-f7720000
    I am considering assigning static addresses to the NIC and printer on
    the new router and I noticed that a few numbers don't appear to add up Network is currently up and running

    The IPv6 address shown above is an IPv4 address. Given that ifconfig -a is not showing an inet6 line with the IPv6 address, it looks like IPv6 has been disabled.

    The rest is normal. The router has an address of 192.168.20.1, is configured to work
    with devices connected to it with addresses in the range 192.168.20.0 to 192.168.20.255, and the pc ethernet card has an address of 192.168.20.20 that has
    either been statically set or assigned by dhcp.

    To use static only addresses turn off the dhcp server in the router and manually
    assign the desired address of each device to one within the range and that has not
    been assigned to another device such as the router.

    To mix static and dhcp addresses, reduce the range allowed by the router's dhcp
    server to for example, 192.168.20.128 to 192.168.20.255, and set all statically
    assigned addresses to be in the range 192.168.20.0 to 192.168.20.127.

    Is there something else about the above output that seems strange to you?

    Does the new router have a different default ip address?

    Regards, Dave Hodgins

    --
    Change [email protected] to [email protected] for
    email replies.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Tue Dec 1 01:50:47 2020
    On 1/12/20 11:50 am, David W. Hodgins wrote:



    To mix static and dhcp addresses, reduce the range allowed by the
    router's dhcp
    server to for example, 192.168.20.128 to 192.168.20.255, and set all statically
    assigned addresses to be in the range 192.168.20.0 to 192.168.20.127.

    After a cup of tea and some calm thinking and declarations of "IDIOT"!!
    I managed to do all of the above and found that it works. I also had a miss-typed gateway address.


    Is there something else about the above output that seems strange to you?

    Just that network center popup states an IPv4 address as IPv6 address

    Does the new router have a different default ip address?

    Just a little
    Old Billion 192.168.1.x

    New NetComm 192.168.20.x

    I am still surprised that the configuration is simpler than I expect.

    I always feel that an address change to a networked device will also
    require that the router be manually updated with the change also.
    But not so.


    thanks Dave
    regards


    --
    faeychild
    Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Tue Dec 1 02:12:52 2020
    On Mon, 30 Nov 2020 20:50:47 -0500, faeychild <[email protected]> wrote:
    Just a little
    Old Billion 192.168.1.x
    New NetComm 192.168.20.x
    I am still surprised that the configuration is simpler than I expect.
    I always feel that an address change to a networked device will also
    require that the router be manually updated with the change also.
    But not so.

    There is one thing that you have to be careful of when static ip addresses are used on the device. If the address is in the same range that may be used by the
    dhcp server in the router, then it's possible for the router to assign a dhcp address to another device that is the same as the one picked for the static assignment resulting in a conflict.

    Either turn off the dhcp server in the router, or reduce it's range and only assign status ip addresses within the range the router netmask allows that
    are outside of the range that the dhcp server might use. If all devices using that router are statically assigned, and no new devices that use dhcp are allowed the effect is the same as if the server was disabled.

    Regards, Dave Hodgins

    --
    Change [email protected] to [email protected] for
    email replies.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Tue Dec 1 02:14:59 2020
    On Tue, 1 Dec 2020 12:50:47 +1100, faeychild wrote:


    I am still surprised that the configuration is simpler than I expect.

    I always feel that an address change to a networked device will also
    require that the router be manually updated with the change also.
    But not so.


    Yup, the newer/smarter routers will allow you to set up your computer
    with a static address and not have to mess around in the router.

    I set my static ip in the xxx range, and leave the 0xx for any guests.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Tue Dec 1 04:45:51 2020
    On 1/12/20 1:14 pm, Bit Twister wrote:


    Yup, the newer/smarter routers will allow you to set up your computer
    with a static address and not have to mess around in the router.

    I set my static ip in the xxx range, and leave the 0xx for any guests.


    I'm not sure how "smart" this router is; it has settings way past my pay
    level

    NetComm NF18MESH

    DHCP range was 192.168.20.2 / 192.168.20.254

    It's now from 192.168.20.20 => " "
    Far more static addresses than I'll ever need

    I'll miss the Billion router, it would have worked fine but it didn't
    have voip telephone ports.

    regards
    --
    faeychild
    Running plasmashell 5.15.4 on 5.7.19-desktop-3.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)