Two hardware-related problems with Knoppix 5.0.1

Printable View

09-25-2006, 04:34 PM
DaXiuyi

Two hardware-related problems with Knoppix 5.0.1

G'day everyone,

Am a complete newbie to Linux, so sorry if I stuff up with terminology etc...

Am trying to get my Knoppix 5.0.1 to work, and it's doing great apart from 2 things:
1. Printers. I have a Samsung ML-1710 and when I try and configure it using the Configure Printers utility, I keep getting told that the driver doesn't exist. An earlier post suggested trying to configure it as a similar printer for which drivers exist (e.g. Samsung ML-1210), and I tried that, except it doesn't seem to work for any similar printers :(

2. Net connection. Konqueror seems to work fine, but Firefox just times out. I tried to use the network card configuration utility, but got a bit confused by the terms it asked for. Here's what I know from my Network connection settings in Windows XP: Address (assigned by DHCP), IP (xxx.xxx.1.2), Subnet (255.255.255.0) and Gateway (xxx.xxx.1.1). How do I get Knoppix to reflect this? I also tried to use the ADSL configuration utility, and I jst get timeouts all the time :S

If there's any particular output you need from a certain program or command prompt, please let me know. Otherwise any help would be greatly appreciated. I have seen solutions to similar sounding problems in the forums, but either they refer to an old ve4rsion of Knoppix or I've tried them and they don't work.

Any help would be greatly appreciated
09-25-2006, 05:23 PM
Harry Kuhman

Re: Two hardware-related problems with Knoppix 5.0.1

Quote:

Originally Posted by DaXiuyi

2. Net connection. Konqueror seems to work fine, but Firefox just times out. I tried to use the network card configuration utility, but got a bit confused by the terms it asked for. Here's what I know from my Network connection settings in Windows XP: Address (assigned by DHCP), IP (xxx.xxx.1.2), Subnet (255.255.255.0) and Gateway (xxx.xxx.1.1). How do I get Knoppix to reflect this? I also tried to use the ADSL configuration utility, and I jst get timeouts all the time :S

I can't answer you first question. 2 looks interesting, although I don't have a good theory about what is going on yet. In my mind if Konquror works then Firefox should too. Can you tell us more about your configuration? You mention ADSL but never mention pppoe configuration. Are you using a router (which I very highly recommend doing)? It looks that way from the little bit of the IP that you let us see, but if that's the case it's just ignorant to hide the 192.168.2.1 entire address (or other private unroutable IP asddress). Such addresses can't be reached fron the Internet, millions of people are using the same addresses, and there is no reason to hide it and good reason to show it, particularly when you are trying to get help resolving this problem.

If you are using a router then Knoppix should be doing a dhcp handshake at boot time. post what it is getting (the full numbers, not partial munged numbers), by posting the output of ifconfig. You can also set these values by doing a netcardconfig and answering the dhcp question in the negative, but I would like to see the ifconfig output first. It looks like the handshake may be failing, but that doesn't really explain Konquror working and Firefix not. I suspect it may be some strange proxy issue, but that's a very wild guess.

And if you are using a router the make and model and even firmware revision may help. Some modern DSL modems have a router built in, so check that. And you might want to look into the availability of a flash update for the router and if you are at the current firmware level.
09-25-2006, 08:01 PM
rec9140

Re: Two hardware-related problems with Knoppix 5.0.1

Quote:

Originally Posted by DaXiuyi

Am trying to get my Knoppix 5.0.1 to work, and it's doing great apart from 2 things:
1. Printers. I have a Samsung ML-1710 and when I try and configure it using the Configure Printers utility, I keep getting told that the driver doesn't exist. An earlier post suggested trying to configure it as a similar printer for which drivers exist (e.g. Samsung ML-1210), and I tried that, except it doesn't seem to work for any similar printers :(

Printers are fubar'd in 5.02 as per Klaus from the debian-knoppix list. Its a permissions issue. I had to go back to 4.02 due that issue alone as if I can't print I can't work.

Quote:

Originally Posted by DaXiuyi

2. Net connection. Konqueror seems to work fine, but Firefox just times out. I tried to use the network card configuration utility, but got a bit confused by the terms it asked for. Here's what I know from my Network connection settings in Windows XP: Address (assigned by DHCP), IP (xxx.xxx.1.2), Subnet (255.255.255.0) and Gateway (xxx.xxx.1.1). How do I get Knoppix to reflect this? I also tried to use the ADSL configuration utility, and I jst get timeouts all the time :S

Did you try to let it set things via DHCP and it failed when you ran the netcard config script ?

If not, then let it try to set things via the script and via DHCP. DHCP will answer all the questions for the script automatically. Some routers can be incompatible with DHCP on Knoppix and then you will need to run it manually.

If you run ipconfig /all from a command prompt on a winvirus box and write the output down the important items:

IP Address = same in the script
Netmask = should ALWAYS bee 255.255.255.0 (Would only change in very specific instances, not likely in a home net)
Default Gateway = your ROUTER's IP, which in the winworld is normaly 192.168.0.1, or 192.168.1.1 NOT 192.168.1.254 like *nix
Name Server = DNS Servers You can either use the ones provided from the ISP, or use your router for the DNS/Nameserver. Most modern soho type rotuers will act as a DNS proxy and forward on your request to the WAN side.

Give the DHCP option a try and then post back.
09-25-2006, 10:26 PM
Harry Kuhman

Re: Two hardware-related problems with Knoppix 5.0.1

Quote:

Originally Posted by rec9140

Netmask = should ALWAYS bee 255.255.255.0

This is a huge generalization, and not one that should go without a response. If you had said something like the netmask is usually 255.255.255.0 then I could accept that, but an uppercase always is just too strong. I have seen home networking equipment that uses different masks. A much better statement might be that DHCP should always set this for you, and when it doesn't, one should understand network masks and set it properly. I've written about how to set the mask and it's relation to broadcast address and the assigned IP address in other threads and don't have time to go into it again, but there is plenty of good information on the Internet that explains it in easy to understand terms (caution: not all of that information is correct).

Quote:

Originally Posted by rec9140

Default Gateway = your ROUTER's IP, which in the winworld is normaly 192.168.0.1, or 192.168.1.1 NOT 192.168.1.254 like *nix

I'm not really clear on what you are saying here. Usually the default setup for a router is one that ends in .1, but I've seen 192.168.0.1, 192.168.1,1, 192.168.2.1 and 10.0.0.1 used pretty commonly (Belkin likes to use 192.168.2.1) and I've seen some routers that don't default to the last digit being 1. I must be missing what you are trying to say about a xxx.xxx.xx.254 address, while you can move most routers there, wherever the router is it would be reached by the same address from Windows, Linux, Unix or any other OS that you are running.
09-26-2006, 02:19 AM
DaXiuyi

Re: Two hardware-related problems with Knoppix 5.0.1

Ok, thanks for that guys. Like I said, I'm a real newb :P I'll focus on the Net connection then and explain what I can (as you can see, might not be much)

I'm on an ADSL (512/128) connection using a Netcomm NB5Plus4 ADSL Modem and Router (Netcomm are an Australian manufacturer, so I've attached the link to it here). From the info I've pulled out of Win XP, my connection info is:
IP: 192.168.1.2, Subnet: 255.255.255.0, Default Gateway=DHCP=DNS=192.168.1.1, Physical Address: 00-11-D8-B5-37-7E (if that helps). Sorry for not putting up the info before, I thought it was some sort of security thing...

I tried to use the netcardconfig utility and when I allow DHCP it runs automatically and closes itself. The output from ifconfig is below:
knoppix@1[knoppix]$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:D8:B5:37:7E
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::211:d8ff:feb5:377e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2228 errors:0 dropped:0 overruns:0 frame:0
TX packets:2535 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2210393 (2.1 MiB) TX bytes:576835 (563.3 KiB)
Interrupt:22 Base address:0xa000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:900 (900.0 b) TX bytes:900 (900.0 b)

Umm, what does this mean? Hope this is what you're after...

When I run the ADSL config utility it detects eth0, then tries the first task (times out), then tries it again (times out again), returns an error message ("check your cable settings etc") and then closes itself.

Hope the information helps, and many thanks for your patience. Let me know if there's further stuff I need to post.

As for Firefox, when it first starts up an update window opens saying "checking for compatability updates to your Extensions" and it just hangs.

As for my printer, that's kind of frustrating. Now I know linuxprinting.org has linux drivers available for my printer, but if I were to download them, where would I put them so that once I boot Knoppix it detects them and works? Would anywhere work so that I can load them manually?

Many thanks.
09-26-2006, 03:04 AM
DaXiuyi

Re: Two hardware-related problems with Knoppix 5.0.1

Oh, and forgot one other piece of information. My network connection is through an SiS 900 PCI Fast Ethernet Adapter...

Hope that helps too.
09-26-2006, 03:46 AM
DaXiuyi

Re: Two hardware-related problems with Knoppix 5.0.1

Oh sorry, forgot to include the ipconfig /all output. This might make more sense to you...

Windows IP Configuration

Host Name . . . . . . . . . . . . : desktop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SiS 900 PCI Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-11-D8-B5-37-7E
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Tuesday, 26 September 2006 12:28:15 PM
Lease Expires . . . . . . . . . . : Tuesday, 26 September 2006 1:28:15 PM

HTH, and many thanks again.
09-26-2006, 04:31 AM
Harry Kuhman

DaXiuyi, I'm working on a horriably long technical post that will scare the hell out of you. Please stand by, I'll post as soon as I can.
09-26-2006, 04:59 AM
DaXiuyi

Harry, that's ok. If it has to be technical, then so be it. It's the only way I'll learn...

Thanks heaps for your time and patience.
09-26-2006, 05:35 AM
Harry Kuhman

Well DaXiuyi, what I can say is that the data that you have posted looks perfectly correct. And the fact that you can use Konquror as a browser supports that; it's able to access the Internet just fine. Which gets us back to Firefox, and pretty much right back to where we started, I'm still at a loss to know what that isn't working for you. I've rechecked and we are not in the HDD install forum and you have never indicated that you "installed" Knoppix, but as long as we're not fighting clasic networking problems that show up after such nonsense then we have a reeal puzzle here.

Of course, someone smarter than I may step in and know exactly what the issue is. We can hope that will happen. But while we're waiting and hoping, if you're interested in rolling up your sleves and getting your hands dirty in the guts of networking, I can tell you what my next step would be if this was my system. That next step (all I can think of at the moment) would be to actually look and see what is happening. In this case that's done by something called packet sniffing. This simply means looking at the blocks of data (packets) sent out and hopefully received when you try to access a web page. Looking at them byte by byte to see what parts of the packets look correct and what parts may look wrong, or what packets just never seem to happen and figure out why.

This may sound scarry (it sure as hell sounded complex the first time I tried to do it), but it's quite doable if you don't let it intimidate you. And there is a packet sniffing program called ethereal that you can use to do it. And guess what, ethereal just happens to be already included in Knoppix, so all you have to do is run it and, oh yea, interpret the captured data. I'll try to pass along enough info to make you dangerous.

Try this (what's the worst that can happen?): Boot Knoppix. Leave Konquror running. Run ethereal. I usually run it from the command prompt, but it's in the menus somewhere too. I also usually run it from the root account (sudo ethereal), which is a must if you are sniffing the wire and capturing traffic from other systems, but in your case you only need data to and from your own computer so you should not need root access if you don't want to use it. So with that info, start ethereal any way that you think suitable. I would open a terminal and type sudo ethereal or just open a root terminal and type ethereal.

Ethereal has a nice graphical interface, so a splash screen should show up, followed by a graphical window. The window will not be too scary at first, as there will not be much in it. But there will be an awful lot of options across the menu line. The place to start is with Capture and the second choice under that, options...

Now it's getting interesting, there will be lots of choices that may look like geek speak. At the top of the new window will be a drop down menu to pick which interface you want to sniff. These should include eth0, lo, and a pseudo interface. there may also be other interfaces here, depending on what networking hardware you have on your system. I expect and hope that you want eth0 (but make a note if there are any choices beyond the 3 that I mentioned). Leave the Link-layer setting below that set to ethernet. Don't check the Permiscious mode box in this case (although it will not matter if you do as long as you are doing this as root). Leave the "limit each packet" line unchecked. Leave the capure filter line blank, Leave the capture files section empty and don't put anything in the Stop after... section. To the right of these two I like to check the "update packets in real time" and then the "automatic scrolling" option that appears under it, but you can leave these unchecked if you want. Under name resolution check the first and third options, MAC and Transport and leave the middle option, network name, unchecked. I think this is what it will default to.

OK, that's the setup, now you're ready to capture packets. Say a prayer to your god and press the start button.

Within a few seconds you should see a window that shows how many packets of each type have been captured. It should start with no packets. But if you wait a few minutes you may see some background backets on the network, things like ARP packets. We don't really care about those though, and will have to ignore them in picking through the packets to understand this problem.

OK, remember that I said to leave Konquror open? Now would be a great time to switch back to Konquror. I would put a URL in the Konquror window and capture some packets. But don't capture a website like this one's packets, that would be way more traffic to pick through than you want to start with. I would suggest a nice simple clean website like http://checkip.dyndns.org/ . This site returns one simple string, no graphics, no frames, nothing complex, so it's a nice site to use for sniffing 101. Feel free to sniff other sites later, you'll learn a lot, but for now you just want to get basic packets worked out. Plug the above url into Konquror and let it load the page. When you have a string in the window, switch back to ethereal and hit the stop button to tell it to stop capturing packets. You should now see a window of all the packets that are involved in looking up that web page and getting you your line of text back.

OK, still with me? I'm not going to try to go into detail about what each packet is, but you should be able to see the packets from your computer that look up checkip.dyndns.org's IP from the URL, and then the packets that make the connection to the site and get the information. Scan through the list and see if you can't make sense of it. If you highlight any line you should see information about it in the middle third of the window and the raw packet byte by byte in the bottom window, but the most useful info is not the raw data but the human formatted representation of it in the top and middle windows. These will tell you key things like the source of the packet and the destination that it is being sent to. All of these packets (about 18 of them in this case) are sent and received to request and get this one line of text.

OK, now what? Same thing, but start Firefox and capture it's packets as it tries to access the same page. If it fails, as we expect, stop the sniffer and see what is different. Is Firefox trying to talk to a different address? Is it failing to look up the IP address? Is it getting the correct IP address? Is it making a connection to dyndns.org? Once you know what is going wrong you can try to determine why it is going wrong and then correct it.

One other thing that you might want to try is to bypass the DNS lookup and plug the correct IP address right into Firefox. If it can get to the website this way then you should suspect DNS, if it still can't get to the website then it's not a DNS issue, so you learn something either way. The IP address is 204.13.250.51 .

Good luck, let us know how it works out.
09-26-2006, 08:59 AM
DaXiuyi

Ok then everyone, here goes...

I think going from Harry's last sentence that there's a DNS problem. When I follow as suggested and try to access that check IP website while running ethereal, things work quite smoothly in Konqueror.

But when I put the URL into Firefox, the destination IP is weird: 1.0.0.0. However when I enter the IP address directly into Firefox, it connects fine, no problems at all. This extends to the URL - so if I've entered the IP first and it connects, FF always connects when the URL is subsequently entered.

So does is sound as though there is some sort of DNS error? OR should I provide more information from the ethereal output? If it is a DNS issue, is there anything I can do? I read somewhere that this is often an ISP problem. Should I talk to them then? Or would it be more a FF problem?

Hope I've provided the necessary information. Thanks heaps for all your help!

PS: Here are the troublesome parts of the FF loading. Unfortunately since I tried entering the IP address first, it now always connects :P so I tried a different website (The Sydney Morning Herald that demonstrates the problem:

No. Time Source Destination Protocol Info
1 0.000000 192.168.1.2 192.168.1.1 DNS Standard query AAAA www.smh.com.au

Frame 1 (74 bytes on wire, 74 bytes captured)
Ethernet II, Src: AsustekC_b5:37:7e (00:11:d8:b5:37:7e), Dst: XaviTech_48:f3:61 (00:01:38:48:f3:61)
Internet Protocol, Src: 192.168.1.2 (192.168.1.2), Dst: 192.168.1.1 (192.168.1.1)
User Datagram Protocol, Src Port: 32877 (32877), Dst Port: domain (53)
Domain Name System (query)

No. Time Source Destination Protocol Info
2 0.022463 192.168.1.1 192.168.1.2 DNS Standard query response CNAME www.smh.com.au.edgesuite.net CNAME a1758.g.akamai.net

Frame 2 (206 bytes on wire, 206 bytes captured)
Ethernet II, Src: XaviTech_48:f3:61 (00:01:38:48:f3:61), Dst: AsustekC_b5:37:7e (00:11:d8:b5:37:7e)
Internet Protocol, Src: 192.168.1.1 (192.168.1.1), Dst: 192.168.1.2 (192.168.1.2)
User Datagram Protocol, Src Port: domain (53), Dst Port: 32877 (32877)
Domain Name System (response)

No. Time Source Destination Protocol Info
3 0.024915 192.168.1.2 192.168.1.1 DNS Standard query A www.smh.com.au

Frame 3 (74 bytes on wire, 74 bytes captured)
Ethernet II, Src: AsustekC_b5:37:7e (00:11:d8:b5:37:7e), Dst: XaviTech_48:f3:61 (00:01:38:48:f3:61)
Internet Protocol, Src: 192.168.1.2 (192.168.1.2), Dst: 192.168.1.1 (192.168.1.1)
User Datagram Protocol, Src Port: 32877 (32877), Dst Port: domain (53)
Domain Name System (query)

No. Time Source Destination Protocol Info
4 0.026686 192.168.1.1 192.168.1.2 DNS Standard query response A 1.0.0.0

Frame 4 (90 bytes on wire, 90 bytes captured)
Ethernet II, Src: XaviTech_48:f3:61 (00:01:38:48:f3:61), Dst: AsustekC_b5:37:7e (00:11:d8:b5:37:7e)
Internet Protocol, Src: 192.168.1.1 (192.168.1.1), Dst: 192.168.1.2 (192.168.1.2)
User Datagram Protocol, Src Port: domain (53), Dst Port: 32877 (32877)
Domain Name System (response)

No. Time Source Destination Protocol Info
5 0.027516 192.168.1.2 1.0.0.0 TCP 57820 > www [SYN] Seq=0 Len=0 MSS=1460 TSV=316663 TSER=0 WS=7

Frame 5 (74 bytes on wire, 74 bytes captured)
Ethernet II, Src: AsustekC_b5:37:7e (00:11:d8:b5:37:7e), Dst: XaviTech_48:f3:61 (00:01:38:48:f3:61)
Internet Protocol, Src: 192.168.1.2 (192.168.1.2), Dst: 1.0.0.0 (1.0.0.0)
Transmission Control Protocol, Src Port: 57820 (57820), Dst Port: www (80), Seq: 0, Len: 0

No. Time Source Destination Protocol Info
6 3.028375 192.168.1.2 1.0.0.0 TCP 57820 > www [SYN] Seq=0 Len=0 MSS=1460 TSV=317413 TSER=0 WS=7

Frame 6 (74 bytes on wire, 74 bytes captured)
Ethernet II, Src: AsustekC_b5:37:7e (00:11:d8:b5:37:7e), Dst: XaviTech_48:f3:61 (00:01:38:48:f3:61)
Internet Protocol, Src: 192.168.1.2 (192.168.1.2), Dst: 1.0.0.0 (1.0.0.0)
Transmission Control Protocol, Src Port: 57820 (57820), Dst Port: www (80), Seq: 0, Len: 0

[2 more ARP packets]

No. Time Source Destination Protocol Info
9 9.028460 192.168.1.2 1.0.0.0 TCP 57820 > www [SYN] Seq=0 Len=0 MSS=1460 TSV=318913 TSER=0 WS=7

Frame 9 (74 bytes on wire, 74 bytes captured)
Ethernet II, Src: AsustekC_b5:37:7e (00:11:d8:b5:37:7e), Dst: XaviTech_48:f3:61 (00:01:38:48:f3:61)
Internet Protocol, Src: 192.168.1.2 (192.168.1.2), Dst: 1.0.0.0 (1.0.0.0)
Transmission Control Protocol, Src Port: 57820 (57820), Dst Port: www (80), Seq: 0, Len: 0

[Repeats]
09-26-2006, 11:18 AM
Harry Kuhman

Yea, this sounds DNS related, but it's still not making sense. It's the same DNS services fior Konquror and Firefox. And you say that now that you have does a sucessful access by IP address that the url now works??? That would imply that Firefox has made the URL to IP connection, which is the DNS lookup. So something else seems to be going wrong.

You say that you can't do the checkip.dyndns.org test any more since now Firefox is working fine on that url. But we are talking about Knoppix from the Live CD here right???? If you reboot does the problem not come back? If this fix survives a reboot of the CD then something very very very strange is going on in the router And, of course, if this isn't a Live dCD or DVD boot then you are just wasting my time, networking after Knoppix has been "installed" is known to be buggy.

I'll wait for your response, then I want to go off and contemplate this for a while. I seems like it could be something like a proxy setting in Firefox. But even a proxy setting should affect both access by URL and access by IP, so I just need to take some time to let these new facts sink in.
09-26-2006, 12:24 PM
rec9140

Goto a console and type cat /etc/resolv.conf and post the results.

You mention that Konqeror "seems to work fine" is Konq 100% and this just effects other browsers? Or can you reproduce it in Konq? With the EXACT same results.
09-26-2006, 12:59 PM
DaXiuyi

G'day everyone,

rec9140, the output is below:

knoppix@2[knoppix]$ cat /etc/resolv.conf
nameserver 192.168.1.1

Here's my checklist of what I do and what happens [have rebooted Knoppix from the Live-CD]:

1. Go to http://checkip.dyndns.org/ in Konq: Opens fine, no problems at all.
2. Go to http://checkip.dyndns.org/ in FF: After opening FF and trying (without success) for a compatibility update, it works.
3. Go to http://www.smh.com.au in FF: Hangs, with the following ethereal output:

No. Time Source Destination Protocol Info
1 0.000000 192.168.1.2 1.0.0.0 TCP 54784 > www [SYN] Seq=0 Len=0 MSS=1460 TSV=168381 TSER=0 WS=7

Frame 1 (74 bytes on wire, 74 bytes captured)
Ethernet II, Src: AsustekC_b5:37:7e (00:11:d8:b5:37:7e), Dst: XaviTech_48:f3:61 (00:01:38:48:f3:61)
Internet Protocol, Src: 192.168.1.2 (192.168.1.2), Dst: 1.0.0.0 (1.0.0.0)
Transmission Control Protocol, Src Port: 54784 (54784), Dst Port: www (80), Seq: 0, Len: 0

No. Time Source Destination Protocol Info
2 2.999158 192.168.1.2 1.0.0.0 TCP 54784 > www [SYN] Seq=0 Len=0 MSS=1460 TSV=169131 TSER=0 WS=7

Frame 2 (74 bytes on wire, 74 bytes captured)
Ethernet II, Src: AsustekC_b5:37:7e (00:11:d8:b5:37:7e), Dst: XaviTech_48:f3:61 (00:01:38:48:f3:61)
Internet Protocol, Src: 192.168.1.2 (192.168.1.2), Dst: 1.0.0.0 (1.0.0.0)
Transmission Control Protocol, Src Port: 54784 (54784), Dst Port: www (80), Seq: 0, Len: 0

No. Time Source Destination Protocol Info
3 4.999160 AsustekC_b5:37:7e XaviTech_48:f3:61 ARP Who has 192.168.1.1? Tell 192.168.1.2

Frame 3 (42 bytes on wire, 42 bytes captured)
Ethernet II, Src: AsustekC_b5:37:7e (00:11:d8:b5:37:7e), Dst: XaviTech_48:f3:61 (00:01:38:48:f3:61)
Address Resolution Protocol (request)

No. Time Source Destination Protocol Info
4 4.999475 XaviTech_48:f3:61 AsustekC_b5:37:7e ARP 192.168.1.1 is at 00:01:38:48:f3:61

Frame 4 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: XaviTech_48:f3:61 (00:01:38:48:f3:61), Dst: AsustekC_b5:37:7e (00:11:d8:b5:37:7e)
Address Resolution Protocol (reply)

No. Time Source Destination Protocol Info
5 8.999245 192.168.1.2 1.0.0.0 TCP 54784 > www [SYN] Seq=0 Len=0 MSS=1460 TSV=170631 TSER=0 WS=7

Frame 5 (74 bytes on wire, 74 bytes captured)
Ethernet II, Src: AsustekC_b5:37:7e (00:11:d8:b5:37:7e), Dst: XaviTech_48:f3:61 (00:01:38:48:f3:61)
Internet Protocol, Src: 192.168.1.2 (192.168.1.2), Dst: 1.0.0.0 (1.0.0.0)
Transmission Control Protocol, Src Port: 54784 (54784), Dst Port: www (80), Seq: 0, Len: 0

No. Time Source Destination Protocol Info
6 20.999416 192.168.1.2 1.0.0.0 TCP 54784 > www [SYN] Seq=0 Len=0 MSS=1460 TSV=173631 TSER=0 WS=7

[Repeats this TCP packet twice more]

[Repeats ARP packets as before]

I even tried using Elinks and entering the Check IP address there, no luck either... just hangs "making connection." And have only used the Live-CD (wouldn't even know how to install Knoppix to my hard drive :P)

So it appears that every other browser is playing up... except for Konqueror!

Hope this helps guys and it hasn't made life even more confusing for you!
09-26-2006, 04:19 PM
rec9140

Quote:

Originally Posted by DaXiuyi

rec9140, the output is below:

knoppix@2[knoppix]$ cat /etc/resolv.conf
nameserver 192.168.1.1

goto a console, swith to super user mode via su

something along

rec9140@rickscne:~$ su
Password:
root@rickscne:/home/rec9140# joe /etc/resolv.conf

You can use Kate or KWrite too which ever your most familar with, kwrite|kate /etc/resolv.conf would do the same thing. joe is just a simple text based editor and much easier than vi or emacs (awful programs!)

Edit resolv.conf to be:
nameserver 208.67.222.222

Save the file.

See if the problems persists.

Your router may not like acting as DNS proxy, some SOHO types just don't do it well or at all. Which is perplexing as Konq works but others have an issue with address resolution...hmmmm..... live cd......hmmm even more strange....

I take it that you zero issues with visting sites as the router is configured if used under winvirus, at least thats the way I read things, correct?
09-27-2006, 05:42 AM
DaXiuyi

No, using Win XP I get no problems at all.

Well, I edited the file as you said, rec9140, and now everything works beautifully :) All other programs (FF, Gaim etc) connect and work fine :D

Thanks heaps for all your help guys. I'm still scratching my head as to why it suddenly works, but thank you so much all the same...

Now that I know I can connect to the Net in Linux now, and that with a proper dist'n I can load the drivers for my printer, I think I'll be switching to some sort of *nix distribution before long ^^

Thanks again
09-27-2006, 06:40 AM
Jacky

Hi,

I have been following this in the background, and I also know of some previous posters on this forum who have encountered a similar problem where Konqueror works but Firefox and other browsers do not. From what has been described and how it was solved, I now think that what we are seeing is something called the IPv6 problem which has been discussed on other forums. IPv6 is the new form of internet addressing which is slowly being introduced but which is not supported everywhere yet. This problem occurs when a DNS does not properly support IPv6. The DNS then times out or returns an error when a browser sends out a IPv6 request because it does not know what to do with it.

I found some details of the problem here: http://www.cisco.com/web/about/ac123...e_servers.html
and some discussion here: http://www.linuxforums.org/forum/lin...eror-does.html

The solution given for Firefox in the above link is to disable IPv6, or as, for DaXiuYi did, simply change to a different DNS.

The evidence for my hunch is when I did an ethereal capture of Konqueror and Firefox -- they behave differently when making DNS requests. Konqueror sends out a Type A (IPv4) request first followed by a Type AAAA request (IPv6). Firefox and Elink sends out a Type AAAA request first, and then a Type A request. So in the case of Firefox and Elink, it could be possible that when the DNS receives a Type AAAA request, it does not know what to do, and so times out and never gets round to handling the Type A request. On the other hand, Konqueror sends out a Type A request to the DNS and gets a good response, so it doesn't matter whether the Type AAAA request gets a response or not.

I can't completely test this hunch until I get the IP of a DNS which we know for sure is faulty and does not support IPv6 (for example, DaXiuYi, you might know which DNS your ISP has provided and tell it to me). I will then set my system to these faulty DNS and see if I get a problem.

Anyway I am glad this episode happened because in the past I have read of other posters having this problem and we all puzzled over it and could not understand what was wrong. Now at least we are solving the puzzle.
09-27-2006, 07:23 AM
Harry Kuhman

Jacky has a very interesting theory there. DaXiuyi, one good test of this theory would be to change the DNS setting in your router to the one that works, and then see if Knoppix works fine from a cold boot of the CD with no editing. Unfortunately, I've read through the router manual and as far as I can see you don't get an option to change this setting in the router when using PPPoE or PPPoA, only when using static settings. However, you may want to look, I may have overlooked something, or you may have newer firmware than the manual documants that allows this. You could even check if you are running the current firmware and flash your router if you are not.

Many routers do allow the DNS server to be changed when running PPPoE/PPPoA, although the one that I'm currently running doesn't allow it either. I never liked that about my router, now that we see a potential serious problem that it can lead to I like it even less. If you do figure out how to change the DNS server used in your router settings please let us know the results.
09-27-2006, 11:00 AM
Jacky

I think my router does allow DNS settings to be changed. What I need now are DNS addresses which have been known to cause people trouble.

DaXiuYi, if you can tell me what DNS settings are on your router (the DNS settings which your router was using when you had the Firefox problems), I will set my router to use your DNS settings. If this causes my Firefox to fail, then we shall know.
09-27-2006, 12:00 PM
rec9140

Quote:

Originally Posted by Jacky

I have been following this in the background, and I also know of some previous posters on this forum who have encountered a similar problem where Konqueror works but Firefox and other browsers do not. From what has been described and how it was solved, I now think that what we are seeing is something called the IPv6 problem which has been discussed on other forums. IPv6 is the new form of internet addressing which is slowly being introduced but which is not supported everywhere yet. This problem occurs when a DNS does not properly support IPv6. The DNS then times out or returns an error when a browser sends out a IPv6 request because it does not know what to do with it.

I found some details of the problem here: http://www.cisco.com/web/about/ac123...e_servers.html
and some discussion here: http://www.linuxforums.org/forum/lin...eror-does.html

The solution given for Firefox in the above link is to disable IPv6, or as, for DaXiuYi did, simply change to a different DNS.

The evidence for my hunch is when I did an ethereal capture of Konqueror and Firefox -- they behave differently when making DNS requests. Konqueror sends out a Type A (IPv4) request first followed by a Type AAAA request (IPv6). Firefox and Elink sends out a Type AAAA request first, and then a Type A request. So in the case of Firefox and Elink, it could be possible that when the DNS receives a Type AAAA request, it does not know what to do, and so times out and never gets round to handling the Type A request. On the other hand, Konqueror sends out a Type A request to the DNS and gets a good response, so it doesn't matter whether the Type AAAA request gets a response or not.

This is interesting....hmmmm... OK.. I was always wondering what kind of issues are going to come up in the IPV4 to IPV6 mess.
09-30-2006, 01:59 AM
DaXiuyi

Umm, Ok Jacky, here's what I can find.

Protocol: PPPoA LLC
VPI/VCI: 8/35
DNS 1: 220.233.0.4
DNS 2: 220.233.0.3

Hope that helps. Let me know if there's any more info you need.
09-30-2006, 03:19 AM
Jacky

Thanks DaXiuYi, that's just what I needed.

Unfortunately, friends, my experiments with these DNS IPs contradict my theory.

220.233.0.4 and 220.233.0.3 all behave correctly as DNS. As far as I can see, there's nothing wrong with them. They take a Type AAAA query, don't process it, the application then falls back quickly to a Type A query which the DNS then correctly responds by supplying the IP. No error, no time out, no problems.

I have tried various scenarios -- set the above DNS into my router, and/or in resolv.conf, set 192.168.1.1 into resolv.conf and use the router to proxy a DNS call to these 2 DNS etc. Everytime Firefox and Konqueror have worked. I just could not get anything to go wrong!

By searching for "only Konqueror works" on Google, I find there are people on Mepis, Ubuntu and Suse etc who have experienced this problem. They have all come up with various fixes, but nobody seems to know what the root of the problem is.

Well, DaXiuYi has fixed the problem, but we still don't know why there was the problem in the first place.........The only clue left is that Konqueror handles a DNS query differently from Firefox. I think the problem is still about DNS, and may be the way some routers proxy DNS calls. But we will have to wait until the next forum-user reports and similar problem........

DaXiuYi, are you still experiencing problems and still have to edit resolv.conf everytime you reboot? If so, did you try out Harry's suggestion? Change the DNS setting in your router to 208.67.222.222 (if your router let's you, you will probably put the setting in something like "Static DNS setting"). Save the settings, reboot and see if Firefox works.
10-01-2006, 10:47 AM
DaXiuyi

Quote:

DaXiuYi, are you still experiencing problems and still have to edit resolv.conf everytime you reboot?

Yes.
[/quote]
If so, did you try out Harry's suggestion? Change the DNS setting in your router to 208.67.222.222 (if your router let's you, you will probably put the setting in something like "Static DNS setting"). Save the settings, reboot and see if Firefox works.

Quote:

Umm, I'm not sure if I can. When I try, the status light stays red, implying that it doesn't work :S I figure it's safer just to leave things as they are...

Will keep trying and let you know.