internet connection blues!

[muppet]

Hello,
I've been attempting to connect to the t'internet for ages, first with a usb adsl modem, with no success, and now i've got a router i thought everything would be simpler, but i'm still struggling. The router is a Voyager 220V which was given as a freebie when i upgraded my isp account. It works fine under XP but i'm confused 'cos when i look at the set-up it says the protocol is PPPOA, (which after reading many pages on this forum over the lastr few weeks i expected to be PPPOE) even though i'm not sure i should be using PPPOE or not

I'm running knoppix live from a DVD (V5.01) and have configured eth0 (i think) when i run ifconfig eth0 is listed and is given an ip of 192.168.1.1 (and get a response when i ping it) so i think its working, so the problem is getting to the WAN. When i run the DSL config script from the knoppix menu it tells me that it could not find an ethernet connection!

On XP when i look at config page of the router and try to configure a new connection i get an error message saying that because the router was supplied by the isp, i can only use it for the isp, which is fine cos i do, but with unix. Is this a ball-breaker or not?

If anyone can give me the benefit of their wisdom i would be very gratefull.

Thanx

[Harry Kuhman]

PPPoA is used in some countries instead of PPPoE. Routers generally support the protocol used in the coutry that are distributed in, so this should be OK. You're in the UK and I expect PPPoA is not a problem fior you as it would be in the USA.

You say you have a usb modem, but they don't work with external routers, so I hope that you have a modem that supports either usb or ethernet, and I expect that you do, otherwise you couldn't connect the router to the modem.

Some ADSL modems that have both usb and ethernet (such as a popular Westel modem) already have a router built in. In that case you don't want to use a second router, you want to connect your system by ethernet directly to the modem/router and use that. Did your xp system need pppoea/pppoe software before you added the router (as it would if there was no router built in the mode)? What make and model modem is it? Have you researched to determine if it has a built in router?

This message about the router only working with the ISP is troubling, it may be that the ISP is playing games that are complicating the issue. In general Unix is not the issue, nor is Linux, which you are using. Linux is not Unix. You should not be running a DSL configuration script though, the router takes care of all DSL issues, you should just automatically be handshaking with the router at Knoppix boot, getting your setup info by DHCP at boot andbe on the Internet as the boot finishes.

[rec9140]

I'm running knoppix live from a DVD (V5.01) and have configured eth0 (i think) when i run ifconfig eth0 is listed and is given an ip of 192.168.1.1 (and get a response when i ping it) so i think its working, so the problem is getting to the WAN. When i run the DSL config script from the knoppix menu it tells me that it could not find an ethernet connection!

Boot the CD/DVD and then hit:

Penquin Icon, Configure Network/Internet then, NETWORK CARD configuration. Dont use the DSL/PPPoE script your not running the PPOE on your computer, thats the routers job and for you ISP its using PPPoA.

When the script runs it will ask if you want to use DHCP broadcast. Hit yes

See if the router supplies an IP etc.. and if the script closes with out an error. Then run a Konqueror sesssion and just try to go to the Knopper site or any other site. Continue on if you don't have working internet, otherwise stop here.

Boot under winviurs, and do a START, RUN, type CMD (hit return) then at the C:\> prompt type ipconfig /all (hit enter)

Write down: IP address, DNS servers, default gateway IP addresses.

If the netcard script under Knoppix doesn't work RERUN the same Network Card config, Answer NO to DHCP broadcast Then answer the questions using the values from the winvirus session. See if that brings your network up.

Try these first, and post back results, and worst case if it comes to it you may have to edit some things by hand.

[muppet]

Try these first, and post back results, and worst case if it comes to it you may have to edit some things by hand.

