Re: difficult to isolate problem - browser access to router has problems on on machine but not other
On Ma, 17 apr 12, 23:17:10, Arthur Marsh wrote: I'd like to try a different chipset network card in the AMD64 machine next. Sounds like a good idea. Kind regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: difficult to isolate problem - browser access to router has problems on on machine but not other
* Arthur Marsh arthur.ma...@internode.on.net wrote: Hi, I've tried to run through all I can think of and am getting a bit stuck. I have two machines running Debian (one a dual-core Pentium4 with i386, the other a quad-core AMD64-X2 with amd64), both with built-in ethernet cards. The Pentium4 machine can access the browser interface of the adsl router I use with no problems. The AMD64 machine has recently taken to stalling after entering the username and password for the adsl router's browser interface, and I've tried downgrading recent package upgrades, and different kernels and browsers without success. However, the AMD64 machine booted with the sysrescuecd can access the browser interface of the adsl router without problems. The AMD64 machine has a built-in Realtek 8169 NIC. Not that I've got very much experience with network issues, but I'll answer anyway. To me this still sounds like some ethernet issue. I'd first if there are any oddities with the output of # ip addr and # ethtool -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jmpmlf$slb$1...@dough.gmane.org
Re: difficult to isolate problem - browser access to router has problems on on machine but not other
Keith wrote, on 18/04/12 05:26: On 17/04/12 14:53, Arthur Marsh wrote: Thanks for your suggestions, but I've tried several browsers on the AMD64 machine and experience the same fault, so I'm tending towards an AMD64-specific bug that happens with the realtek 8169 chipset. Arthur. I haven't been following this thread, so may have missed it but have you got the firmware drivers on your 64bit system, as you say it works on your 32bit system? Yes, firmware-realtek from non-free is installed on both machines. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/964369-i66@ppp14-2-48-242.lns21.adl2.internode.on.net
Re: difficult to isolate problem - browser access to router has problems on on machine but not other
Indulekha wrote, on 17/04/12 00:44: Arthur Marsharthur.ma...@internode.on.net wrote: Yes, gtklauncher from libwebkit on each machine. Probably worth a try with elinks (or opera or iceweasel or some other proper browser), as libwebkit purports to be made to be embedded in other applications, such as mail readers, or web browsers. It may not your best bet in this particular instance... I tried chromium and iceweasel and a few other browsers and still had the same problem on the AMD64 machine. I also bought a replacement realtek 8169 NIC and tried that, with the same problem on the AMD64 machine but no problem on the Pentium4 machine running the i386 version of Debian. I'd like to try a different chipset network card in the AMD64 machine next. Arthur. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ur8069-2rm@ppp14-2-48-242.lns21.adl2.internode.on.net
Re: difficult to isolate problem - browser access to router has problems on on machine but not other
Camaleón wrote, on 17/04/12 00:25: On Mon, 16 Apr 2012 07:34:55 +0930, Arthur Marsh wrote: Camaleón wrote, on 15/04/12 23:43: (...) Are you accessing to the router web interface using the same browser from both machines? What's the browser that gets stuck after the login screen? Yes, gtklauncher from libwebkit on each machine. Mmm, I don't know the capabilities of gtklauncher but if it works on one computer it should also work in the other. Are there any differences between both computer environments (e.g., same package version of libwebkit?). Also, 32 and 64 bits package versions can make a difference so to discard any bug or incompatibility problem with gtklauncher I would try with a different browser. As mentioned in another sub-thread I bought a realtek 8169 based network card (same chipset as the built-in ethernet on the AMD64 motherboard). This worked in the Pentium4 machine running the i386 version of Debian at accessing the router's web interface, but failed on the AMD64 machine running the AMD64 version of Debian. I'd like to try a network card with a different chipset in the AMD64 machine. (Also one could put the hard disk from the Pentium4 machine in the AMD64 machine to run the i386 version of Debian in the AMD64 machine). I've saved wireshark traces from both machines. As it gets stuck after login, more than a connectivity issue I would go for a management issue, I mean, the browser cannot handle the client request and this can be caused by many sources (bad web interface programming, cookies, javascript error...). Well, you can check if the router provides a telnet/ssh access alternative and manage it from there. I find CLI modes of these devices are most stable and reliable than their web interface. It does have a telnet interface, but that interface doesn't offer any management capabilities. In my experience, it uses to be the opposite: while CLI provides all of the settings that can be tweaked, the web GUI only gives the user the possibility to configure the basics and hides the rest :-) Greetings, Thanks for your suggestions, but I've tried several browsers on the AMD64 machine and experience the same fault, so I'm tending towards an AMD64-specific bug that happens with the realtek 8169 chipset. Arthur. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/b79069-rq9@ppp14-2-48-242.lns21.adl2.internode.on.net
Re: difficult to isolate problem - browser access to router has problems on on machine but not other
On Tue, 17 Apr 2012 23:23:14 +0930, Arthur Marsh wrote: Camaleón wrote, on 17/04/12 00:25: (...) Are there any differences between both computer environments (e.g., same package version of libwebkit?). Also, 32 and 64 bits package versions can make a difference so to discard any bug or incompatibility problem with gtklauncher I would try with a different browser. As mentioned in another sub-thread I bought a realtek 8169 based network card (same chipset as the built-in ethernet on the AMD64 motherboard). This worked in the Pentium4 machine running the i386 version of Debian at accessing the router's web interface, but failed on the AMD64 machine running the AMD64 version of Debian. I'd like to try a network card with a different chipset in the AMD64 machine. (Also one could put the hard disk from the Pentium4 machine in the AMD64 machine to run the i386 version of Debian in the AMD64 machine). (...) But you already discarded the network card because it worked from a LiveCD (SystemRescueCD), right? Which makes me think this has to be some sort of software issue :-? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jmjuu4$h73$6...@dough.gmane.org
Re: difficult to isolate problem - browser access to router has problems on on machine but not other
Camaleón wrote, on 18/04/12 00:02: On Tue, 17 Apr 2012 23:23:14 +0930, Arthur Marsh wrote: Camaleón wrote, on 17/04/12 00:25: (...) Are there any differences between both computer environments (e.g., same package version of libwebkit?). Also, 32 and 64 bits package versions can make a difference so to discard any bug or incompatibility problem with gtklauncher I would try with a different browser. As mentioned in another sub-thread I bought a realtek 8169 based network card (same chipset as the built-in ethernet on the AMD64 motherboard). This worked in the Pentium4 machine running the i386 version of Debian at accessing the router's web interface, but failed on the AMD64 machine running the AMD64 version of Debian. I'd like to try a network card with a different chipset in the AMD64 machine. (Also one could put the hard disk from the Pentium4 machine in the AMD64 machine to run the i386 version of Debian in the AMD64 machine). (...) But you already discarded the network card because it worked from a LiveCD (SystemRescueCD), right? Which makes me think this has to be some sort of software issue :-? Greetings, Yes, but it could be software specific to the chipset on the network card that has been upgraded since the version that appeared on sysrescuecd. Arthur. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8cc069-4gg@ppp14-2-48-242.lns21.adl2.internode.on.net
Re: difficult to isolate problem - browser access to router has problems on on machine but not other
On Wed, 18 Apr 2012 00:17:04 +0930, Arthur Marsh wrote: Camaleón wrote, on 18/04/12 00:02: (...) I'd like to try a network card with a different chipset in the AMD64 machine. (Also one could put the hard disk from the Pentium4 machine in the AMD64 machine to run the i386 version of Debian in the AMD64 machine). (...) But you already discarded the network card because it worked from a LiveCD (SystemRescueCD), right? Which makes me think this has to be some sort of software issue :-? Yes, but it could be software specific to the chipset on the network card that has been upgraded since the version that appeared on sysrescuecd. Exactly, but that will be a software issue in the end (e.g., the network card kernel module). Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jmk0i6$h73$9...@dough.gmane.org
Re: difficult to isolate problem - browser access to router has problems on on machine but not other
On 17/04/12 14:53, Arthur Marsh wrote: Thanks for your suggestions, but I've tried several browsers on the AMD64 machine and experience the same fault, so I'm tending towards an AMD64-specific bug that happens with the realtek 8169 chipset. Arthur. I haven't been following this thread, so may have missed it but have you got the firmware drivers on your 64bit system, as you say it works on your 32bit system? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f8dcae3.5040...@gmail.com
Re: difficult to isolate problem - browser access to router has problems on on machine but not other
On Mon, 16 Apr 2012 07:34:55 +0930, Arthur Marsh wrote: Camaleón wrote, on 15/04/12 23:43: (...) Are you accessing to the router web interface using the same browser from both machines? What's the browser that gets stuck after the login screen? Yes, gtklauncher from libwebkit on each machine. Mmm, I don't know the capabilities of gtklauncher but if it works on one computer it should also work in the other. Are there any differences between both computer environments (e.g., same package version of libwebkit?). Also, 32 and 64 bits package versions can make a difference so to discard any bug or incompatibility problem with gtklauncher I would try with a different browser. I've saved wireshark traces from both machines. As it gets stuck after login, more than a connectivity issue I would go for a management issue, I mean, the browser cannot handle the client request and this can be caused by many sources (bad web interface programming, cookies, javascript error...). Well, you can check if the router provides a telnet/ssh access alternative and manage it from there. I find CLI modes of these devices are most stable and reliable than their web interface. It does have a telnet interface, but that interface doesn't offer any management capabilities. In my experience, it uses to be the opposite: while CLI provides all of the settings that can be tweaked, the web GUI only gives the user the possibility to configure the basics and hides the rest :-) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jmhbt1$o2a$5...@dough.gmane.org
Re: difficult to isolate problem - browser access to router has problems on on machine but not other
Arthur Marsh arthur.ma...@internode.on.net wrote: Yes, gtklauncher from libwebkit on each machine. Probably worth a try with elinks (or opera or iceweasel or some other proper browser), as libwebkit purports to be made to be embedded in other applications, such as mail readers, or web browsers. It may not your best bet in this particular instance... -- ❤ ♫ ❤ ♫ ❤ ♫ ❤ Indulekha -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120416151429.GA18168@radhesyama
Re: difficult to isolate problem - browser access to router has problems on on machine but not other
Arthur Marsh arthur.ma...@internode.on.net wrote: Are there any browsers on Debian that support javascript without having to run under the X window system? It does sound like a browser issue. lynx is pretty good at js. -- ❤ ♫ ❤ ♫ ❤ ♫ ❤ Indulekha -- ❤ ♫ ❤ ♫ ❤ ♫ ❤ Indulekha -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120415134334.GA29045@radhesyama
Re: difficult to isolate problem - browser access to router has problems on on machine but not other
On Sun, 15 Apr 2012 13:30:14 +0930, Arthur Marsh wrote: Hi, I've tried to run through all I can think of and am getting a bit stuck. I have two machines running Debian (one a dual-core Pentium4 with i386, the other a quad-core AMD64-X2 with amd64), both with built-in ethernet cards. The Pentium4 machine can access the browser interface of the adsl router I use with no problems. The AMD64 machine has recently taken to stalling after entering the username and password for the adsl router's browser interface, and I've tried downgrading recent package upgrades, and different kernels and browsers without success. Are you accessing to the router web interface using the same browser from both machines? What's the browser that gets stuck after the login screen? However, the AMD64 machine booted with the sysrescuecd can access the browser interface of the adsl router without problems. So one problem less: no hardware error on the amd64 computer. The AMD64 machine has a built-in Realtek 8169 NIC. debsums has so far been inconclusive at pointing to any corrupted files. I've also swapped ports that the pc's use on the router without any noticeable change, and have powered-down both the pc and router completely to eliminate issues caused by power glitches. Are there any browsers on Debian that support javascript without having to run under the X window system? Firefox/Iceweasel require an X server to be installed (not in full, just the minimal package) but not necessarily a running DE. Any other suggestions welcome. Well, you can check if the router provides a telnet/ssh access alternative and manage it from there. I find CLI modes of these devices are most stable and reliable than their web interface. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jmel33$3it$2...@dough.gmane.org
Re: difficult to isolate problem - browser access to router has problems on on machine but not other
On Sun, 15 Apr 2012 08:43:34 -0500 Indulekha indule...@theunworthy.com wrote: Arthur Marsh arthur.ma...@internode.on.net wrote: Are there any browsers on Debian that support javascript without having to run under the X window system? It does sound like a browser issue. lynx is pretty good at js. lynx supports Javascript? I've long been under the impression that it does not, although I can't currently find an authoritative reference one way or another. [The Lynx Wikipedia page claims that it does not, but the citation is to a TechRepublic article which does not actually state that.] Celejar -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120415112645.059fc5b5.cele...@gmail.com
Re: difficult to isolate problem - browser access to router has problems on on machine but not other
Celejar cele...@gmail.com wrote: On Sun, 15 Apr 2012 08:43:34 -0500 Indulekha indule...@theunworthy.com wrote: Arthur Marsh arthur.ma...@internode.on.net wrote: Are there any browsers on Debian that support javascript without having to run under the X window system? It does sound like a browser issue. lynx is pretty good at js. lynx supports Javascript? I've long been under the impression that it does not, although I can't currently find an authoritative reference one way or another. [The Lynx Wikipedia page claims that it does not, but the citation is to a TechRepublic article which does not actually state that.] Sorry, links not lynx. Also elinks. :) -- ❤ ♫ ❤ ♫ ❤ ♫ ❤ Indulekha -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120415154723.GA2317@radhesyama
Re: difficult to isolate problem - browser access to router has problems on on machine but not other
On Sun, 15 Apr 2012 10:47:23 -0500 Indulekha indule...@theunworthy.com wrote: Celejar cele...@gmail.com wrote: On Sun, 15 Apr 2012 08:43:34 -0500 Indulekha indule...@theunworthy.com wrote: Arthur Marsh arthur.ma...@internode.on.net wrote: Are there any browsers on Debian that support javascript without having to run under the X window system? It does sound like a browser issue. lynx is pretty good at js. lynx supports Javascript? I've long been under the impression that it does not, although I can't currently find an authoritative reference one way or another. [The Lynx Wikipedia page claims that it does not, but the citation is to a TechRepublic article which does not actually state that.] Sorry, links not lynx. Also elinks. I don't know about links, but links2 has removed Javascript support several years ago, as we've discussed many times on this list: http://lists.debian.org/debian-user/2008/04/msg01429.html Celejar -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120415122144.a58a4506.cele...@gmail.com
Re: difficult to isolate problem - browser access to router has problems on on machine but not other
On 4/14/2012 11:00 PM, Arthur Marsh wrote: Hi, I've tried to run through all I can think of and am getting a bit stuck. I have two machines running Debian (one a dual-core Pentium4 with i386, the other a quad-core AMD64-X2 with amd64), both with built-in ethernet cards. The Pentium4 machine can access the browser interface of the adsl router I use with no problems. The AMD64 machine has recently taken to stalling after entering the username and password for the adsl router's browser interface, and I've tried downgrading recent package upgrades, and different kernels and browsers without success. However, the AMD64 machine booted with the sysrescuecd can access the browser interface of the adsl router without problems. The AMD64 machine has a built-in Realtek 8169 NIC. debsums has so far been inconclusive at pointing to any corrupted files. I've also swapped ports that the pc's use on the router without any noticeable change, and have powered-down both the pc and router completely to eliminate issues caused by power glitches. Are there any browsers on Debian that support javascript without having to run under the X window system? Any other suggestions welcome. Read the docs and everything you find online for that make/model of ADSL router. What you're looking for specifically is whether it is designed to use an admin PC. Some of these consumer routers force you to enter an IP address of only one machine that can log into the admin interface. Others simply store a cookie on the first machine you log in with then deny access from any machine without that cookie. There are probably other variations on this theme as well. Given what you describe, I'd be 99% sure something like this is what you're up against. Clear the cookies cache on both machines, then try the problem machine first. In addition to reading all docs you can find. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f8b2844.8050...@hardwarefreak.com
Re: difficult to isolate problem - browser access to router has problems on on machine but not other
Camaleón wrote, on 15/04/12 23:43: On Sun, 15 Apr 2012 13:30:14 +0930, Arthur Marsh wrote: Hi, I've tried to run through all I can think of and am getting a bit stuck. I have two machines running Debian (one a dual-core Pentium4 with i386, the other a quad-core AMD64-X2 with amd64), both with built-in ethernet cards. The Pentium4 machine can access the browser interface of the adsl router I use with no problems. The AMD64 machine has recently taken to stalling after entering the username and password for the adsl router's browser interface, and I've tried downgrading recent package upgrades, and different kernels and browsers without success. Are you accessing to the router web interface using the same browser from both machines? What's the browser that gets stuck after the login screen? Yes, gtklauncher from libwebkit on each machine. I've saved wireshark traces from both machines. Well, you can check if the router provides a telnet/ssh access alternative and manage it from there. I find CLI modes of these devices are most stable and reliable than their web interface. It does have a telnet interface, but that interface doesn't offer any management capabilities. Arthur. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/79tr59-lih@ppp14-2-48-242.lns21.adl2.internode.on.net
Re: difficult to isolate problem - browser access to router has problems on on machine but not other
Stan Hoeppner wrote, on 16/04/12 05:27: On 4/14/2012 11:00 PM, Arthur Marsh wrote: ... The AMD64 machine has recently taken to stalling after entering the username and password for the adsl router's browser interface, and I've tried downgrading recent package upgrades, and different kernels and browsers without success. ... Read the docs and everything you find online for that make/model of ADSL router. What you're looking for specifically is whether it is designed to use an admin PC. Some of these consumer routers force you to enter an IP address of only one machine that can log into the admin interface. Others simply store a cookie on the first machine you log in with then deny access from any machine without that cookie. There are probably other variations on this theme as well. Given what you describe, I'd be 99% sure something like this is what you're up against. Clear the cookies cache on both machines, then try the problem machine first. In addition to reading all docs you can find. Interesting suggestion, but given that the AMD64 machine can still access the router's web interface without problem when booted from sysrescuecd, I'm not sure that this is the case. Thanks for the suggestion! Arthur. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/gjtr59-n2i@ppp14-2-48-242.lns21.adl2.internode.on.net
