10:45 p.m.
Hi!
This might be a little bit out of topic on this list but I am getting
out of options. So here we go and thank you for your patience:
I have a few Fedora clients on one subnet, a firewall and the Internet
on one side. Then in a different room, far away from my router I have a
HP printer with a RJ-45 connector.
I then bought an inexpensive Wi-Fi Repeater/Router with 2 Ethernet ports
(I guess 1 WAN, 1 LAN), thinking I could connect a cable from the LAN
port and to the Wifi using that device allowing me to share that printer
over my network.
I've setup that device as a repeater and the wifi part works. However it
seems the LAN interface can only be setup as a different subnet. Let's
say my network is 192.168.0.x then the LAN interface IP is automatically
set by the device firmware as 192.168.1.x (netmasks are all at
255.255.255.0) . The repeater IP is currently given by the DHCP server
running on my router and on 192.168.0.x. Currently I can't see the
printer from my computer.
I could also set up the device as a router (I however assume I'd need a
cable from the WAN port to my router), an AP (would need a cable from my
router to the device - so no) or an WISP (not what I need neither) but
it doesn't seem to fit.
I've already spent 2 days on this and starting to lose my hair... so do
you guys have any suggestion or done this before?
Looking forward to reading from you.
Thank you.
Fred
11:24 p.m.
On Wed, 2020-03-04 at 11:45 +0700, Frederic Muller wrote:
I then bought an inexpensive Wi-Fi Repeater/Router with 2 Ethernet
ports (I guess 1 WAN, 1 LAN), thinking I could connect a cable from
the LAN port and to the Wifi using that device allowing me to share
that printer over my network.
Tell us the make and model of the device.
--
uname -rsvp
Linux 3.10.0-1062.12.1.el7.x86_64 #1 SMP Tue Feb 4 23:02:59 UTC 2020 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
11:30 p.m.
On 3/4/20 12:24 PM, Tim via users wrote:
On Wed, 2020-03-04 at 11:45 +0700, Frederic Muller wrote:
> I then bought an inexpensive Wi-Fi Repeater/Router with 2 Ethernet
> ports (I guess 1 WAN, 1 LAN), thinking I could connect a cable from
> the LAN port and to the Wifi using that device allowing me to share
> that printer over my network.
Tell us the make and model of the device.
Sure, it's a PIXLINK LV-WR09 300Mbps Wireless-N Repeater/Router/AP .
Thank you.
Fred
4:19 a.m.
On Wed, 2020-03-04 at 12:30 +0700, Frederic Muller wrote:
it's a PIXLINK LV-WR09 300Mbps Wireless-N Repeater/Router/AP
Looking at this:
http://pmod1b8a3.pic8.websiteonline.cn/upload/WR09QuickInstallationGuide.pdf
It looks like it should support the mode you want. Try using it as an
access point. Can you follow their guide? Get back to us with how far
you can manage to get.
--
uname -rsvp
Linux 3.10.0-1062.12.1.el7.x86_64 #1 SMP Tue Feb 4 23:02:59 UTC 2020 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
4:30 a.m.
On 3/4/20 5:19 PM, Tim via users wrote:
On Wed, 2020-03-04 at 12:30 +0700, Frederic Muller wrote:
> it's a PIXLINK LV-WR09 300Mbps Wireless-N Repeater/Router/AP
Looking at this:
http://pmod1b8a3.pic8.websiteonline.cn/upload/WR09QuickInstallationGuide.pdf
It looks like it should support the mode you want. Try using it as an
access point. Can you follow their guide? Get back to us with how far
you can manage to get.
Oh yes it supports the mod that I want, except that I am failing to
connect to the printer probably because of IP routing issues. I was in
fact expecting the LAN port to connect to the same subnet as if it was a
Wifi connection to the repeater. Apparently it doesn't work this way.
AP mode cannot work as I would need to lay a cable between my router and
the AP: then I'm better off setting up the cable directly to the
printer... which I cannot do.
So my question is how can I connect from 192.168.0.x subnet to
192.168.1.x subnet (or specific printer IP) knowing this connection
doesn't go through my router/firewall (which is on 192.168.0.1).
The repeater IP is currently dynamic (I can probably set it as fixed)
and falls randomly between 100 to 190, which would be the gateway to
access the printer. And that's where my routing knowledge tells me there
is a problem.
Thank you.
Fred
5:09 a.m.
On 2020-03-04 18:30, Frederic Muller wrote:
On 3/4/20 5:19 PM, Tim via users wrote:
> On Wed, 2020-03-04 at 12:30 +0700, Frederic Muller wrote:
>> it's a PIXLINK LV-WR09 300Mbps Wireless-N Repeater/Router/AP
> Looking at this:
> http://pmod1b8a3.pic8.websiteonline.cn/upload/WR09QuickInstallationGuide.pdf
>
> It looks like it should support the mode you want. Try using it as an
> access point. Can you follow their guide? Get back to us with how far
> you can manage to get.
>
Oh yes it supports the mod that I want, except that I am failing to
connect to the printer probably because of IP routing issues. I was in
fact expecting the LAN port to connect to the same subnet as if it was a
Wifi connection to the repeater. Apparently it doesn't work this way.
AP mode cannot work as I would need to lay a cable between my router and
the AP: then I'm better off setting up the cable directly to the
printer... which I cannot do.
So my question is how can I connect from 192.168.0.x subnet to
192.168.1.x subnet (or specific printer IP) knowing this connection
doesn't go through my router/firewall (which is on 192.168.0.1).
The repeater IP is currently dynamic (I can probably set it as fixed)
and falls randomly between 100 to 190, which would be the gateway to
access the printer. And that's where my routing knowledge tells me there
is a problem.
So, your system is on the 192.168.0.x subnet and the repeater IP is as well. You can
ping the IP repeater, yes?
And the HP printer has an IP address of 192.168.1.x. Do you know what "x" is?
It sounds to me that you should first fix the IP address of the repeater. After that, it
sounds as if you
need to add a static route on your system to the 192.168.1.x subnet via the repeater.
On your system, what it the output of....
ip route show
--
The key to getting good answers is to ask good questions.
5:45 a.m.
On Wed, 4 Mar 2020 at 06:34, Frederic Muller <fred(a)cm17.com> wrote:
On 3/4/20 5:19 PM, Tim via users wrote:
> On Wed, 2020-03-04 at 12:30 +0700, Frederic Muller wrote:
>> it's a PIXLINK LV-WR09 300Mbps Wireless-N Repeater/Router/AP
> Looking at this:
>
http://pmod1b8a3.pic8.websiteonline.cn/upload/WR09QuickInstallationGuide.pdf
>
> It looks like it should support the mode you want. Try using it as an
> access point. Can you follow their guide? Get back to us with how far
> you can manage to get.
>
Oh yes it supports the mod that I want, except that I am failing to
connect to the printer probably because of IP routing issues. I was in
fact expecting the LAN port to connect to the same subnet as if it was a
Wifi connection to the repeater. Apparently it doesn't work this way.
I assume you are using WISP mode. The above document is short on
detail, but mentions "routing", so may offer a bridge configuration that
actually works. It sounds like the lan port is getting NATed addresses.
It isn't clear if you know the IP assigned to the printer. Your printer
should
be able to generate a status page that shows the IP assigned by the
router.
Some models with displays can show the IP.
To use WISP mode you may need to configure the router to allow specific
ports from wifi to connect to the LAN side. Unless there are more options
than
the "Quick" guide provides, you can't connect to the printer.
AP mode cannot work as I would need to lay a cable between my router and
the AP: then I'm better off setting up the cable directly to the
printer... which I cannot do.
Have you considered powerline ethernet? That can work well, but depends
on the way the building was wired.
So my question is how can I connect from 192.168.0.x subnet to
192.168.1.x subnet (or specific printer IP) knowing this connection
doesn't go through my router/firewall (which is on 192.168.0.1).
The repeater IP is currently dynamic (I can probably set it as fixed)
and falls randomly between 100 to 190, which would be the gateway to
access the printer. And that's where my routing knowledge tells me there
is a problem.
You want a bridge, not a router. The problem is that you can't rely on the
technical information from online shopping sites, and two low-end devices
with the same model number are often different internally. There are
simple
devices that do what you want, but some have a poor antenna, so many
don't have proper UL certification (in case fire, insurance has an excuse to
avoid paying). The most robust route is to build your own from a
single-board
computer (SBC) with wifi and an ethernet port. There are excellent online
groups
that can help with linux or BSD-based router/bridge configurations for SBC
hardware.
--
George N. White III
5:54 a.m.
On 3/4/20 6:09 PM, Ed Greshko wrote:
> The repeater IP is currently dynamic (I can probably set it as
fixed)
> and falls randomly between 100 to 190, which would be the gateway to
> access the printer. And that's where my routing knowledge tells me there
> is a problem.
So, your system is on the 192.168.0.x subnet and the repeater IP is as well. You can
ping the IP repeater, yes?
And the HP printer has an IP address of 192.168.1.x. Do you know what "x" is?
It sounds to me that you should first fix the IP address of the repeater. After that, it
sounds as if you
need to add a static route on your system to the 192.168.1.x subnet via the repeater.
On your system, what it the output of....
ip route show
Dear Ed,
Yes I can ping the repeater. In fact the firmware is a web app which I
access to configure it and change its settings.
The HP printer has the option to be set using a DHCP server or
manually. I set it up manually as it will be easier to "find" the
printer I assumed. So yes the IP is 192.168.1.20.
ip route show gives:
default via 192.168.0.1 dev wlp4s0 proto dhcp metric 600
192.168.0.0/24 dev wlp4s0 proto kernel scope link src 192.168.0.134
metric 600
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
linkdown
So I'll have to add this route to any machine needing to connect to the
printer right?
Thank you.
Fred
6:01 a.m.
On 3/4/20 6:45 PM, George N. White III wrote:
I assume you are using WISP mode.
Ok i wasn't clear about
WISP mode and my first search didn't return what
I found now. So no, I am using repeater mode but maybe I should dig into
that WISP mode in fact.
The above document is short on
detail, but mentions "routing", so may offer a bridge configuration that
actually works. It sounds like the lan port is getting NATed
addresses.
yes the LAN port seems to be automatically NATed to the next subnet
available. Even though you can manually change that, should you pick the
same subnet as the repeater it then defaults back to the next available
subnet.
It isn't clear if you know the IP assigned to the printer. Your
printer should
be able to generate a status page that shows the IP assigned by the
router.
Some models with displays can show the IP.
As I replied to Ed the printer can be
either using DHCP or manually
assigned IP/mask/gateway. so I'd say it's the easy side of the equation
(or I hope since I haven't managed to reach it yet).
To use WISP mode you may need to configure the router to allow
specific
ports from wifi to connect to the LAN side. Unless there are more
options than
the "Quick" guide provides, you can't connect to the printer.
Thank you for the heads up I think I need to dig into that mode.
Well time for dinner down here but definitely something to do after ;-)
Thanks a lot.
Fred
6:31 a.m.
On 2020-03-04 19:54, Frederic Muller wrote:
On 3/4/20 6:09 PM, Ed Greshko wrote:
>> The repeater IP is currently dynamic (I can probably set it as fixed)
>> and falls randomly between 100 to 190, which would be the gateway to
>> access the printer. And that's where my routing knowledge tells me there
>> is a problem.
> So, your system is on the 192.168.0.x subnet and the repeater IP is as well. You
can
> ping the IP repeater, yes?
>
> And the HP printer has an IP address of 192.168.1.x. Do you know what "x"
is?
>
> It sounds to me that you should first fix the IP address of the repeater. After
that, it sounds as if you
> need to add a static route on your system to the 192.168.1.x subnet via the
repeater.
>
> On your system, what it the output of....
>
> ip route show
Dear Ed,
Yes I can ping the repeater. In fact the firmware is a web app which I access to
configure it and change its settings.
The HP printer has the option to be set using a DHCP server or manually. I set it up
manually as it will be easier to "find" the printer I assumed. So yes the IP is
192.168.1.20.
ip route show gives:
default via 192.168.0.1 dev wlp4s0 proto dhcp metric 600
192.168.0.0/24 dev wlp4s0 proto kernel scope link src 192.168.0.134 metric 600
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
So I'll have to add this route to any machine needing to connect to the printer
right?
First, you'd need a route to 192.168.1.0/24 via whatever the IP is of the router.
Which is why it should
be a fixed IP.
Then, it may not be necessary to have the route on all systems if you set up this one
system as
a print server for all systems on the 192.168.0.0/24 LAN segment.
--
The key to getting good answers is to ask good questions.
7:53 a.m.
On Wed, 2020-03-04 at 17:30 +0700, Frederic Muller wrote:
Oh yes it supports the mod that I want, except that I am failing to
connect to the printer probably because of IP routing issues. I was
in fact expecting the LAN port to connect to the same subnet as if it
was a Wifi connection to the repeater. Apparently it doesn't work
this way.
AP mode cannot work as I would need to lay a cable between my router
and the AP: then I'm better off setting up the cable directly to the
printer... which I cannot do.
Sorry, I was thinking backwards. I'm not sure if an access port can
actually work equally bi-directionally.
But there looks like several possible scenarios for using it.
If you're only connecting one thing, then the 2nd (client) mode seems
the most obvious. It would be acting as an external WiFi adaptor for
something that doesn't have built in WiFi (they list smart TVs, games,
computers, but a printer is just yet another device).
The 3rd mode on that list, as a repeater ought to work (it mentions
that clients can connect to it via WiFi or ethernet).
The 5th mode on that list, WISP sounds like another contender, similar
to the 3rd mode.
Though, in either case, it would depend if it just repeats as a bridge
or simple switch (connects your other WiFi router through itself to the
ethernet port), or if it also interposes itself in the middle as
another router. Since it has its own inbuilt web-based configuration,
it does look like it might be difficult to have it not behave as a
router in the middle. It mentions acting as a gateway by default, but
that page doesn't give much detail about using it not as one.
So my question is how can I connect from 192.168.0.x subnet to
192.168.1.x subnet (or specific printer IP) knowing this connection
doesn't go through my router/firewall (which is on 192.168.0.1).
The repeater IP is currently dynamic (I can probably set it as fixed)
and falls randomly between 100 to 190, which would be the gateway to
access the printer. And that's where my routing knowledge tells me
there is a problem.
Yes, things would be a lot easier to manage if your devices always have
the same address.
Another issue to consider is your original WiFi router. With one of
mine, its wired ethernet and WiFi can be on different subnets.
--
uname -rsvp
Linux 3.10.0-1062.12.1.el7.x86_64 #1 SMP Tue Feb 4 23:02:59 UTC 2020 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
1:41 a.m.
On 3/4/20 7:31 PM, Ed Greshko wrote:
On 2020-03-04 19:54, Frederic Muller wrote:
> On 3/4/20 6:09 PM, Ed Greshko wrote:
>>> The repeater IP is currently dynamic (I can probably set it as fixed)
>>> and falls randomly between 100 to 190, which would be the gateway to
>>> access the printer. And that's where my routing knowledge tells me there
>>> is a problem.
>> So, your system is on the 192.168.0.x subnet and the repeater IP is as well. You
can
>> ping the IP repeater, yes?
>>
>> And the HP printer has an IP address of 192.168.1.x. Do you know what
"x" is?
>>
>> It sounds to me that you should first fix the IP address of the repeater. After
that, it sounds as if you
>> need to add a static route on your system to the 192.168.1.x subnet via the
repeater.
>>
>> On your system, what it the output of....
>>
>> ip route show
> Dear Ed,
>
> Yes I can ping the repeater. In fact the firmware is a web app which I access to
configure it and change its settings.
>
> The HP printer has the option to be set using a DHCP server or manually. I set it up
manually as it will be easier to "find" the printer I assumed. So yes the IP is
192.168.1.20.
>
> ip route show gives:
> default via 192.168.0.1 dev wlp4s0 proto dhcp metric 600
> 192.168.0.0/24 dev wlp4s0 proto kernel scope link src 192.168.0.134 metric 600
> 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
>
> So I'll have to add this route to any machine needing to connect to the printer
right?
>
>
First, you'd need a route to 192.168.1.0/24 via whatever the IP is of the router.
Which is why it should
be a fixed IP.
Then, it may not be necessary to have the route on all systems if you set up this one
system as
a print server for all systems on the 192.168.0.0/24 LAN segment.
Hi!
So I tried to go that way and I haven't been so successful. At this
stage this is what I'm getting:
- added the route on the firewall/router/dhcp server (pfsense) : didn't
seem to propagate
- manually added the route on my machine and I have this:
default via 192.168.0.1 dev wlp4s0 proto dhcp metric 600
192.168.0.0/24 dev wlp4s0 proto kernel scope link src 192.168.0.134
metric 600
192.168.1.0/24 via 192.168.0.20 dev wlp4s0
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
linkdown
- pinging tests:
ping 192.168.0.20 works
ping 192.168.1.254 doesn't work (that's the repeater IP on the other subnet)
ping 192.168.1.20 doesn't work
- Switch to the repeater wifi xxx_net. My machine IP switched to the
other subnet and became 192.168.1.104
- pinging tests:
ping 192.168.1.254 works
ping 192.168.1.20 doesn't work (and the printer is on and shows the
right IP configuration)
- Tried to add the "network" printer and it didn't work neither
So obviously I have 2 issues:
- routing to other subnet doesn't seem to work
- "network" printer doesn't seem to work as such
It'd be nice to be able to fix the routing issue, but if the printer
doesn't work in a network configuration it is somehow moot for now.
Thank you all for your help in the matter.
Fred
1:55 a.m.
On 03/05/2020 12:41 AM, Frederic Muller wrote:
So obviously I have 2 issues:
- routing to other subnet doesn't seem to work
- "network" printer doesn't seem to work as such
Three questions:
First, can you ping the printer from a box on the same subnet?
Second, if so, can you print from that box?
Third, can you reach that router's config page from the box on a
different subnet?
2:05 a.m.
On 3/5/20 2:55 PM, Joe Zeff wrote:
On 03/05/2020 12:41 AM, Frederic Muller wrote:
> So obviously I have 2 issues:
> - routing to other subnet doesn't seem to work
> - "network" printer doesn't seem to work as such
Three questions:
First, can you ping the printer from a box on the same subnet?
No which is why
I'm wondering if I don't have another issue with the printer
Second, if so, can you print from that box?
Neither, as it
doesn't seem to find the printer
Third, can you reach that router's config page from the box on a
different subnet?
Yes can!
So I'm going to temporary move the printer to the main switch, change
the ethernet cable and see if that works... then let you know.
Thank you.
Fred
2:13 a.m.
On 03/05/2020 01:05 AM, Frederic Muller wrote:
So I'm going to temporary move the printer to the main switch, change
the ethernet cable and see if that works... then let you know.
Try changing the cable first and don't worry about printing from the
other subnet until you can get it printing from the same one.
2:16 a.m.
On 3/5/20 3:05 PM, Frederic Muller wrote:
On 3/5/20 2:55 PM, Joe Zeff wrote:
> On 03/05/2020 12:41 AM, Frederic Muller wrote:
>> So obviously I have 2 issues:
>> - routing to other subnet doesn't seem to work
>> - "network" printer doesn't seem to work as such
>
> Three questions:
>
> First, can you ping the printer from a box on the same subnet?
No which is why I'm wondering if I don't have another issue with the
printer
> Second, if so, can you print from that box?
Neither, as it doesn't seem to find the printer
> Third, can you reach that router's config page from the box on a
> different subnet?
Yes can!
So I'm going to temporary move the printer to the main switch, change
the ethernet cable and see if that works... then let you know.
Thank you.
Fred
ok, it was actually a cable issue. Replaced and then I can ping and add
the printer when on the same subnet.
So now I'm back to my routing issue :-D
Fred
2:23 a.m.
On 03/05/2020 01:16 AM, Frederic Muller wrote:
So now I'm back to my routing issue :-D
Great! It's always best to break things like this down into separate
issues and fix them one at a time and in this case, your router issue
didn't matter until you had the printer working locally.
6:49 a.m.
On Thu, 5 Mar 2020 at 04:17, Frederic Muller <fred(a)cm17.com> wrote:
On 3/5/20 3:05 PM, Frederic Muller wrote:
On 3/5/20 2:55 PM, Joe Zeff wrote:
On 03/05/2020 12:41 AM, Frederic Muller wrote:
So obviously I have 2 issues:
- routing to other subnet doesn't seem to work
- "network" printer doesn't seem to work as such
Three questions:
First, can you ping the printer from a box on the same subnet?
No which is why I'm wondering if I don't have another issue with the
printer
Second, if so, can you print from that box?
Neither, as it doesn't seem to find the printer
Third, can you reach that router's config page from the box on a different
subnet?
Yes can!
So I'm going to temporary move the printer to the main switch, change the
ethernet cable and see if that works... then let you know.
Thank you.
Fred
ok, it was actually a cable issue. Replaced and then I can ping and add
the printer when on the same subnet.
So now I'm back to my routing issue :-D
From the manual:
"LAN Port: One 10/100Mbps RJ45 Ethernet port used to add wireless
connectivity to an Ethernet-enabled device such as Internet TV, DVR,
Gaming console and so on. Please note that this port is not allowed to
be connected with router."
These are all devices that need outbound access, but do not offer network
services.
--
George N. White III
6:04 p.m.
On Thu, 2020-03-05 at 08:49 -0400, George N. White III wrote:
From the manual:
"LAN Port: One 10/100Mbps RJ45 Ethernet port used to add wireless
connectivity to an Ethernet-enabled device such as Internet TV, DVR,
Gaming console and so on. Please note that this port is not allowed
to be connected with router."
These are all devices that need outbound access, but do not offer
network services.
Though that could be something as simple as because it would conflict
with its DHCP service, or NAT behind NAT facing the wrong way.
Something that didn't have such a conflict mayn't be incompatible.
--
uname -rsvp
Linux 3.10.0-1062.12.1.el7.x86_64 #1 SMP Tue Feb 4 23:02:59 UTC 2020 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
9:31 p.m.
On 3/5/20 7:49 PM, George N. White III wrote:
These are all devices that need outbound access, but do not offer
network
services.
wow.. I'm feeling like I got cheated now. I have a spare (or 2)
wifi
router. I'll see if I can set it up in a similar way then. The thing
takes a lot more space though.
Anyone know of smaller device similar to that Pixlink thing that would
work both ways?
Thank you really for your help.
Fred
11:54 p.m.
On 3/4/20 2:19 AM, Tim via users wrote:
On Wed, 2020-03-04 at 12:30 +0700, Frederic Muller wrote:
> it's a PIXLINK LV-WR09 300Mbps Wireless-N Repeater/Router/AP
Looking at this:
http://pmod1b8a3.pic8.websiteonline.cn/upload/WR09QuickInstallationGuide.pdf
It looks like it should support the mode you want. Try using it as an
access point. Can you follow their guide? Get back to us with how far
you can manage to get.
According to that document, I think what you really want is client mode.
That should make anything connected to the ethernet port be part of
your regular network. The device connects to your main wifi router and
shares the connection over the ethernet port.
1:45 a.m.
On 3/6/20 12:54 PM, Samuel Sieb wrote:
On 3/4/20 2:19 AM, Tim via users wrote:
> On Wed, 2020-03-04 at 12:30 +0700, Frederic Muller wrote:
>> it's a PIXLINK LV-WR09 300Mbps Wireless-N Repeater/Router/AP
>
> Looking at this:
> http://pmod1b8a3.pic8.websiteonline.cn/upload/WR09QuickInstallationGuide.pdf
>
>
> It looks like it should support the mode you want. Try using it as an
> access point. Can you follow their guide? Get back to us with how far
> you can manage to get.
According to that document, I think what you really want is client
mode. That should make anything connected to the ethernet port be
part of your regular network. The device connects to your main wifi
router and shares the connection over the ethernet port.
OK so I had to re-flash my old Netgear using DD-WRT as the repeat mode
in Netgear firmware doesn't support WPA2-PSK (only WEP or open). And it
now works perfectly. Just takes an awful lot of space with cables, power
adapter and just the "repeater" itself. Note that took me no time
compared to that other "new" device I got.
Now I will however try to set it up in client mode and see how this
goes. Thank you very much for your patience and the time spent finding a
solution for me.
Fred
2:16 a.m.
On 3/6/20 12:54 PM, Samuel Sieb wrote:
According to that document, I think what you really want is client
mode. That should make anything connected to the ethernet port be
part of your regular network. The device connects to your main wifi
router and shares the connection over the ethernet port.
Ok I tried the WISP mode
which is actually that client mode. It doesn't
seem to work as such in fact and looks exactly the same as the repeater
mode. I get a prompt to rename the 'extended wifi' with _ext and the Lan
IP gets set to a different subnet. Pinging the printer doesn't work
(while pinging the device works). So it seems I might be stuck with my
older and bigger router.
Well only costed me $13 and I am sure I must have a friend who'll be
happy to get a free repeater :-)
Thank you.
Fred
5:16 a.m.
On Fri, 6 Mar 2020 at 04:17, Frederic Muller <fred(a)cm17.com> wrote:
On 3/6/20 12:54 PM, Samuel Sieb wrote:
> According to that document, I think what you really want is client
> mode. That should make anything connected to the ethernet port be
> part of your regular network. The device connects to your main wifi
> router and shares the connection over the ethernet port.
Ok I tried the WISP mode which is actually that client mode. It doesn't
seem to work as such in fact and looks exactly the same as the repeater
mode. I get a prompt to rename the 'extended wifi' with _ext and the Lan
IP gets set to a different subnet. Pinging the printer doesn't work
(while pinging the device works). So it seems I might be stuck with my
older and bigger router.
Might be worth asking the DD-WRT people about the smallest device
that runs DD-WRT. I have used a wifi to ethernet bridge, but choose
a model with a good (e.g., big) antenna useful with laptops that
weren't able to get wifi at locations distant from an access point.
Well only costed me $13 and I am sure I must have a friend who'll be
happy to get a free repeater :-)
That device sucks as a repeater, but might be useful connecting "an
Ethernet-enabled device such as Internet TV, DVR, Gaming console
and so on" if there is a good wifi signal at the wall outlet.
--
George N. White III
1538
days inactive
1540
days old
23 comments
6 participants
participants (6)
-
Ed Greshko -
Frederic Muller -
George N. White III -
Joe Zeff -
Samuel Sieb -
Tim