okay,
i ran network card config first with DHCP, and got a FAILED response, so as suggested i re-ran it without DHCP and entered the ip addresses gained from ipconfig running XP.
(I used the default responses for 'Broadcast address for eth0' (192.168.1.255) and 'Nameserver' (192.168.1.254)

i tried to connect to the internet but no joy.

ifconfig gave the following;

eth0 Link encap:UNSPEC HWaddr 00-11-06-00-00-00-38-1A-00-00-00-00-00-00-00-00
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:36 errors:6 dropped:6 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:1296 (1.2 KiB)

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:51 errors:0 dropped:0 overruns:0 frame:0
TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3923 (3.8 KiB) TX bytes:3923 (3.8 KiB)


i tried pinging 216.32.81.146 but only got a response from 192.168.1.2 and 'Destination Host is unreachable'

Thanks for all your help
Muppet.

[Harry Kuhman]

i ran network card config first with DHCP, and got a FAILED response, so as suggested i re-ran it without DHCP and entered the ip addresses gained from ipconfig running XP.
(I used the default responses for 'Broadcast address for eth0' (192.168.1.255) and 'Nameserver' (192.168.1.254)

i tried to connect to the internet but no joy.
I'm not sure why you used that .254 address as the nameserver, try 192.168.1.1 (assuming that 192.168.1.x is the proper subnet). What IP address did you assign (that's pretty important here and you didn't say).



ifconfig gave the following;

eth0 Link encap:UNSPEC HWaddr 00-11-06-00-00-00-38-1A-00-00-00-00-00-00-00-00
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:36 errors:6 dropped:6 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:1296 (1.2 KiB)

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:51 errors:0 dropped:0 overruns:0 frame:0
TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3923 (3.8 KiB) TX bytes:3923 (3.8 KiB)

Did it give this before or after you did the manual netcardconfig? If before then things are looking pretty good, just try changing that nameserver. And I don't know for sure that your router will behave as a nameserver, although most modern ones will. You may be able to get a DNS server address from your ISP to use here, or you likely can go into the router setup and see what it has been told to use for a DNS server and use that yourself, cutting out the middleman.


i tried pinging 216.32.81.146 but only got a response from 192.168.1.2 and 'Destination Host is unreachable'
This isn't good. You didn't tell us what IP you assigned but I'm guessing it was 192.168.1.2, and if so then that is just your local computer saying that. Since a ping of an IP address (as opposed to a URL) doesn't use a nameserver at all then something is pretty wrong here. Once again I think it's that 254 you used but that would only be the case if you gave 192.168.1.254 as a default gateway too. If changing the 254 doesn't fix things let us know about how a ping works to the router at 192.168.1.1. And ping anything and everything else you can think of to ping and see if you can pin down where the problem is.

[rec9140]

i ran network card config first with DHCP, and got a FAILED response, so as suggested i re-ran it without DHCP and entered the ip addresses gained from ipconfig running XP.
(I used the default responses for 'Broadcast address for eth0' (192.168.1.255) and 'Nameserver' (192.168.1.254)

i tried pinging 216.32.81.146 but only got a response from 192.168.1.2 and 'Destination Host is unreachable'



Rerun your netcard config:

Use DHCP - NO

IP Address: 192.168.1.2

Netmask : 255.255.255.0

Broadcast: 192.168.1.255

Nameserver: 208.67.222.222

Default Gateway: 192.168.1.1

Your router should be IP 192.168.1.1 depending on the maker if you put http://192.168.1.1 into Konqueror it should ask you for a user name and password in some manner to access the setup of your router.

IF your ROUTER is a DIFFERNET IP than 192.168.1.1 then your default gateway MUST MATCH THIS IP.

Also if your router is 192.168.0.x see that 0 in the next to last section.... Thats important change to the following:


Use DHCP - NO

IP Address: 192.168.0.2

Netmask : 255.255.255.0

Broadcast: 192.168.0.255

Nameserver: 208.67.222.222

Default Gateway: 192.168.0.1

If you ping an IP it should work unless you have another issue.

[muppet]

Thanks for all your help but i re-ran the netcard config as above but with no better results.
Afterwards ifconfig gave the following;

eth0 Link encap:UNSPEC HWaddr 00-11-06-00-00-00-38-1A-00-00-00-00-00-00-00-00
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:30 errors:2 dropped:2 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:1080 (1.0 KiB)

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:48 errors:0 dropped:0 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3672 (3.5 KiB) TX bytes:3672 (3.5 KiB)


i then tried to ping to the internet and this gave the following;

PING 216.32.81.146 (216.32.81.146) 56(84) bytes of data.
From 192.168.1.2 icmp_seq=1 Destination Host Unreachable
From 192.168.1.2 icmp_seq=2 Destination Host Unreachable
From 192.168.1.2 icmp_seq=3 Destination Host Unreachable
From 192.168.1.2 icmp_seq=4 Destination Host Unreachable
From 192.168.1.2 icmp_seq=5 Destination Host Unreachable
From 192.168.1.2 icmp_seq=6 Destination Host Unreachable
From 192.168.1.2 icmp_seq=7 Destination Host Unreachable
From 192.168.1.2 icmp_seq=8 Destination Host Unreachable
From 192.168.1.2 icmp_seq=9 Destination Host Unreachable

--- 216.32.81.146 ping statistics ---
12 packets transmitted, 0 received, +9 errors, 100% packet loss, time 11076ms
, pipe 3


also i couldnt get access to the router via Konquerer using http://192.168.1.1


i've had a look while running xp and ipconfig gives;

Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : home
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

Other info i've got from the router is :



LAN IP Address 192.168.1.1
Default Gateway 217.47.67.142
Primary DNS Server 194.74.65.69
Secondary DNS Server 62.6.40.178

Firmware Version 3.01z
Boot Loader Version 1.0.37-21.6.11
ADSL Driver Version A2pB018c1.d16d
Ethernet MAC Address 00:16:E3:64:79:12

i also tried putting this gateway ip when running knoppix with no better results.

I'm sure i should be able to get to the internet while running knoppix, as all the lights on the router indicates that the connection is on.

If theres any other info i can supply to help solve my problems please let me know, otherwise i'm a bit stuck!

Thanks in advance.

[muppet]

Sorry,
i forgot to add the contents of my routing table from XP (if its any use)


Destination Netmask Gateway Interface Metric
217.47.67.142 255.255.255. 255 0.0.0.0 pppoa_0_38_1 0
192.168.1.0 255.255.255.0 0.0.0.0 br0 0
0.0.0.0 0.0.0.0 217.47.67.142 pppoa_0_38_1 0

[Harry Kuhman]

The signal to noise ration here is not good.

Here is the info that I request to try to assist. If you wish, fell free to use the bold editing feature (first one in the line above the edit window) to call attention to things, or the "Code" block to block off output that you pasted in, but please don't use enlarged fonts to call attention to parts of the post.

1) The make and model of your modem. If you have checked and determined if it has a router built in, please let us know. If you have a link to an on-line copy of the manual for it please post that.

2) Make and model of your router. If you have a link to a manual for the router please post it. I'm assuming that you are still using the router, if not please let us know.

3) From Windows, the output of the command "ipconfig".

