• WLAN Extender on Subnet

    From David W. Hodgins@21:1/5 to wg1@gmx.net on Tue Jan 19 12:44:26 2021
    On Tue, 19 Jan 2021 12:34:32 -0500, WG <wg1@gmx.net> wrote:

    Greetings!

    This is a home LAN with an OpenSuSE Linux gateway and a WLAN Router.
    The Gateway has the fix IP 192.168.1.222 with NetMask 255.255.255.0.
    The WLAN router has the fix address 192.168.1.240.
    It had the default address 192.168.0.1 which I modified to fit the subnet. All clients are connected viad dhcp.
    Connection via cable or wireless works fine.

    Now I want to add a WLAN Extender which has the fix IP 192.168.0.254.
    The extenders ip addr is not changable.

    My question:
    What needs to be done to integrate the new subnet 192.168.0.n
    with the subnet 192.168.1.n so that the clients traffic connected to the extender is routed to the gateway 192.168.1.222?

    Thanx for reading and hints.

    Change the netmask to 255.255.0.0, so it's 192.168.0.0/16

    Regards, Dave Hodgins

    --
    Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
    email replies.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From WG@21:1/5 to All on Tue Jan 19 18:34:32 2021
    Greetings!

    This is a home LAN with an OpenSuSE Linux gateway and a WLAN Router.
    The Gateway has the fix IP 192.168.1.222 with NetMask 255.255.255.0.
    The WLAN router has the fix address 192.168.1.240.
    It had the default address 192.168.0.1 which I modified to fit the subnet.
    All clients are connected viad dhcp.
    Connection via cable or wireless works fine.

    Now I want to add a WLAN Extender which has the fix IP 192.168.0.254.
    The extenders ip addr is not changable.

    My question:
    What needs to be done to integrate the new subnet 192.168.0.n
    with the subnet 192.168.1.n so that the clients traffic connected to the extender is routed to the gateway 192.168.1.222?

    Thanx for reading and hints.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jim Jackson@21:1/5 to David W. Hodgins on Tue Jan 19 18:34:22 2021
    On 2021-01-19, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
    On Tue, 19 Jan 2021 12:34:32 -0500, WG <wg1@gmx.net> wrote:

    Greetings!

    This is a home LAN with an OpenSuSE Linux gateway and a WLAN Router.
    The Gateway has the fix IP 192.168.1.222 with NetMask 255.255.255.0.
    The WLAN router has the fix address 192.168.1.240.
    It had the default address 192.168.0.1 which I modified to fit the subnet. >> All clients are connected viad dhcp.
    Connection via cable or wireless works fine.

    Now I want to add a WLAN Extender which has the fix IP 192.168.0.254.
    The extenders ip addr is not changable.

    My question:
    What needs to be done to integrate the new subnet 192.168.0.n
    with the subnet 192.168.1.n so that the clients traffic connected to the
    extender is routed to the gateway 192.168.1.222?

    I don't think you need to do anything, for the actual wireless clients
    it services. It's only for admin of the device. It is possible to add an
    IP address in the 192.168.0.0/24 range on the device you are going to
    use to admin the wireless device.

    as root ifconfig eth0:1 192.168.0.1

    or better use ip but I can't remember the invocation.


    Thanx for reading and hints.

    Change the netmask to 255.255.0.0, so it's 192.168.0.0/16

    Regards, Dave Hodgins


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jim Jackson@21:1/5 to Jim Jackson on Tue Jan 19 18:35:39 2021
    On 2021-01-19, Jim Jackson <jj@franjam.org.uk> wrote:
    On 2021-01-19, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
    On Tue, 19 Jan 2021 12:34:32 -0500, WG <wg1@gmx.net> wrote:

    Greetings!

    This is a home LAN with an OpenSuSE Linux gateway and a WLAN Router.
    The Gateway has the fix IP 192.168.1.222 with NetMask 255.255.255.0.
    The WLAN router has the fix address 192.168.1.240.
    It had the default address 192.168.0.1 which I modified to fit the subnet. >>> All clients are connected viad dhcp.
    Connection via cable or wireless works fine.

    Now I want to add a WLAN Extender which has the fix IP 192.168.0.254.
    The extenders ip addr is not changable.

    My question:
    What needs to be done to integrate the new subnet 192.168.0.n
    with the subnet 192.168.1.n so that the clients traffic connected to the >>> extender is routed to the gateway 192.168.1.222?

    I don't think you need to do anything, for the actual wireless clients
    it services. It's only for admin of the device. It is possible to add an
    IP address in the 192.168.0.0/24 range on the device you are going to
    use to admin the wireless device.

    as root ifconfig eth0:1 192.168.0.1

    or better use ip but I can't remember the invocation.


    I was going to add - if it can't be changed, it means you can't have more
    than one on your network. A bit strange.


    Thanx for reading and hints.

    Change the netmask to 255.255.0.0, so it's 192.168.0.0/16

    Regards, Dave Hodgins


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From WG@21:1/5 to All on Wed Jan 20 10:43:26 2021
    On 19.01.2021 18:34, WG wrote:
    Greetings!

    This is a  home LAN with an OpenSuSE Linux gateway and a WLAN Router.
    The Gateway has the fix IP 192.168.1.222 with NetMask 255.255.255.0.
    The WLAN router has the fix address 192.168.1.240.
    It had the default address 192.168.0.1 which I modified to fit the subnet. All clients are connected viad dhcp.
    Connection via cable or wireless works fine.

    Now I want to add a WLAN Extender which has the fix IP 192.168.0.254.
    The extenders ip addr is not changable.

    My question:
    What needs to be done to integrate the new subnet 192.168.0.n
    with the subnet 192.168.1.n so that the clients traffic connected to the extender is routed to the gateway 192.168.1.222?

    Thanx for reading and hints.

    Thanks for your comments, all up and working :-)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)