Accessing a printer from another VLAN
-
@louis2 said in Accessing a printer from another VLAN:
the gui is not accessable from the other lans, unless the printer is in active mode
If it sleeping, the GUI server part is shut down ?
@louis2 said in Accessing a printer from another VLAN:
never managed to get gui access via IPV6
My 5100 doesn't support DHCP6, only a rudimentary Ipv6 static setup, I had to set up manually an IPv6 :
and I had to create an IPv6 host override (bottom part of the resolver).
Now, when I visit "https://brother-hotel....... my browser accesses the printer GUI using IPv6.
-
@Gertjan
hey there,
same here: put printer's IPv6 (here I use ULA instead of GUA) in unbound's host override. I can reach my printer now via IPv4 and IPv6 (ULA) from subnets. Using SLAAC, since my ISP is giving out dynamic v6 prefixes.
Works fine for me, used those IPs (v4 and v6-ULA plus FQDN) in brother printer's certificate for ssl (thanx to pfsense's cert manager easily done).
Surprisingly, my printer's GUI is reachable even when the device is asleep (energy saving mode)... -
Sorry, GUI via IPV6 is working! Even better ín opposite to IPV4 it always works even if the printer is 'a sleep'.
Since I use fixed addresses for all my equipment, I did set-up the IPV6-address via the printer GUI.
In general IPV6 seems to work significant better than IPV4.So its all working now.
I found and downloaded the manual. Much more info that in the online manual. Not so easy to find that download, since it is not an item in the download menu. I found it someway via the online helpmenu.
There are a lot of options, I will probably never useI just do not like that:
- it is possible to change some settings via the panel without any form of autorisation, e.g. you can change the IP-address ....
- less sevire, as far as I know I can not limit gui access based on IPV6 address. However than there is password protection
-
@Gertjan said in Accessing a printer from another VLAN:
far less. Microsoft devices : I'm not sure. Windows can detect printers and other devices on the same network, As far as I know, Windows doesn't make use of what Avahi makes 'visible' to them (shows the existence of devices elsewhere) but as these devices are on another network, things start to be complicated. Although a PC could reach out to the device, check out the GUID, so it knows what driver it needs, etc .... but no ... Microsoft is still locked into the ancient Network Neighborhood mentality
Well, I have to take my words back I was wrong.
I brought with me my windows pro 11 laptop, and connected the wifi to my captive portal network.
All went well, I was presented immediately with a login page, and I could connect.As windows doesn't 'know' (recognized) the network, the network was defined as the default, save public mode. This means that my laptop will not see/use/access any local resources except the gateway. This is enough for a working Internet connection.
I switched to "trusted".
Then : Settings -> Bluetooth and Devices -> Printers and scanners and hit "Add a device".
After several seconds, it started to list all my brother printers and the big Ricoh copy color scanner printer. All these devices are on my LAN, and my laptop was connected to another LAN, my OPT1 or captive portal network.So, I have to take back my words : Windows 11 (pro, if that matters) works just fine, it can see and use printer on other networks. IMHO : It must be using the announcements that Avahi makes on my portal network.
No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ?? -
@louis2 It's not that it works better, just that most firmware these days gets confused in dual-stack mode, especially during reduced power CPU states. I have setup HAProxy in TCP mode to act as a mediator for both IPv4 and IPv6 addresses of my printers. This opens up a lot more possibilities (as far as authentication and authorization for printing goes) through the use of an SSO, such as authelia.
-
@Gertjan Both things are true. Yes, Win11 works just fine, but also MS has made a mess with all windows config that is not likely do be resolved until they completely move away from the old control panel and consolidate all GP options to have counterparts in the Settings app. They are caught between the need to move on (completely) to the new way of doing things (general DNS and native TCP/IP solutions for everything) and the need to support those clients that, while they upgraded their server and desktop Windows to a new version, their setup is unchanged (or at least, its topology is) from the one they had in the Windows Server 2003 days...
I ranted all that, because the option to choose the location for a network (or options that essentially do the same thing) exists in at least 5 different places in the OS. Registry, netsh powershell, GPEdit, control panel, settings... All methods of configuring a setting should be about the same setting (eg, in registry). That is currently not the case. -
I completely agree with the windows11 config mess. In windows 7 and 10 it was simple / logical now things should be configured. Windows 11 shit IMHO.
I strogly prefer ^the old^ condiguration screen! -
@louis2 Man, I dream sometimes that all that "new age" (in reality we are too lazy and cheap and fired all old devs or drove them out) crap would go away, and Windows would have the Vista UI, with that Aero Glass, and through the years the OS would have gotten thinner and lighter, and with today's hardware... That would be AWESOME! But... the new design team likes the almost minecraft style UI they made in 2 days and called it a day. For shame.
-
@louis2 "Oh, isn't it nice, dear, that you can have 2105549 different ways to change 45032432452345 configuration variables for the same exact thing? Should we create, besides settings, an old control panel, a new control panel and a "did you just assume my age?" control panel? Isn't it nice that we have 96% of our devs (windows team) find ways to make money of the user's data and metadata and blast them with ads or sponsored content from every direction? Aren't we serious and good at our jobs, and show that we take things seriously, when the differences from one major upgrade to the next are a few more ways to align the start button and some changes to the color of the icons? Also, wait for Windows 123 in order to have taskbar toolbars again?" BARF
-
@louis2 I say, the right time for Windows Vista is now. It's almost the same kernel. Remove GPOs, rewrite/patch the NT kernel (without telemetry), optimize the Aero Glass UI for new HW, slap a one time fee of 500$ for 10 years (I would happily pay that), su and take my money.
-
@ myself Hahaha, for whomever didn't realize it, this is what an unnecessary rant looks like. Let it serve as an example of what NOT to do in this forum. Please, read the forum rules.