4) From Knoppix, the output of the command "ifconfig" after booting when attached to the network but before doing any netcardconfig.

5) Exactly what you are typing in for each question during netcardconfig.

6) The output of "ifconfig" after doing a netcardconfig in Knoppix.

[muppet]

Harry,
Thanks for any help you can give, and sorry for the big text!

Answers,

1) There is no seperate modem, the router is attached to the pc via an ethernet cable, and the router is connected to the internet via an ADSL enabled phone line.

2) The router is a voyager 220V details can be found at
www.shop.bt.com/invt/car116

3) ipconfig under windows gives;

Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : home
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

4) Before netcardconfig while running Knoppix, ifconfig gives;

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:48 errors:0 dropped:0 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3672 (3.5 KiB) TX bytes:3672 (3.5 KiB)

5) When running netcardconfig i gave the following responses;


Use DHCP - NO

IP Address: 192.168.1.2

Netmask : 255.255.255.0

Broadcast: 192.168.1.255

Default Gateway: 192.168.1.1

Nameserver: 208.67.222.222



6) After netcardconfig ifconfig gives the following;

eth0 Link encap:UNSPEC HWaddr 00-11-06-00-00-00-38-1A-00-00-00-00-00-00-00-00
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:30 errors:2 dropped:2 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:1080 (1.0 KiB)

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:48 errors:0 dropped:0 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3672 (3.5 KiB) TX bytes:3672 (3.5 KiB)

