On Wed, 2019-04-10 at 14:04 +0200, Dr Rainer Woitok wrote: > Louis, > > On Monday, 2019-04-08 19:19:02 +0200, you wrote: > > > ... > > I guess that the problem is with your router: if we query for the > > hostname new-host.local it returns 2 addresses: 192.168.2.106 AND > > 192.168.2.199. Now that second address is correct, the first one is > > bogus. So if we do the lookup later, we use the first address (that > > is > > incorrect) and we get into the timeouts. > > The funny thing is: I see that the .106 address gets used in the > > logfiles, but I don't see that in the wireshark traces? > > By looking into the "list*.txt" files I sent you I found the same > and > can confirm it: the scanner is (in fact was, see below) reachable > via > both addresses. The .106 address was a dynamic DHCP address used > for > scanning and printing from Windows, while the .199 address was a > static > DHCP address I tied to the device's MAC address in the router > configur- > ation in order to be able to use it from Linux without having to > fear > dynamic changes of it. > > Neither was I aware of these two addresses nor did I find a way to > rem- > ove the dynamic one. So I spent the better part of yesterday to > do a > factory reset of the router and to reinstall it using my notes from > the > first installation. This time I did not use any static DHCP > addresses > but rather set the expiration dates of all dynamic DHCP addresses > to > "never". > > This changed the scanner's address from .106/.199 to .102, and after > up- > dating my local "pixma.conf" file "scanimage -L" immediately > returned > the scanner information without any error messages or timeouts :-) > > But I still didn't find a way to turn this silly name "new-host" > into > something reasonable :-( > > And today my wife printed from her Windows laptop and now the IP > address > of the scanner again is .106! Back to square one ... :-( > > But since in the output from "scanimage -L" the scanner was > advertized > as "pixma:MX880_new-host.local", I tried to specify the scanner in > my > local "pixma.conf" file as "bjnp://new-host/timeout=5000" -- and > that > worked. So I will simply use that name rather than an IP address, > and > if I ever find a way to change the name in my router, I'll do so. > > That said, I regard the problem as locally solved and -- what's worse > -- > I can no longer run additional tests to find out what goes wrong > should > a scanner have more than one IP address. I do hope youl'll have > enough > information in the data I sent you to hunt down this problem. > > > To verify if this could be the problem, try the following from the > > PC: > > nslookup new-host.local > > Yes, this returned both addresses. > > > ... > > does your router have the possibility to allocate a fixed ip- > > address/hostname combination to a mac-address? If so, set it to > > MX880 > > and the .199 address and you may be in business > > It allows to permanently tie an IP-address to a MAC address > only. That > is what I did up to yesterday. > > > ... > > If you can tell me brand and model of the router, I can try to find > > the > > manual and see if that contains some hints > > It's a Vodafone EasyBox 804 which apparently is manufactured by > Arcadyan. > > > Oh, and please get the the output from: > > ip a s > > $ ip a s > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN > group default qlen 1000 > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever > inet6 ::1/128 scope host > valid_lft forever preferred_lft forever > 2: enp2s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN > group default qlen 1000 > link/ether 80:fa:5b:3d:1a:d9 brd ff:ff:ff:ff:ff:ff > 3: wwp0s20f0u5c3: <BROADCAST,MULTICAST,NOARP> mtu 1500 qdisc noop > state DOWN group default qlen 1000 > link/ether 1e:de:17:a0:80:ae brd ff:ff:ff:ff:ff:ff > 4: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state > UP group default qlen 1000 > link/ether 78:0c:b8:67:43:46 brd ff:ff:ff:ff:ff:ff > inet 192.168.2.105/24 brd 192.168.2.255 scope global wlp3s0 > valid_lft forever preferred_lft forever > inet6 fd91:dab6:a2b2:1:503:3277:e71b:a2/64 scope global temporary > dynamic > valid_lft 9701sec preferred_lft 2501sec > inet6 fd91:dab6:a2b2:1:7a0c:b8ff:fe67:4346/64 scope global > mngtmpaddr dynamic > valid_lft 9701sec preferred_lft 2501sec > inet6 fe80::7a0c:b8ff:fe67:4346/64 scope link > valid_lft forever preferred_lft forever > $ > > > and > > ip r s > > $ ip r s > default via 192.168.2.1 dev wlp3s0 > 192.168.2.0/24 dev wlp3s0 proto kernel scope link src > 192.168.2.105 > $ > > Hope this helps :-) > > Sincerely, > Rainer Hello Rainer It is good to see this solved. Given the somewhat nasty behavior of your router, you might want to give your printer a fixed address: reduce the DHCP range on the router (Einstellungen -> Netwerk) and set the end of the DHCP range (Letzste IP des Address Pool) to something below 254 (lets say 250) and set your printer to a fixed address of 192.168.2.251 (<.255 but outside the pool range you just set)
That will avoid the router messing with the addressing I am still wondering why the printer got back to the .106 address. BR, Louis -- sane-devel mailing list: [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to [email protected]
