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