Hope this helps you with my problem and Thanks again.

[Harry Kuhman]

OK, now I at least have a better understanding of the setup.

1 and 2 - I didn't understard that where you said that they gave you a router that it was actually a modem and router and that you had put aside your old modem. So this thakes several potential problems away.

I've looked over the link you gave, still can't find a manual for the router. Interesting that they set it up so it could only work on their system. I note that they say the NAT feature can be disabled, but it isn't in your case, answer 3 confirms that.

Just an observation, you only seem to get one ethernet port, so I suggest using a switch (or a hub) if you want to build a local network or give more than one computer access to the Internet at once.

3 - this looks good.

4 - hmm, the eth0 didn't show up at all here, I expected that it would, but as long as you don't get an error when you try to manually do a netcardconfig I'm not too concerned about that.

5 - Without knowing why DHCP is failing, doing the manual netcardconfig seem the next logical step. All of your input looks good. I don't know if that Nameserver (DNS) is valid, but I'll assume it is. If it's not them the symptom would be that you could access sites by the IP address but not by their URL.

OK, I have one suggested test to try at this point. It may sound strange, it should. But try the same thing using an IP address different from 192.168.1.2 for the computer's IP address. I know that the computer is being assigned that address in Windows, but there's an extremely slim chance that you could have a dhcp lease problem with that address (Which in no way explains why automatic DHCP is failing and really doesn't make any sense unless you know about a problem another user had about two years ago). But try putting in 192.168.1.10 or 192.168.1.100 and see if that works. I don't really have a lot of hope that this is going to fix anything, but I think it would be a shame not to try and then find out later that it was the problem.

And just to be real clear, when you did the ipconfig under windows, that was done on the same computer that we are trying to get Knoppix running on, right? We are not talking about two different computers here, are we?

6 - Well, at this point the data here looks right, although I want to fire up Linux and look at my interface's ifconfig to check a few things. Your hardware address sure has a lot of 00's in it, which is giving me some doubt. ifconfig is telling us that you're sending packets out but never getting anything back. And it doesn't seem to get any background chatter from the router, also strange. This leads me to a question that I should have asked but missed, and I don't think you've posted the answer yet. Just what is the NIC hardware that you're using to talk to the router? I'm wondering if it's some fancy NIC chipset that Knoppix isn't supporting yet. If it was I would have expected the manual netcardconfig to give an error, but it's the most obvious thing to ask at this point.

And there is only one ethernet port, right? You don't have a NIC card installed but also a NIC on your motherboard, do you? If you did it would be posiable that you are configuring eth0 but need to talk to eth1.

Assuming that you're running a normal supported 10/100 NIC that Knoppix should recognize, we need to determine just why the etho interface seems to be talking but never getting a response. To know that it would be helpful to see exactly what it's saying. There is a tool that will let us do just that, ethereal. I wrote up another entry on using it recently in this thread (http://www.knoppix.net/forum/viewtopic.php?t=25578). You might want to read that thread through and then try capturing packets on the interface. We'll learn a lot by seeing if it's trying to access 192.168.1.1 when it should, and otherwise picking apart the packets to see how they differ from the windows packets that do get a response.

I would start ethereal even before trying to do a netcardconfig. Even the captured packets from answering yes to the dhcp question should tell us a lot. The packets for trying to access 192.168.1.1 with Konquror after doing the manual netcardconfig may tell us even more.

Hope that has given you more to think about and that maybe somewhere here I've stumbled across the answer.

[muppet]

Thanks for all that Harry,
Yes there is only one computer and as far as i know there is only one ethernet (on the motherboard) (i know i should know if i've put in another network card in my own computer, but i cant remember if i did when i built this one, Ill check when i get home)

I'll have a go with ethereal and changing the ip adresses and let you know how i get on.
Thanks again for your help.

[Harry Kuhman]

Ok thanks. You might want to post what that motherboard is and what ethernet chipset it uses if you can find it. Would be worth trying to research how well it is supported under Linux and under Knoppix too.

[muppet]

Back again!
first things first.
motherboard

Motherboard Properties:
Motherboard ID 63-0201-000010-00101111-091605-945PL$A0355000_BIOS DATE: 09/16/05 11:07:08 VER: 08.00.10
Motherboard Name ASUS P5PL2

Front Side Bus Properties:
Bus Type Intel NetBurst
Bus Width 64-bit
Real Clock 200 MHz (QDR)
Effective Clock 800 MHz
Bandwidth 6400 MB/s

Memory Bus Properties:
Bus Type Dual DDR2 SDRAM
Bus Width 128-bit
Real Clock 267 MHz (DDR)
Effective Clock 533 MHz
Bandwidth 8533 MB/s

Chipset Bus Properties:
Bus Type Intel Direct Media Interface
NIC; (only one!)


Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC ]

Network Adapter Properties:
Network Adapter Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC
Interface Type Gigabit Ethernet
Hardware Address 00-15-F2-08-0F-ED
Connection Name Local Area Connection
Connection Speed 100 Mbps
MTU 1500 bytes
DHCP Lease Obtained 30/09/2006 12:33:52
DHCP Lease Expires 01/10/2006 12:33:52
Bytes Received 49832832 (47.5 MB)
Bytes Sent 2858125 (2.7 MB)

Network Adapter Addresses:
IP / Subnet Mask 192.168.1.2 / 255.255.255.0
Gateway 192.168.1.1
DHCP 192.168.1.1
DNS 192.168.1.1



ok,
i booted up knoppixand tried using other ip addresses for the computers ip address. when i then tried to ping the outside world i simply got the message network not found. One thing i did notice when knoppix was booting up was after it found eth0,it brought up the message "DHCP broadcasting for ip (backgrounding)" (dont know if thats pertinent or not)

so i then re-booted knoppix and started ethereal (as root) before i ran netcardconfig. ethereal could not find eth0 at all, so i quit the application and ran netcardconfig. This time ethereal found eth0 so i started the capture process. Nothing happened until i tried to ping to ping 216.32.81.146. ethereal gave a few lines of the following;

source destination protocol info
(blank) (blank) ARP (malformed packet)
at this point the only thing i could think to do was to try and reconfigure my NIC to use DHCP, this gave a few lines of the following;

source destination protocol info
0.0.0.0 255.255.255.255 DHCP DHCP Discovery Transaction ID 0x69140600
ethereal then quit itself complaining that it could not find eth0

So i'm not sure where to go from here, any suggestions?

Thanks in advance.

[Harry Kuhman]

Am I to understand that the network interface is on a PCI-E card and not on the motherboard? That seems strange, particularly for a recent Asus board. I'm thinking that maybe the interface is on the motherboard, even though you called it PCI-E above (maybe a terminology that Asus uses). Obviously with that BIOS date it's a pretty new motherboard. While Knoppix is doing better in supporting 10/100/1000 NICS, it might be that it's just too new to be supported yet, even though it's being recognized. That's just speculation, but is seems to fit with everything that you are reporting.

My first though is that it seems from your previous posts that you very well may have another NIC available. If so I would try adding that NIC, hopefully a simple 10/100 NIC on a PCI interface. If there is a BIOS feature or motherboard jumper to disable the other NIC and you want to really keep things simple I would disable it, and if it is a PCI-E card I would remove it. You should still be able to get the add-in NIC working if you don't, but this would prevent problems differentiating between eth0 and eth1, and help be sure that DHCP at boot time tried the NIC that you wanted it to use. Of course, feel free to try experimenting without disabling or removing the 10/100/1000 NIC if you wish.

I expect that that will resolve it for you. Hopefully a future release of Knoppix will suport your newer hardware.

[muppet]

Thanks Harry for all your help.
you are absolutely right. I've installed my old nic card and am now writing this running linux.
Thanks again, no doubt i'll return when (not if)_ i need help !