Re: Fwd: Billion 7800N
On 31/08/2011, D G Teed donald.t...@gmail.com wrote: On Tue, Aug 30, 2011 at 11:16 AM, Andrew McGlashan I cannot believe this thread is still going -- it is way beyond funny now it's ludicrous to say the least Your Ethernet device is broken and if it is not broken, then get someone else to fix this problem for you as you are only going around in circles and getting nowhere. I should add, your earlier suggestion to boot from a Live CD is a very good one. It would provide a very quick method to determine if the hardware or the OS install was faulty. If the Live CD works to get on the 'net, then the notebook hardware is fine and the install/configuration is botched. Yes, I wanted to try this earlier, but had no way to download an iso. But, as things have turned out, there's no longer a problem. As the wheezy weekly build netinstall couldn't seem to see the XP partition on the PC, I was forced to install Debian on the laptop. I did an expert install and besides not selecting kernel options like remote install through ssh, I also foregoed ppp and pppd-udeb installs. Dhcp picked up the router during network detection automagically and I'm posting this from the laptop on a wheezy install on a stable, consistent connection. My humble thanks to all for the time and trouble they've put in. It has been much appreciated. Regards, Weaver. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion. -- 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/CAPeXKO2Po6A3iQ+s9MM6zL6+7bdVgKHVK74_=Ogs=2yoadt...@mail.gmail.com
Re: Fwd: Billion 7800N
On Wed, 24 Aug 2011 09:54:48 +1000, Heddle Weaver wrote: On 22 August 2011 22:02, Camaleón noela...@gmail.com wrote: I need pppd of course, but not ppp. Can you explain why you need pppd? :-? Well, I was under the impression that with ppp over ethernet, the daemon would be required. I'm probably wrong. That's alright. It makes other people feel good. :-) With an ethernet router you normally don't need to manually establish a pppd connection, this facility is embedded within the router itself and your ISP is in charge of setting this so the user has to do nothing. At least this is the common setup in Spain and guess that also is in Europe. Can you point me to somewhere on the Internet where I can see what are your ISP connection settings? I'll bring them into town and post them on the next trip, probably tomorrow. This is getting very interesting, like a mystery novel :-) I've got severe health problems, so I have access to the computers of a specialist Disabled Job Network organisation. Ooops, sorry to hear that ;-( They somewhat draw the line before downloading an iso and burning it to disc, though. This is also why I haven't got back to the list over the last couple of days. Stretched out on a bed with a definition of headaches that engenders a death-wish, which I would indulge in if I could move. Luckily the situation takes over completely and I'm incapable of moving. Don't worry, take the time you need and recover soon so you can return to the battle! Yes, having DHCP on is the most common nowadays. Anyway, having a static IP would have required to manually set the gateway. Well, there could be something in that. As I recall, this ISP relegates static and not dynamic addresses. Hum... remmeber that there are two differenet set of IPs: local (LAN) and remote (WAN). Usually, ISPs give the users dynamic IP addressing for WAN and also enable the DHCP server of the router for the LAN so computer clients can easily reach the LAN part. Our interest here are the setting options for the LAN part. Well, I'm actually getting an IP address on the Linux laptop, so DHCP must be active. If your ethernet device has an IP assigned that means the router is able to communicate with your laptop and so you should also be able to access to the router or at least get a response from wget different than a timeout :-? I believe the contact between the laptop and modem is inconsistent and think this is the source of the majority of disconnections. I think there is more than one aspect to this problem. Testing with an additional ethernet card (USB to RJ-45) would be the best thing to discard something wrong with your current adapter. Is not very usual to have ethernet hardware issues but who knows... weird things can happen. I'll post that when I get back in also, although I'm sure I've done it already somewhere. I recall my IP, the peer's IP, DNS primary and secondary, amongst other things, but I'll get proof positive. Regards and thanks, Waiting anxiously for the feedback :-) O.K., here it is, but it might be a bit of an over-dose: dhcp last modified May 23rd, and dhcp3, last modified April 29th, both installed and appear active ~ Primary server: 203.12.160.35 Secondary server: 203.12.160.36 These are both present and correct in 'resolve.conf' ~~ This is interesting because it states 'existing default route through ppp3': (...) Where would I go to delete those? Okay, start by disabling pppd service at all, you don't need it unless your ISP has told you otherwise. Stop the service and try again. (...) That's about it, unless there's anything else you need. I'm afraid I don't have anything solid to contribute at this stage, but would be grateful for a translation. I can't traslate unless pppd is completely off because I dunno why is running afterall :-) It looks like I can get a reconditioned Dell PC for $250.00 this Monday, which should leave me free to play with the laptop a little more. Good! So, if you don't want to become any more involved with this situation, I can understand. Nope, I like this game :-) 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/pan.2011.08.30.11.24...@gmail.com
Re: Fwd: Billion 7800N
On Mon, Aug 29, 2011 at 9:49 PM, Heddle Weaver weaver2wo...@gmail.com wrote: On 29 August 2011 13:05, D G Teed donald.t...@gmail.com wrote: This would be the entry in /etc/network/interfaces I mentioned before: allow-hotplug eth0 iface eth0 inet dhcp Then reboot. You are really not that far off from getting this up. Well, I've actually done this, but I didn't have too much success. Of course, I didn't give up trying. Unfortunately, I think I tried too much and too far and that's about all I have left in /etc/network/interfaces. Oh. Well, the only other thing you need is the loopback. Typically listed first in the interfaces file: auto lo iface lo inet loopback I thought I'd wait until I installed the new Debian config on the new, secondhand PC. I'm actually posting from that now. So easy when you can access the interface. Once I get a successful config on the new Debian install, I was going to try copying the configuration over to the laptop. I know I've deleted something on the laptop in the 'network' config that I shouldn't have. If you only mean the interfaces file, then the addition above may help. If you mean unknown deleted files from the system, it might be advisable to reinstall. I think you mentioned there was a home directory to preserve. If that is a different partition, there is nothing written over on /home by the installer, as long as you do not select to reformat the /home partition device. Doing it this way is the most constructive way to become more familiar with things, I think. To a point, this is true, but often learning is easier on something that works. If the system is mortally wounded in an unknown way, and you are driving into town to use webmail to get help, and driving back to try a couple more things each time, I think there would be less greenhouse gas produced with a reinstall.
Re: Fwd: Billion 7800N
Heddle Weaver wrote: Failing that, I'll do a new install on the laptop, but I think it'll be alright. Regards and thanks, Weaver. I cannot believe this thread is still going -- it is way beyond funny now it's ludicrous to say the least Your Ethernet device is broken and if it is not broken, then get someone else to fix this problem for you as you are only going around in circles and getting nowhere. -- Kind Regards AndrewM -- 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/4e5cf0d9.30...@affinityvision.com.au
Re: Fwd: Billion 7800N
On Tue, Aug 30, 2011 at 11:16 AM, Andrew McGlashan andrew.mcglas...@affinityvision.com.au wrote: I cannot believe this thread is still going -- it is way beyond funny now it's ludicrous to say the least Your Ethernet device is broken and if it is not broken, then get someone else to fix this problem for you as you are only going around in circles and getting nowhere. There is actually some progress and it might be resolved soon. We have no indication there is a hardware issue, but every indication networking was not set up appropriately in Linux. We finally got past the assumptions that there is something wrong with the router or that ppp daemon was required on the Linux notebook, and now we are making progress. Everyone had to learn the basics some way.
Re: Fwd: Billion 7800N
On Tue, Aug 30, 2011 at 11:16 AM, Andrew McGlashan I cannot believe this thread is still going -- it is way beyond funny now it's ludicrous to say the least Your Ethernet device is broken and if it is not broken, then get someone else to fix this problem for you as you are only going around in circles and getting nowhere. I should add, your earlier suggestion to boot from a Live CD is a very good one. It would provide a very quick method to determine if the hardware or the OS install was faulty. If the Live CD works to get on the 'net, then the notebook hardware is fine and the install/configuration is botched.
Re: Fwd: Billion 7800N
On 29 August 2011 13:05, D G Teed donald.t...@gmail.com wrote: On Sun, Aug 28, 2011 at 10:14 PM, Heddle Weaver weaver2wo...@gmail.comwrote: On 27 August 2011 11:41, D G Teed donald.t...@gmail.com wrote: I started another reply, and it had lots of steps to try to repair this situation, but then I rethought. If this is a fresh install, and you have no data to keep on the Debian system, here is a bulletproof solution: Reinstall. This is the latest fashion. It's not a new install, but I have my /home partition on an external 1TB expansion drive, so inconvenience is minimal and the revision factor won't hurt. I suggested reinstall as it would be the quickest way to get rid of ppp daemon if you didn't know how to disable the service. But now that that mystery is resolved, no need to reinstall. Once ppp is gone, then set up DHCP to get your IP from the router on Debian system. This would be the entry in /etc/network/interfaces I mentioned before: allow-hotplug eth0 iface eth0 inet dhcp Then reboot. You are really not that far off from getting this up. Well, I've actually done this, but I didn't have too much success. Of course, I didn't give up trying. Unfortunately, I think I tried too much and too far and that's about all I have left in /etc/network/interfaces. I thought I'd wait until I installed the new Debian config on the new, secondhand PC. I'm actually posting from that now. So easy when you can access the interface. Once I get a successful config on the new Debian install, I was going to try copying the configuration over to the laptop. I know I've deleted something on the laptop in the 'network' config that I shouldn't have. Doing it this way is the most constructive way to become more familiar with things, I think. Failing that, I'll do a new install on the laptop, but I think it'll be alright. Regards and thanks, Weaver. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On 27 August 2011 06:10, Eduardo M KALINOWSKI edua...@kalinowski.com.brwrote: On 08/26/2011 04:08 PM, Heddle Weaver wrote: All ISPs in Australia employ PPPoE. PPPoA is available, in many instances also. And elsewhere too, but your modem appears to be a router. In this case, it handles PPPoE by itself, and all you need is to get an ip from it via dhcp. Yes. It probably has a bridge mode in which your computer has to establish the PPPoE connection, but unless you have a specific reason to want it, let the modem do it. Yes, in fact it has a separate port for bridging to a modem in the situation of a fibre network (for example0, but we don't need to be concerned with that here. The computer is plugged into one of the four LAN ports, on the router, from the ethernet port on the laptop. In other words, get rid of ppp. You don't need it. O.K.I removed ppp, as it wasn't required, which, of course, removed pppoe and pppoeconf, because they depend on it and now I have: Bandit:/home/weaver# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface Bandit:/home/weaver# .No ppp! Isn't it great? And then, of course, we have: Bandit:/home/weaver# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:15:60:c2:63:46 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:16 lo Link encap:Local Loopback LOOPBACK MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Which also endorses the fact that I have no connection whatsoever! We have consistency! I used to have a LAN problem and now I don't have it any more! A LAN, I mean, and lesser minds would be somewhat nonplussed by this. But not me! A mere bagatelle! It's a unique way of dealing with a problem that I simply haven't come across before, for some obscure reason. If you have a problem within any given environment, simply remove the environment! Just think of the potential in regard to other more major issues! Planetary pollution? Simply remove the planet! Here I await, Breath abate, for even greater revelations from this list. Please, keep them coming. I get my new, secondhand PC delivered tomorrow morning. Stand by for the next episode in 'Weaver - Lost In The Network!' Regards, Weaver. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On 27 August 2011 11:41, D G Teed donald.t...@gmail.com wrote: I started another reply, and it had lots of steps to try to repair this situation, but then I rethought. If this is a fresh install, and you have no data to keep on the Debian system, here is a bulletproof solution: Reinstall. This is the latest fashion. It's not a new install, but I have my /home partition on an external 1TB expansion drive, so inconvenience is minimal and the revision factor won't hurt. When you reinstall, don't do anything fancy with network. Just let it do the default with DHCP. Plug it into the router LAN jack as you do the install. I'm pretty sure the netinstall will pick up the modem/router and install it anyway, for apt. All that's required for that is the username and password. Once Debian is installed, run a web browser and go to the webpage on your router as documented in the router manual. In the router's web site (something like 192.168.1.1), set up the Internet connection to login via PPPoE. If you have already set up the router from your Mac or Windows system and a web browser, you don't need to do it again from Linux, it will just work. If the Debian system can see the router website, but not the Internet after setting up the router with the ISP info, try one reboot of Debian to give it a chance to load the networking since the router had its configuration done. This is the shortest and simplest path to fixing up the botched Linux networking setup you have. I'm getting a new, secondhand PC tomorrow, which has a Windows install on it. I'll be putting a Debian partition on the end of the drive with the same password and username/rootpswd, etc as the current laptop install., which will allocate the external drive to the PC. I will then do a fresh install of Debian on the laptop, with new username/password, etc, which has a 160GB harddrive, which will be plenty for a notebook install if I off-load onto the main system occasionally. Remember, the idea is to allow the router to be your path to the Internet. It will handle everything, and the Linux system only needs to get on the LAN, behind the firewall on the router. That's been the main problem, I think. I didn't appreciate the difference in thinking between a modem and a modem/router. Debian Billion Router ISP Modem -- Internet Cheers! Thanks for the time and trouble. Once it's sorted, I'll write it up and post it to give this thread validity and supply a resource for others. Regards, Weaver. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On Sun, Aug 28, 2011 at 10:14 PM, Heddle Weaver weaver2wo...@gmail.comwrote: On 27 August 2011 11:41, D G Teed donald.t...@gmail.com wrote: I started another reply, and it had lots of steps to try to repair this situation, but then I rethought. If this is a fresh install, and you have no data to keep on the Debian system, here is a bulletproof solution: Reinstall. This is the latest fashion. It's not a new install, but I have my /home partition on an external 1TB expansion drive, so inconvenience is minimal and the revision factor won't hurt. I suggested reinstall as it would be the quickest way to get rid of ppp daemon if you didn't know how to disable the service. But now that that mystery is resolved, no need to reinstall. Once ppp is gone, then set up DHCP to get your IP from the router on Debian system. This would be the entry in /etc/network/interfaces I mentioned before: allow-hotplug eth0 iface eth0 inet dhcp Then reboot. You are really not that far off from getting this up.
Re: Fwd: Billion 7800N
On 26 August 2011 05:05, D G Teed donald.t...@gmail.com wrote: On a re-read of what I wrote earlier, it might be a little confusing where I say you need static network set up and then instruct on how to do DHCP. Perhaps I can just make an assumption or two and give you some simple steps. Assuming your ISP does use PPPoE, and you are using the router device to connect your system to the ISP/Internet: All ISPs in Australia employ PPPoE. PPPoA is available, in many instances also. 1. Disable pppd. This is important. I think the command would be: update-rc.d disable pppd No, that's not it. I'm getting a read-out that says it's not available. 2. Ensure eth0 network device will be able to get an IP from the router via DHCP. This would be the entry in /etc/network/interfaces I mentioned before: allow-hotplug eth0 iface eth0 inet dhcp I placed this into that file and nothing has changed. If anything, connectivity is a little worse. 3. Reboot to allow pppd to go away and dhcp client to kick in. 4. Verify your IP and routing are good: route -n (Here is mine: route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 192.168.0.0 0.0.0.0 255.255.0.0 U 0 00 eth1 0.0.0.0 192.168.0.1 0.0.0.0 UG0 00 eth1 ) Yours would be similar except 192.168.1 everywhere and likely eth0. Bandit:/home/weaver# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 0.0.0.0 0.0.0.0 U 0 00 ppp0 10.20.21.72 0.0.0.0 255.255.255.255 UH0 00 ppp0 Bandit:/home/weaver# eth0 used to be in there. ifconfig -a Bandit:/home/weaver# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:15:60:c2:63:46 inet6 addr: fe80::215:60ff:fec2:6346/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2895 errors:0 dropped:7 overruns:0 frame:0 TX packets:3480 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2053262 (1.9 MiB) TX bytes:668068 (652.4 KiB) Interrupt:16 loLink encap:Local Loopback LOOPBACK MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) ppp0 Link encap:Point-to-Point Protocol inet addr:110.174.203.247 P-t-P:10.20.21.72 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:262 errors:0 dropped:0 overruns:0 frame:0 TX packets:259 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:177245 (173.0 KiB) TX bytes:8 (86.8 KiB) The upside is that I only have one ppp action .at present. I think the output of that is covered previously. 5. Start up a web browser and visit your Billion router at whatever IP the router documentation says it is running on. No, that still doesn't happen. Though I'm posting this from that same laptop. 6. Configure the router for Internet (WAN) access according to the ISP's information. 7. The Internet should now work from the Debian system. It always has. The problem has been that access has been only intermittent and inconsistent when I have gained access. I managed an aptitude cli update/safe-upgrade two nights ago, with about two dozen attempts. Download speeds varied from 8 Bytes/s to 1,686 Kb/s. All over the place. But, at least we can be safe in assuming that the higher speeds weren't by way of your standard dial-up facility. Oh, well. never mind. I get a fully checked out, brand new, second-hand pc in two days. I expect no problems with connectivity with the installed windows whatever, or with the Debian partition I'll install from a downloaded netinstall ISO. It's all very simple here in Australia. The vast majority of ISPs automatically allocate Primary and Secondary DNS as well as IP addresses, so basically all that's required with initial config is username and password. That hasn't been the case this time. I won't give up on the old laptop until I know it's completely hopeless - maybe once I get reconnected I'll try a wireless card. I also need to understand a lot more about networking than I do, also. Regards and thanks, Weaver. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On 08/26/2011 04:08 PM, Heddle Weaver wrote: All ISPs in Australia employ PPPoE. PPPoA is available, in many instances also. And elsewhere too, but your modem appears to be a router. In this case, it handles PPPoE by itself, and all you need is to get an ip from it via dhcp. It probably has a bridge mode in which your computer has to establish the PPPoE connection, but unless you have a specific reason to want it, let the modem do it. In other words, get rid of ppp. You don't need it. -- Mother is the invention of necessity. Eduardo M KALINOWSKI edua...@kalinowski.com.br -- 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/4e57fdbd.9000...@kalinowski.com.br
Re: Fwd: Billion 7800N
I started another reply, and it had lots of steps to try to repair this situation, but then I rethought. If this is a fresh install, and you have no data to keep on the Debian system, here is a bulletproof solution: Reinstall. When you reinstall, don't do anything fancy with network. Just let it do the default with DHCP. Plug it into the router LAN jack as you do the install. Once Debian is installed, run a web browser and go to the webpage on your router as documented in the router manual. In the router's web site (something like 192.168.1.1), set up the Internet connection to login via PPPoE. If you have already set up the router from your Mac or Windows system and a web browser, you don't need to do it again from Linux, it will just work. If the Debian system can see the router website, but not the Internet after setting up the router with the ISP info, try one reboot of Debian to give it a chance to load the networking since the router had its configuration done. This is the shortest and simplest path to fixing up the botched Linux networking setup you have. Remember, the idea is to allow the router to be your path to the Internet. It will handle everything, and the Linux system only needs to get on the LAN, behind the firewall on the router. Debian Billion Router ISP Modem -- Internet
Re: Fwd: Billion 7800N
On a re-read of what I wrote earlier, it might be a little confusing where I say you need static network set up and then instruct on how to do DHCP. Perhaps I can just make an assumption or two and give you some simple steps. Assuming your ISP does use PPPoE, and you are using the router device to connect your system to the ISP/Internet: 1. Disable pppd. This is important. I think the command would be: update-rc.d disable pppd 2. Ensure eth0 network device will be able to get an IP from the router via DHCP. This would be the entry in /etc/network/interfaces I mentioned before: allow-hotplug eth0 iface eth0 inet dhcp 3. Reboot to allow pppd to go away and dhcp client to kick in. 4. Verify your IP and routing are good: route -n (Here is mine: route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 192.168.0.0 0.0.0.0 255.255.0.0 U 0 00 eth1 0.0.0.0 192.168.0.1 0.0.0.0 UG0 00 eth1 ) Yours would be similar except 192.168.1 everywhere and likely eth0. ifconfig -a I think the output of that is covered previously. 5. Start up a web browser and visit your Billion router at whatever IP the router documentation says it is running on. 6. Configure the router for Internet (WAN) access according to the ISP's information. 7. The Internet should now work from the Debian system.
Re: Fwd: Billion 7800N
On 22 August 2011 22:02, Camaleón noela...@gmail.com wrote: On Mon, 22 Aug 2011 10:27:57 +1000, Heddle Weaver wrote: On 21 August 2011 21:20, Camaleón noela...@gmail.com wrote: But do you really need it? I mean, does your ISP require you to use a PPP connection with your router? I also use a DSL connection and don't need PPP for nothing. No I don't. I need pppd of course, but not ppp. And here's a second sample to show how some things seem to move around: Second sample: weaver@Bandit:~$ su Password: Bandit:/home/weaver# plog Aug 24 11:35:00 Bandit pppd[22604]: Serial link appears to be disconnected. Aug 24 11:35:00 Bandit pppd[22604]: Connect time 3.0 minutes. Aug 24 11:35:00 Bandit pppd[22604]: Sent 182 bytes, received 3875 bytes. Aug 24 11:35:06 Bandit pppd[19295]: Connection terminated. Aug 24 11:35:06 Bandit pppd[19295]: Modem hangup Aug 24 11:35:06 Bandit pppd[22604]: Connection terminated. Aug 24 11:35:06 Bandit pppd[22604]: Modem hangup Bandit:/home/weaver# Bandit:/home/weaver# ifconfig ppp0 ppp0 Link encap:Point-to-Point Protocol inet addr:110.174.203.247 P-t-P:10.20.21.81 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:3 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:54 (54.0 B) TX bytes:210 (210.0 B) Bandit:/home/weaver# /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:15:60:c2:63:46 inet6 addr: fe80::215:60ff:fec2:6346/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1573 errors:0 dropped:119 overruns:0 frame:0 TX packets:1796 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:150412 (146.8 KiB) TX bytes:131579 (128.4 KiB) Interrupt:16 loLink 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:529 errors:0 dropped:0 overruns:0 frame:0 TX packets:529 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:31314 (30.5 KiB) TX bytes:31314 (30.5 KiB) ppp0 Link encap:Point-to-Point Protocol inet addr:110.174.203.247 P-t-P:10.20.21.81 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:3 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:54 (54.0 B) TX bytes:210 (210.0 B) ppp1 Link encap:Point-to-Point Protocol inet addr:110.174.203.247 P-t-P:10.20.21.81 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:114 (114.0 B) TX bytes:314 (314.0 B) ppp2 Link encap:Point-to-Point Protocol inet addr:110.174.203.247 P-t-P:10.20.21.72 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:3 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:54 (54.0 B) TX bytes:106 (106.0 B) ppp3 Link encap:Point-to-Point Protocol inet addr:110.174.203.247 P-t-P:10.20.21.36 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:37 errors:0 dropped:0 overruns:0 frame:0 TX packets:31 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:11616 (11.3 KiB) TX bytes:4172 (4.0 KiB) ppp4 Link encap:Point-to-Point Protocol inet addr:110.174.203.247 P-t-P:10.20.21.36 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:12 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:1197 (1.1 KiB) TX bytes:586 (586.0 B) ppp5 Link encap:Point-to-Point Protocol inet addr:110.174.203.247 P-t-P:10.20.21.173 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:181 (181.0 B) TX bytes:54 (54.0 B) ppp6 Link encap:Point-to-Point Protocol inet addr:110.174.203.247 P-t-P:10.20.21.173 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:7
Re: Fwd: Billion 7800N
On 22 August 2011 22:02, Camaleón noela...@gmail.com wrote: On Mon, 22 Aug 2011 10:27:57 +1000, Heddle Weaver wrote: On 21 August 2011 21:20, Camaleón noela...@gmail.com wrote: But do you really need it? I mean, does your ISP require you to use a PPP connection with your router? I also use a DSL connection and don't need PPP for nothing. No I don't. I need pppd of course, but not ppp. Can you explain why you need pppd? :-? Well, I was under the impression that with ppp over ethernet, the daemon would be required. I'm probably wrong. That's alright. It makes other people feel good. Can you point me to somewhere on the Internet where I can see what are your ISP connection settings? I'll bring them into town and post them on the next trip, probably tomorrow. This is getting very interesting, like a mystery novel :-) I've got severe health problems, so I have access to the computers of a specialist Disabled Job Network organisation. They somewhat draw the line before downloading an iso and burning it to disc, though. This is also why I haven't got back to the list over the last couple of days. Stretched out on a bed with a definition of headaches that engenders a death-wish, which I would indulge in if I could move. Luckily the situation takes over completely and I'm incapable of moving. Okay, that's what I thought. Then the same has to apply for your linux box. Can you check if DHCP is enable on the windows laptop? It's not mine. so I've given it back, but to establish a connection immediately, it must have been as I would have needed an IP address to connect. Yes, having DHCP on is the most common nowadays. Anyway, having a static IP would have required to manually set the gateway. Well, there could be something in that. As I recall, this ISP relegates static and not dynamic addresses. The network card requires a firmware, you should download from non-free repos. Additional information here: http://wiki.debian.org/Firmware Further along in the sequence, eth0 and the firmware seem to connect up, so I don't think there's a problem there. Anyway, you should install it. O.K. I'll do that with aptitude when I get a connection. Yep, just to discard any source of the problem. In fact, the same you did in your windows box you have to do in your linux box. If DHCP is enabled on windows, enable it on linux. If no dialer was used in windows, do not use a dialer in linux, and so on... Well, I'm actually getting an IP address on the Linux laptop, so DHCP must be active. If your ethernet device has an IP assigned that means the router is able to communicate with your laptop and so you should also be able to access to the router or at least get a response from wget different than a timeout :-? I believe the contact between the laptop and modem is inconsistent and think this is the source of the majority of disconnections. I think there is more than one aspect to this problem. I'll post that when I get back in also, although I'm sure I've done it already somewhere. I recall my IP, the peer's IP, DNS primary and secondary, amongst other things, but I'll get proof positive. Regards and thanks, Waiting anxiously for the feedback :-) O.K., here it is, but it might be a bit of an over-dose: dhcp last modified May 23rd, and dhcp3, last modified April 29th, both installed and appear active ~ Primary server: 203.12.160.35 Secondary server: 203.12.160.36 These are both present and correct in 'resolve.conf' ~~ This is interesting because it states 'existing default route through ppp3': weaver@Bandit:~$ su Password: Bandit:/home/weaver# plog Aug 23 18:24:15 Bandit pppd[22604]: PAP authentication succeeded Aug 23 18:24:15 Bandit pppd[22604]: peer from calling number 00:03:A0:11:E0:78 authorized Aug 23 18:24:15 Bandit pppd[22604]: not replacing existing default route through ppp3 Aug 23 18:24:15 Bandit pppd[22604]: local IP address 110.174.203.247 Aug 23 18:24:15 Bandit pppd[22604]: remote IP address 10.20.21.81 Aug 23 18:24:15 Bandit pppd[22604]: primary DNS address 203.12.160.35 Aug 23 18:24:15 Bandit pppd[22604]: secondary DNS address 203.12.160.36 Bandit:/home/weaver# ~~ ...and here we have ppp addresses where there shouldn't be any: Bandit:/home/weaver# /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:15:60:c2:63:46 inet6 addr: fe80::215:60ff:fec2:6346/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2297 errors:0 dropped:110 overruns:0 frame:0 TX packets:3351 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:583932 (570.2 KiB) TX bytes:340990 (332.9 KiB) Interrupt:16 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128
Re: Fwd: Billion 7800N
On Mon, 22 Aug 2011 10:27:57 +1000, Heddle Weaver wrote: On 21 August 2011 21:20, Camaleón noela...@gmail.com wrote: But do you really need it? I mean, does your ISP require you to use a PPP connection with your router? I also use a DSL connection and don't need PPP for nothing. No I don't. I need pppd of course, but not ppp. Can you explain why you need pppd? :-? Can you point me to somewhere on the Internet where I can see what are your ISP connection settings? I'll bring them into town and post them on the next trip, probably tomorrow. This is getting very interesting, like a mystery novel :-) Okay, that's what I thought. Then the same has to apply for your linux box. Can you check if DHCP is enable on the windows laptop? It's not mine. so I've given it back, but to establish a connection immediately, it must have been as I would have needed an IP address to connect. Yes, having DHCP on is the most common nowadays. Anyway, having a static IP would have required to manually set the gateway. The network card requires a firmware, you should download from non-free repos. Additional information here: http://wiki.debian.org/Firmware Further along in the sequence, eth0 and the firmware seem to connect up, so I don't think there's a problem there. Anyway, you should install it. O.K. I'll do that with aptitude when I get a connection. Yep, just to discard any source of the problem. In fact, the same you did in your windows box you have to do in your linux box. If DHCP is enabled on windows, enable it on linux. If no dialer was used in windows, do not use a dialer in linux, and so on... Well, I'm actually getting an IP address on the Linux laptop, so DHCP must be active. If your ethernet device has an IP assigned that means the router is able to communicate with your laptop and so you should also be able to access to the router or at least get a response from wget different than a timeout :-? I'll post that when I get back in also, although I'm sure I've done it already somewhere. I recall my IP, the peer's IP, DNS primary and secondary, amongst other things, but I'll get proof positive. Regards and thanks, Waiting anxiously for the feedback :-) 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/pan.2011.08.22.12.02...@gmail.com
Re: Fwd: Billion 7800N
On Sun, 21 Aug 2011 09:11:19 +1000, Heddle Weaver wrote: On 20 August 2011 05:56, Camaleón noela...@gmail.com wrote: Wait... what are those pppx connections? Where are they coming from? Are you using another device to get connected on Internet? The only other device I've used is the borrowed XP laptop I used to set up the modem in the first place. That was a wireless connection, even though I plugged the cable in. I was just so glad to get a connection, I let it go. Perhaps it's a hangover from that? You said you used another laptop with XP to test the connection with the router but that does not explain what are pppd connections doing in your linux box :-) (ppp are a different method to get a connection over Internet, nowadays mostly used for dial-up modems or USB DSL modems but I'm afraid that's not your case...) Can you explain how did you connect your windows computer to Internet? What steps did you follow? Maybe this way we can understand what is going on... That's all there was. Just the one machine, with a wireless config to set up the WAN, but with the ethernet cable plugged in. Possibly, with windows typical interference, it's configured the modem with his account details and I'm getting free access? The pressure builds. I've got to sort this out! It is still not clear what steps did you follow to get your XP laptop connected to the router :-? I took a look at dmesg to see what that could tell me about what was going on. First in the sequence I got this: [2.129507] tg3 :02:0e.0: eth0: Tigon3 [partno(BCM95705A50) rev 3003] (PCI:33MHz:32-bit) MAC address 00:15:60:c2:63:46 [2.142802] tg3 :02:0e.0: eth0: attached PHY is 5705 (10/100/1000Base-T Ethernet) (WireSpeed[0]) That's the normal log for a network card. Which seems to suggest that the non-free Tygon firmware is involved. I thought that was just for hard drives. Further down in the sequence I get this: [ 252.853480] tg3 :02:0e.0: eth0: Failed to load firmware tigon/tg3_tso5.bin (...) The network card requires a firmware, you should download from non-free repos. Additional information here: http://wiki.debian.org/Firmware And at last we arrive at this - and if it applies, I would have no idea. I just wish they'd write this stuff in English. (...) That looks like the firewall log, nothing wrong nor nothing you should worry about :-) 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/pan.2011.08.21.09.51...@gmail.com
Re: Fwd: Billion 7800N
On Sun, 21 Aug 2011 12:51:10 +1000, Heddle Weaver wrote: On 20 August 2011 05:50, Camaleón noela...@gmail.com wrote: Hum... are you sure your router is still at 192.168.1.254? I ran some status checks and get multiple results, without any other configuration: Aug 21 10:15:08 Bandit pppd[32274]: peer from calling number 00:03:A0:11:DC:78 authorized Aug 21 10:15:08 Bandit pppd[32274]: not replacing existing default route through ppp1 Aug 21 10:15:08 Bandit pppd[32274]: local IP address 110.174.203.247 Aug 21 10:15:08 Bandit pppd[32274]: remote IP address 10.20.21.36 Aug 21 10:15:08 Bandit pppd[32274]: primary DNS address 203.12.160.35 Aug 21 10:15:08 Bandit pppd[32274]: secondary DNS address 203.12.160.36 (...) Wait, wait... I will ask this again :-) Why are you using a PPP connection? Ethernet routers do not usually need to setup such kind of connections, you only need to configure your ethernet card (or your DSL device, the LAN part) accordingly and that's all. No PPP nor dialers on the client side, nothing. I suggest you to call your ISP and ask for a technician to setup your device. If they refuse to configure it under linux, call a friend with experience in linux and DSL routers and give him a beer once it finishes :-) 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/pan.2011.08.21.09.59...@gmail.com
Re: Fwd: Billion 7800N
On 21 August 2011 13:28, Andrew McGlashan andrew.mcglas...@affinityvision.com.au wrote: Hi, Heddle Weaver wrote: So it looks more and more like hardware. Regards, I don't agree. The 7800N is one of Billion's best modems, it may be faulty, but I don't think so reading through all this horrible thread. As I have already said, if you had actually read the thread. The thread and your experience completely mis-represents Billion's product as it seems you are clueless on how to use it properly and as designed No, I have not represented Billion's product, I have actually endorsed it. -- ala, as others have said, it should not require anything special and almost ANY reasonable browser will work fine for configuration with standard browser settings on Linux or Windows or any other operating system that understands and works properly with standard TCP networks. But, it doesn't. Access to the modem interface has not been achieved through the use of four separate browsers. But, you would know this, having read the thread. What I find happens with many Mac users is that they try to setup PPP login on their computer, when the modem is meant to be doing the job for their network. This kind of problem is not something that is normally seen with Linux users as they tend to have more of a clue than a Mac user and usually more of a clue than most Windows users. This is somewhat extraneous as there is no Mac or network, other than a laptop and the modem. I suggest the following: First off, connect the modem directly to the setup machine via the Ethernet cable using a LAN port, do not connect to any other devices, ie no switches or other network -- just the modem with the computer. This has already been done. It is fully recorded in the thread. Oh, connect the phone line of the DSL connection too, make sure it isn't filtered coming in to the modem. Yes, so far a standard set-up. And what I've had from the beginning of this situation. - Fully reset the 7800N to factory defaults, any way you can, even using the Windows machine. This is accomplished by way of using the 'reset' button. A facility on most modems. - Use a LIVE CD and eliminate your Linux installation from the equation. The Live CD needs to work, it needs to have drivers for your network card -- if it works fine, then proceed using the setup, otherwise continue with the Windows machine. There's nothing wrong with the O.S., which has also been recently established. When I was referring to a hardware problem, I was referring to the motherboard of an ageing laptop. - Check that you have an IP address in the range of the modem's standard LAN (probably 192.168.1.254 or 192.168.2.254), netmask is 255.255.255.0. - You should be able to telnet to the modem with username admin and password admin -- logout with user logout on the command line interface, don't do anything else here, you seem to be out of your depth in this area. This will prove connectivity with the modem on it's network and that everything should be fine. We have already done this and access is not available by way of telnet or wget. But, you would know this, having read the thread. Take a breath. If all the above works fine, then you should use the web config of the modem. Take a breath. This is not achievable under the current circumstances, because we cannot access the modem interface. You seem to be under the impression that this is the first modem I have configured. It isn't. - Login to the web config using http://192.168.1.254 -- the username and password will both be admin. Once logged in. - Run the quick start wizard. Change only two things, the ISP username and the ISP password. [You may want to scan connection types first, or not). ISPs may give you DNS servers and other setting, but you normally only want to change two things, the PPP username login and the PPP password. - Once you have gone through setting up the ISP login (which the modem takes care of), then do a save configuration to flash, click on the save link, then click on the apply button -- wait for it to say it has been done successfully. You should now have a modem that offers default wireless (fix that ASAP), it should give out IP settings via DHCP (it's own built-in server) and it will be connected to the Internet via the ISP login that you entered. Any machine needing access to the Internet through this modem will simply plug in to the built-in LAN switch or use wireless. The device will get IP settings via DHCP. You do not need to do any kind of PPP login on anything other than the modem itself. Further configuration is for someone whom understands the above things properly first, for starters. All of this is understood, you see. But first we need to access the modem interface, yes/no? Any further configuration is more advanced. I strongly urge you to work out, properly, how to
Re: Fwd: Billion 7800N
Hi, I've read the thread completely. It seems clear to me that you have had networking issues where you've had an IP and then not had an IP. If you have a fully working TCP/IP V4 stack, then I'm sure you'll see success. Have you tried a live cd? Pressing the reset button on the Billion modems, usually resets to factory default, it doesn't always work -- but for sure it does work most of the time. You've also shown evidence of PPP in your setup, unless you wish to use bridge mode, you shouldn't have anything in relation to ppp in your Linux setup. Thank you. btw glad you enjoyed the laugh ;-) -- Kind Regards AndrewM Andrew McGlashan Broadband Solutions now including VoIP -- 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/4e50e5db.4020...@affinityvision.com.au
Re: Fwd: Billion 7800N
On 21 August 2011 19:51, Camaleón noela...@gmail.com wrote: On Sun, 21 Aug 2011 09:11:19 +1000, Heddle Weaver wrote: On 20 August 2011 05:56, Camaleón noela...@gmail.com wrote: Wait... what are those pppx connections? Where are they coming from? Are you using another device to get connected on Internet? The only other device I've used is the borrowed XP laptop I used to set up the modem in the first place. That was a wireless connection, even though I plugged the cable in. I was just so glad to get a connection, I let it go. Perhaps it's a hangover from that? You said you used another laptop with XP to test the connection with the router but that does not explain what are pppd connections doing in your linux box :-) (ppp are a different method to get a connection over Internet, nowadays mostly used for dial-up modems or USB DSL modems but I'm afraid that's not your case...) Will check out /etc/ppp/peers/dsl-providers. Sounds like I might have screwed something up in there. Can you explain how did you connect your windows computer to Internet? What steps did you follow? Maybe this way we can understand what is going on... That's all there was. Just the one machine, with a wireless config to set up the WAN, but with the ethernet cable plugged in. Possibly, with windows typical interference, it's configured the modem with his account details and I'm getting free access? The pressure builds. I've got to sort this out! It is still not clear what steps did you follow to get your XP laptop connected to the router :-? Just the ethernet cable, that's all. The pop-up for the quick connect just appeared on the screen. I didn't have to go looking for anything. Different laptop, mainboard. I took a look at dmesg to see what that could tell me about what was going on. First in the sequence I got this: [2.129507] tg3 :02:0e.0: eth0: Tigon3 [partno(BCM95705A50) rev 3003] (PCI:33MHz:32-bit) MAC address 00:15:60:c2:63:46 [2.142802] tg3 :02:0e.0: eth0: attached PHY is 5705 (10/100/1000Base-T Ethernet) (WireSpeed[0]) That's the normal log for a network card. Which seems to suggest that the non-free Tygon firmware is involved. I thought that was just for hard drives. Further down in the sequence I get this: [ 252.853480] tg3 :02:0e.0: eth0: Failed to load firmware tigon/tg3_tso5.bin (...) The network card requires a firmware, you should download from non-free repos. Additional information here: http://wiki.debian.org/Firmware Further along in the sequence, eth0 and the firmware seem to connect up, so I don't think there's a problem there. And at last we arrive at this - and if it applies, I would have no idea. I just wish they'd write this stuff in English. (...) That looks like the firewall log, nothing wrong nor nothing you should worry about :-) O.K., thanks. So good to have constructive mentalities to talk to. Maybe I'll be able to help you one day. As you were saying, with eth0 and a cable, there's nothing much that can go wrong, so with the disconnects, it looks like the problem is before that. Regards, Weaver. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On 08/21/2011 07:53 AM, Heddle Weaver wrote: We have already done this and access is not available by way of telnet or wget. But, you would know this, having read the thread. This thread is far too long and confused, so this might have been asked already: give us the output of /sbin/ifconfig and /sbin/route -n -- His mind is like a steel trap: full of mice. -- Foghorn Leghorn Eduardo M KALINOWSKI edua...@kalinowski.com.br -- 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/4e50e5f8.1060...@kalinowski.com.br
Re: Fwd: Billion 7800N
On Sun, 21 Aug 2011 21:07:50 +1000, Heddle Weaver wrote: On 21 August 2011 19:51, Camaleón noela...@gmail.com wrote: (ppp are a different method to get a connection over Internet, nowadays mostly used for dial-up modems or USB DSL modems but I'm afraid that's not your case...) Will check out /etc/ppp/peers/dsl-providers. Sounds like I might have screwed something up in there. But do you really need it? I mean, does your ISP require you to use a PPP connection with your router? I also use a DSL connection and don't need PPP for nothing. Can you point me to somewhere on the Internet where I can see what are your ISP connection settings? It is still not clear what steps did you follow to get your XP laptop connected to the router :-? Just the ethernet cable, that's all. The pop-up for the quick connect just appeared on the screen. I didn't have to go looking for anything. Different laptop, mainboard. Okay, that's what I thought. Then the same has to apply for your linux box. Can you check if DHCP is enable on the windows laptop? [ 252.853480] tg3 :02:0e.0: eth0: Failed to load firmware tigon/tg3_tso5.bin (...) The network card requires a firmware, you should download from non-free repos. Additional information here: http://wiki.debian.org/Firmware Further along in the sequence, eth0 and the firmware seem to connect up, so I don't think there's a problem there. Anyway, you should install it. O.K., thanks. So good to have constructive mentalities to talk to. Maybe I'll be able to help you one day. As you were saying, with eth0 and a cable, there's nothing much that can go wrong, so with the disconnects, it looks like the problem is before that. Regards, In fact, the same you did in your windows box you have to do in your linux box. If DHCP is enabled on windows, enable it on linux. If no dialer was used in windows, do not use a dialer in linux, and so on... 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/pan.2011.08.21.11.20...@gmail.com
Re: Fwd: Billion 7800N
On Sunday 21 August 2011 12:20:04 Camaleón wrote: Will check out /etc/ppp/peers/dsl-providers. Sounds like I might have screwed something up in there. Surely the whole point is that it shouldn't be there at all, not that you might have screwed up in there? At least, I think that that is what Camaleón is saying. I have certainly never heard of using ppp to connect by Ethernet to a router. Lisi -- 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/201108211229.08412.lisi.re...@gmail.com
Re: Fwd: Billion 7800N
On 21 August 2011 21:03, Eduardo M KALINOWSKI edua...@kalinowski.com.brwrote: On 08/21/2011 07:53 AM, Heddle Weaver wrote: We have already done this and access is not available by way of telnet or wget. But, you would know this, having read the thread. This thread is far too long and confused, so this might have been asked already: give us the output of /sbin/ifconfig and /sbin/route -n Will post these next trip into town. I had a link last night but haven't been able to get it back yet. Regards, Weaver. -- His mind is like a steel trap: full of mice. -- Foghorn Leghorn Eduardo M KALINOWSKI edua...@kalinowski.com.br -- 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/4e50e5f8.1060...@kalinowski.com.br -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On 21 August 2011 21:20, Camaleón noela...@gmail.com wrote: On Sun, 21 Aug 2011 21:07:50 +1000, Heddle Weaver wrote: On 21 August 2011 19:51, Camaleón noela...@gmail.com wrote: (ppp are a different method to get a connection over Internet, nowadays mostly used for dial-up modems or USB DSL modems but I'm afraid that's not your case...) Will check out /etc/ppp/peers/dsl-providers. Sounds like I might have screwed something up in there. But do you really need it? I mean, does your ISP require you to use a PPP connection with your router? I also use a DSL connection and don't need PPP for nothing. No I don't. I need pppd of course, but not ppp. Can you point me to somewhere on the Internet where I can see what are your ISP connection settings? I'll bring them into town and post them on the next trip, probably tomorrow. It is still not clear what steps did you follow to get your XP laptop connected to the router :-? Just the ethernet cable, that's all. The pop-up for the quick connect just appeared on the screen. I didn't have to go looking for anything. Different laptop, mainboard. Okay, that's what I thought. Then the same has to apply for your linux box. Can you check if DHCP is enable on the windows laptop? It's not mine. so I've given it back, but to establish a connection immediately, it must have been as I would have needed an IP address to connect. [ 252.853480] tg3 :02:0e.0: eth0: Failed to load firmware tigon/tg3_tso5.bin (...) The network card requires a firmware, you should download from non-free repos. Additional information here: http://wiki.debian.org/Firmware Further along in the sequence, eth0 and the firmware seem to connect up, so I don't think there's a problem there. Anyway, you should install it. O.K. I'll do that with aptitude when I get a connection. O.K., thanks. So good to have constructive mentalities to talk to. Maybe I'll be able to help you one day. As you were saying, with eth0 and a cable, there's nothing much that can go wrong, so with the disconnects, it looks like the problem is before that. Regards, In fact, the same you did in your windows box you have to do in your linux box. If DHCP is enabled on windows, enable it on linux. If no dialer was used in windows, do not use a dialer in linux, and so on... Well, I'm actually getting an IP address on the Linux laptop, so DHCP must be active. I'll post that when I get back in also, although I'm sure I've done it already somewhere. I recall my IP, the peer's IP, DNS primary and secondary, amongst other things, but I'll get proof positive. Regards and thanks, Weaver. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On 20 August 2011 05:56, Camaleón noela...@gmail.com wrote: Wait... what are those pppx connections? Where are they coming from? Are you using another device to get connected on Internet? The only other device I've used is the borrowed XP laptop I used to set up the modem in the first place. That was a wireless connection, even though I plugged the cable in. I was just so glad to get a connection, I let it go. Perhaps it's a hangover from that? And I can't see the address anywhere. Also, according to the manual, the mask address is supposed to be 225.25.225.0 There is something evil happening. I can't actually remember adjusting anything, yet the connection, far from good, is the best I've had so far. The above data is very clear: your ethernet device has lost (again) its configuration. what I dunno is what are the remainder ppp connections :-? Can you explain how did you connect your windows computer to Internet? What steps did you follow? Maybe this way we can understand what is going on... That's all there was. Just the one machine, with a wireless config to set up the WAN, but with the ethernet cable plugged in. Possibly, with windows typical interference, it's configured the modem with his account details and I'm getting free access? The pressure builds. I've got to sort this out! I took a look at dmesg to see what that could tell me about what was going on. First in the sequence I got this: [2.129507] tg3 :02:0e.0: eth0: Tigon3 [partno(BCM95705A50) rev 3003] (PCI:33MHz:32-bit) MAC address 00:15:60:c2:63:46 [2.142802] tg3 :02:0e.0: eth0: attached PHY is 5705 (10/100/1000Base-T Ethernet) (WireSpeed[0]) Which seems to suggest that the non-free Tygon firmware is involved. I thought that was just for hard drives. Further down in the sequence I get this: [ 252.853480] tg3 :02:0e.0: eth0: Failed to load firmware tigon/tg3_tso5.bin [ 252.855483] tg3 :02:0e.0: eth0: TSO capability disabled [ 252.994052] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 253.367980] PPP generic driver version 2.4.2 [ 254.103297] process `sysctl' is using deprecated sysctl (syscall) net.ipv6.neigh.default.retrans_time; Use net.ipv6.neigh.default.retrans_time_ms instead. [ 254.471468] ip_tables: (C) 2000-2006 Netfilter Core Team [ 254.489770] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 254.515823] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 256.159728] tg3 :02:0e.0: eth0: Link is up at 1000 Mbps, full duplex [ 256.159732] tg3 :02:0e.0: eth0: Flow control is on for TX and on for RX [ 256.160083] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 256.170762] fuse init (API version 7.16) [ 257.872663] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input9 [ 266.944025] eth0: no IPv6 routers present [ 267.224323] NET: Registered protocol family 24 [ 271.333079] AIF:Dropped INPUT packet: IN=ppp0 OUT= MAC= SRC=61.128.110.98 DST=110.174.203.247 LEN=40 TOS=0x00 PREC=0x00 TTL=108 ID=256 PROTO=TCP SPT=6000 DPT=1433 WINDOW=16384 RES=0x00 SYN URGP=0 And at last we arrive at this - and if it applies, I would have no idea. I just wish they'd write this stuff in English. [ 568.682330] AIF:Dropped INPUT packet: IN=ppp1 OUT= MAC= SRC=76.72.165.90 DST=110.174.203.247 LEN=40 TOS=0x00 PREC=0x00 TTL=116 ID=256 DF PROTO=TCP SPT=12200 DPT=8909 WINDOW=8192 RES=0x00 SYN URGP=0 [ 990.383838] gs[7403]: segfault at 40 ip b70f70f2 sp bffce1a0 error 4 in libgs.so.9.02[b6f56000+4e5000] [ 999.945440] AIF:PRIV UDP broadcast: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:b8:ff:61:ee:d3:40:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=255 ID=54518 PROTO=UDP SPT=68 DPT=67 LEN=308 [ 1001.964640] AIF:PRIV UDP broadcast: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:b8:ff:61:ee:d3:40:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=255 ID=54519 PROTO=UDP SPT=68 DPT=67 LEN=308 [ 2137.861131] AIF:PRIV UDP broadcast: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:12:7c:d2:9b:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=255 ID=52104 PROTO=UDP SPT=68 DPT=67 LEN=308 [ 2139.057008] AIF:PRIV UDP broadcast: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:12:7c:d2:9b:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=255 ID=52105 PROTO=UDP SPT=68 DPT=67 LEN=308 [ 2154.619171] AIF:PRIV UDP broadcast: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:12:7c:d2:9b:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=255 ID=52110 PROTO=UDP SPT=68 DPT=67 LEN=308 And that's it! 'Life in the bitter sea', as the Chinese say, and I'm drowning. Thanks for staying with this. Regards, Weaver. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On 20 August 2011 06:07, Camaleón noela...@gmail.com wrote: On Thu, 18 Aug 2011 16:02:17 +1000, Heddle Weaver wrote: I don't know what's happening any more. I think I'm being haunted. Greemlins are anywhere and they like computers so much, keep your eyes opened! X-) I've just reset the modem to see if I could access the modem url to set it up properly. Hum... I hope the router restores fine from a reset with all the wan settings already predefined for your ISP. Resetting the router is not a task you have to do every day, just avoid to do that unless is strictly necessary :-) I've got four green leds up, Power; Lan; Wireless (The laptop doesn't have a wireless card) DSL. The 5th light is for 'net, and it's orange, which means no connection, but I'm sending this on my gmail account through that same laptop. I'm going to need more than a pair of low-slung six-guns to get me out of this! Usually, the orange light of the Internet port means the router is trying to get an IP for the ISP, after a reset this can be normal. Yes, but after it achieves that, the led turns green and flashes, along with the LAN led to indicate net activity with this modem. And don't worry for Gmail, this is another beast and does its own caching magic in the background... Yes, and there's going to be a lot more activity of that type coming up too. I just hope I'm good enough at the time to evade it all. Corporate money buying our privacy and we don't even get the money. Regards, Weaver. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On 20 August 2011 05:50, Camaleón noela...@gmail.com wrote: On Thu, 18 Aug 2011 07:18:37 +1000, Heddle Weaver wrote: On 16 August 2011 22:12, Camaleón noela...@gmail.com wrote: weaver@Bandit:~$ su Password: Bandit:/home/weaver# wget 192.168.1.254 --2011-08-16 06:06:49-- http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. --2011-08-16 06:07:36-- (try: 2) http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. --2011-08-16 06:08:23-- (try: 3) http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. Hum... are you sure your router is still at 192.168.1.254? I ran some status checks and get multiple results, without any other configuration: Aug 21 10:15:08 Bandit pppd[32274]: peer from calling number 00:03:A0:11:DC:78 authorized Aug 21 10:15:08 Bandit pppd[32274]: not replacing existing default route through ppp1 Aug 21 10:15:08 Bandit pppd[32274]: local IP address 110.174.203.247 Aug 21 10:15:08 Bandit pppd[32274]: remote IP address 10.20.21.36 Aug 21 10:15:08 Bandit pppd[32274]: primary DNS address 203.12.160.35 Aug 21 10:15:08 Bandit pppd[32274]: secondary DNS address 203.12.160.36 and: Aug 21 10:41:18 Bandit pppd[2188]: remote IP address 10.20.21.81 Aug 21 10:41:18 Bandit pppd[2188]: primary DNS address 203.12.160.35 Aug 21 10:41:18 Bandit pppd[2188]: secondary DNS address 203.12.160.36 and: Bandit:/home/weaver# plog Aug 21 12:03:46 Bandit pppd[32274]: Modem hangup Aug 21 12:03:50 Bandit pppd[1824]: No response to 3 echo-requests Aug 21 12:03:50 Bandit pppd[1824]: Serial link appears to be disconnected. Aug 21 12:03:50 Bandit pppd[1824]: Connect time 2.4 minutes. Aug 21 12:03:50 Bandit pppd[1824]: Sent 4422 bytes, received 0 bytes. Aug 21 12:03:56 Bandit pppd[1824]: Connection terminated. Aug 21 12:03:56 Bandit pppd[1824]: Modem hangup and with: Bandit:/home/weaver# ifconfig ppp0 ppp0 Link encap:Point-to-Point Protocol inet addr:110.174.203.247 P-t-P:10.20.21.81 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:6 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:435 (435.0 B) TX bytes:106 (106.0 B) So it looks more and more like hardware. Regards, Weaver. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
Hi, Heddle Weaver wrote: So it looks more and more like hardware. Regards, I don't agree. The 7800N is one of Billion's best modems, it may be faulty, but I don't think so reading through all this horrible thread. The thread and your experience completely mis-represents Billion's product as it seems you are clueless on how to use it properly and as designed -- ala, as others have said, it should not require anything special and almost ANY reasonable browser will work fine for configuration with standard browser settings on Linux or Windows or any other operating system that understands and works properly with standard TCP networks. What I find happens with many Mac users is that they try to setup PPP login on their computer, when the modem is meant to be doing the job for their network. This kind of problem is not something that is normally seen with Linux users as they tend to have more of a clue than a Mac user and usually more of a clue than most Windows users. I suggest the following: First off, connect the modem directly to the setup machine via the Ethernet cable using a LAN port, do not connect to any other devices, ie no switches or other network -- just the modem with the computer. Oh, connect the phone line of the DSL connection too, make sure it isn't filtered coming in to the modem. - Fully reset the 7800N to factory defaults, any way you can, even using the Windows machine. - Use a LIVE CD and eliminate your Linux installation from the equation. The Live CD needs to work, it needs to have drivers for your network card -- if it works fine, then proceed using the setup, otherwise continue with the Windows machine.. - Check that you have an IP address in the range of the modem's standard LAN (probably 192.168.1.254 or 192.168.2.254), netmask is 255.255.255.0. - You should be able to telnet to the modem with username admin and password admin -- logout with user logout on the command line interface, don't do anything else here, you seem to be out of your depth in this area. This will prove connectivity with the modem on it's network and that everything should be fine. Take a breath. If all the above works fine, then you should use the web config of the modem. - Login to the web config using http://192.168.1.254 -- the username and password will both be admin. Once logged in. - Run the quick start wizard. Change only two things, the ISP username and the ISP password. [You may want to scan connection types first, or not). ISPs may give you DNS servers and other setting, but you normally only want to change two things, the PPP username login and the PPP password. - Once you have gone through setting up the ISP login (which the modem takes care of), then do a save configuration to flash, click on the save link, then click on the apply button -- wait for it to say it has been done successfully. You should now have a modem that offers default wireless (fix that ASAP), it should give out IP settings via DHCP (it's own built-in server) and it will be connected to the Internet via the ISP login that you entered. Any machine needing access to the Internet through this modem will simply plug in to the built-in LAN switch or use wireless. The device will get IP settings via DHCP. You do not need to do any kind of PPP login on anything other than the modem itself. Further configuration is for someone whom understands the above things properly first, for starters. Any further configuration is more advanced. I strongly urge you to work out, properly, how to secure the wireless effectively -- change the network name from default, don't use WEP, do use WPA2-PSK with a long and strong password, forget about trying to hide the network or limiting via MAC addresses as both of these options are pointless. If you are unable to manage the above, effectively, I am sure that there are many local people (some maybe even IT consultants), whom should be able to handle this very, very easily -- you'll probably need to have a friend help you or pay a consultant to fix it for you. There was advice I heard a few times about a Word Perfect help desk support call -- it was gold, it might apply to you [1]. Perhaps, only perhaps, that is being a bit harsh. [1] http://www.free-funny-jokes.com/from-the-wordperfect-help-desk.html Good luck, it seems you really need it or a good pay for consultant to help you out -- I don't envy being that consultant in this situation. ;-) -- Kind Regards AndrewM Andrew McGlashan Broadband Solutions now including VoIP -- 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/4e507b41.7000...@affinityvision.com.au
Re: Fwd: Billion 7800N
On Thu, 18 Aug 2011 07:18:37 +1000, Heddle Weaver wrote: On 16 August 2011 22:12, Camaleón noela...@gmail.com wrote: weaver@Bandit:~$ su Password: Bandit:/home/weaver# wget 192.168.1.254 --2011-08-16 06:06:49-- http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. --2011-08-16 06:07:36-- (try: 2) http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. --2011-08-16 06:08:23-- (try: 3) http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. Hum... are you sure your router is still at 192.168.1.254? Yes, because I'm still getting some connections. Every now and again, I get some connections I haven't been able to, e.g., This is the first time I've been able to get access to gmail for two days. That's so weird. I would try with another ethernet interface (if you're running a laptop, there are some cheap USB to RJ-45 adapters). I'm thinking it must be something under the network config. Something in the O.S. itself that has come adrift. I'll try a reinstall. My /home partition is on an external drive, so the data is safe and a reinstall doesn't represent as much of a problem as it would otherwise. Reinstalling is a no-no in the linux ecosphere, is the last resort for the brave and valiants riders (just kidding :-P)... and in this case I'm afraid you won't obtain any gain in doing it. You better hang in there and try to solve the mistery by yourself :-) I understand, but I notice things like the port light on a the laptop's ethernet outlet doesn't seem as busy as it should be and I suspect that, in an eight year old laptop, the main-board may have problems. This is beyond the Lone Ranger, or even the Silver Surfer to solve with a script or two. Regards, If you're facing a hardware issue here, reinstalling won't solve so much ;-(. Anyway, better that reinstalling is testing a LiveCD of your choice, it's a less-aggressive approach. 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/pan.2011.08.19.19.50...@gmail.com
Re: Fwd: Billion 7800N
On Thu, 18 Aug 2011 13:54:13 +1000, Heddle Weaver wrote: On 16 August 2011 22:12, Camaleón noela...@gmail.com wrote: (...) --2011-08-16 06:08:23-- (try: 3) http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. Hum... are you sure your router is still at 192.168.1.254? Now I'm getting this from /sbin/ifconfig: (...) Wait... what are those pppx connections? Where are they coming from? Are you using another device to get connected on Internet? And I can't see the address anywhere. Also, according to the manual, the mask address is supposed to be 225.25.225.0 There is something evil happening. I can't actually remember adjusting anything, yet the connection, far from good, is the best I've had so far. The above data is very clear: your ethernet device has lost (again) its configuration. what I dunno is what are the remainder ppp connections :-? Can you explain how did you connect your windows computer to Internet? What steps did you follow? Maybe this way we can understand what is going on... 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/pan.2011.08.19.19.56...@gmail.com
Re: Fwd: Billion 7800N
On Thu, 18 Aug 2011 16:02:17 +1000, Heddle Weaver wrote: I don't know what's happening any more. I think I'm being haunted. Greemlins are anywhere and they like computers so much, keep your eyes opened! X-) I've just reset the modem to see if I could access the modem url to set it up properly. Hum... I hope the router restores fine from a reset with all the wan settings already predefined for your ISP. Resetting the router is not a task you have to do every day, just avoid to do that unless is strictly necessary :-) I've got four green leds up, Power; Lan; Wireless (The laptop doesn't have a wireless card) DSL. The 5th light is for 'net, and it's orange, which means no connection, but I'm sending this on my gmail account through that same laptop. I'm going to need more than a pair of low-slung six-guns to get me out of this! Usually, the orange light of the Internet port means the router is trying to get an IP for the ISP, after a reset this can be normal. And don't worry for Gmail, this is another beast and does its own caching magic in the background... 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/pan.2011.08.19.20.07...@gmail.com
Re: Fwd: Billion 7800N
On 16 August 2011 22:12, Camaleón noela...@gmail.com wrote: On Tue, 16 Aug 2011 06:18:01 +1000, Heddle Weaver wrote: On 16 August 2011 05:51, Camaleón noela...@gmail.com wrote: How about a simple wget 192.168.1.254? weaver@Bandit:~$ su Password: Bandit:/home/weaver# wget 192.168.1.254 --2011-08-16 06:06:49-- http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. --2011-08-16 06:07:36-- (try: 2) http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. --2011-08-16 06:08:23-- (try: 3) http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. Hum... are you sure your router is still at 192.168.1.254? I don't know what's happening any more. I think I'm being haunted. I've just reset the modem to see if I could access the modem url to set it up properly. I've got four green leds up, Power; Lan; Wireless (The laptop doesn't have a wireless card) DSL. The 5th light is for 'net, and it's orange, which means no connection, but I'm sending this on my gmail account through that same laptop. I'm going to need more than a pair of low-slung six-guns to get me out of this! Regards, Weaver. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On 16 August 2011 22:12, Camaleón noela...@gmail.com wrote: On Tue, 16 Aug 2011 06:18:01 +1000, Heddle Weaver wrote: On 16 August 2011 05:51, Camaleón noela...@gmail.com wrote: How about a simple wget 192.168.1.254? weaver@Bandit:~$ su Password: Bandit:/home/weaver# wget 192.168.1.254 --2011-08-16 06:06:49-- http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. --2011-08-16 06:07:36-- (try: 2) http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. --2011-08-16 06:08:23-- (try: 3) http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. Hum... are you sure your router is still at 192.168.1.254? Yes, because I'm still getting some connections. Every now and again, I get some connections I haven't been able to, e.g., This is the first time I've been able to get access to gmail for two days. (...) I think I have messed up my install inadvertently, in a way that the fact that it is SID doesn't account for. Really, I can't see how your network configuration can be a problem here. If you have setup static values for your NIC and you can ping/reach your DSL router you should get the same you get when using a Windows client. There is no more magic behind an ethernet device and that's precisely its best bet: it works regardless the OS and does not require for special drivers :-) I'm thinking it must be something under the network config. Something in the O.S. itself that has come adrift. I'll try a reinstall. My /home partition is on an external drive, so the data is safe and a reinstall doesn't represent as much of a problem as it would otherwise. Reinstalling is a no-no in the linux ecosphere, is the last resort for the brave and valiants riders (just kidding :-P)... and in this case I'm afraid you won't obtain any gain in doing it. You better hang in there and try to solve the mistery by yourself :-) I understand, but I notice things like the port light on a the laptop's ethernet outlet doesn't seem as busy as it should be and I suspect that, in an eight year old laptop, the main-board may have problems. This is beyond the Lone Ranger, or even the Silver Surfer to solve with a script or two. Regards, Weaver -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On 16 August 2011 22:12, Camaleón noela...@gmail.com wrote: On Tue, 16 Aug 2011 06:18:01 +1000, Heddle Weaver wrote: On 16 August 2011 05:51, Camaleón noela...@gmail.com wrote: How about a simple wget 192.168.1.254? weaver@Bandit:~$ su Password: Bandit:/home/weaver# wget 192.168.1.254 --2011-08-16 06:06:49-- http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. --2011-08-16 06:07:36-- (try: 2) http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. --2011-08-16 06:08:23-- (try: 3) http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. Hum... are you sure your router is still at 192.168.1.254? Now I'm getting this from /sbin/ifconfig: Bandit:/home/weaver# /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:15:60:c2:63:46 inet6 addr: fe80::215:60ff:fec2:6346/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:358255 errors:0 dropped:0 overruns:0 frame:0 TX packets:198906 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:486741086 (464.1 MiB) TX bytes:19033571 (18.1 MiB) Interrupt:16 loLink 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:240 errors:0 dropped:0 overruns:0 frame:0 TX packets:240 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:20313 (19.8 KiB) TX bytes:20313 (19.8 KiB) ppp0 Link encap:Point-to-Point Protocol inet addr:110.174.203.247 P-t-P:10.20.21.36 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:14792 errors:0 dropped:0 overruns:0 frame:0 TX packets:21 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:1526259 (1.4 MiB) TX bytes:1260 (1.2 KiB) ppp1 Link encap:Point-to-Point Protocol inet addr:110.174.203.247 P-t-P:10.20.21.36 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:332680 errors:0 dropped:0 overruns:0 frame:0 TX packets:190996 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:475301403 (453.2 MiB) TX bytes:13559111 (12.9 MiB) And I can't see the address anywhere. Also, according to the manual, the mask address is supposed to be 225.25.225.0 There is something evil happening. I can't actually remember adjusting anything, yet the connection, far from good, is the best I've had so far. Regards, Weaver. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On Tue, 16 Aug 2011 06:18:01 +1000, Heddle Weaver wrote: On 16 August 2011 05:51, Camaleón noela...@gmail.com wrote: How about a simple wget 192.168.1.254? weaver@Bandit:~$ su Password: Bandit:/home/weaver# wget 192.168.1.254 --2011-08-16 06:06:49-- http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. --2011-08-16 06:07:36-- (try: 2) http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. --2011-08-16 06:08:23-- (try: 3) http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. Hum... are you sure your router is still at 192.168.1.254? (...) I think I have messed up my install inadvertently, in a way that the fact that it is SID doesn't account for. Really, I can't see how your network configuration can be a problem here. If you have setup static values for your NIC and you can ping/reach your DSL router you should get the same you get when using a Windows client. There is no more magic behind an ethernet device and that's precisely its best bet: it works regardless the OS and does not require for special drivers :-) I'm thinking it must be something under the network config. Something in the O.S. itself that has come adrift. I'll try a reinstall. My /home partition is on an external drive, so the data is safe and a reinstall doesn't represent as much of a problem as it would otherwise. Reinstalling is a no-no in the linux ecosphere, is the last resort for the brave and valiants riders (just kidding :-P)... and in this case I'm afraid you won't obtain any gain in doing it. You better hang in there and try to solve the mistery by yourself :-) 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/pan.2011.08.16.12.12...@gmail.com
Re: Fwd: Billion 7800N
On Mon, 15 Aug 2011 06:28:26 +1000, Heddle Weaver wrote: On 14 August 2011 14:42, Heddle Weaver weaver2wo...@gmail.com wrote: On 13 August 2011 01:44, Camaleón noela...@gmail.com wrote: After configuring the modem through XP laptop, I can now access the net through my Debian laptop. The connection is very glitchy - lots of 'time-outs' - but a definite improvement. At least I have access. I'll just have to iron out the bugs, now, but it's been quite a different experience. Here would appear to be the problem. I can access the net. Some sites I have absolutely no problem with and others just time out. This is with bookmarks I've had regular and unimpeded access to in the past. Timeouts for some sites may require more debugging. A site can be having any problem or your ISP may be having a routing issue with that specific server... hard to tell what can be happening. If using Firefox, you can just disable ipv6 because some sites become painfully slow when this is enabled (about:config → filter by ipv6 → and set network.dns.disableIPv6 to true). After that, restart Firefox/ Iceweasel. And I *still *can't access the modem interface in Debian. So, it's looking like a system glitch still. This is what puzzles me because I definitely see no (good|logical) reason for not getting access to the web interface from Debian. Ethernet is one of the most standarized technologies out there so I dunno what can be happening with that DSL modem. Have you tried to get access by telnet (telnet 192.168.1.254). Some routers do also allow to be managed in this way :-? 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/pan.2011.08.15.11.34...@gmail.com
Re: Fwd: Billion 7800N
On Monday 15 August 2011 12:34:59 Camaleón wrote: This is what puzzles me because I definitely see no (good|logical) reason for not getting access to the web interface from Debian. Ethernet is one of the most standarized technologies out there so I dunno what can be happening with that DSL modem. What browser are you using? I have come across problems accessing the web interface of a router with Iceweasel/Firefox. Rarely, but I have come across the problem. Lisi -- 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/201108151722.28219.lisi.re...@gmail.com
Re: Fwd: Billion 7800N
On Mon, 15 Aug 2011 17:22:28 +0100, Lisi wrote: On Monday 15 August 2011 12:34:59 Camaleón wrote: This is what puzzles me because I definitely see no (good|logical) reason for not getting access to the web interface from Debian. Ethernet is one of the most standarized technologies out there so I dunno what can be happening with that DSL modem. What browser are you using? I have come across problems accessing the web interface of a router with Iceweasel/Firefox. Rarely, but I have come across the problem. Yes! :-) In fact I was remembering the problem you experienced months ago and so I mentioned an alternative to bypass anything that can be related to the browser and could be making noise here, like accessing via telnet. 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/pan.2011.08.15.16.30...@gmail.com
Re: Fwd: Billion 7800N
On 15 August 2011 21:34, Camaleón noela...@gmail.com wrote: On Mon, 15 Aug 2011 06:28:26 +1000, Heddle Weaver wrote: On 14 August 2011 14:42, Heddle Weaver weaver2wo...@gmail.com wrote: On 13 August 2011 01:44, Camaleón noela...@gmail.com wrote: After configuring the modem through XP laptop, I can now access the net through my Debian laptop. The connection is very glitchy - lots of 'time-outs' - but a definite improvement. At least I have access. I'll just have to iron out the bugs, now, but it's been quite a different experience. Here would appear to be the problem. I can access the net. Some sites I have absolutely no problem with and others just time out. This is with bookmarks I've had regular and unimpeded access to in the past. Timeouts for some sites may require more debugging. A site can be having any problem or your ISP may be having a routing issue with that specific server... hard to tell what can be happening. debian.org Al Jazeera English Oxford Dictionaries Online My ISP's home page Just for a few examples. This is not the connection, because I get other pages consistently, but these I am unable to gain access to at all over many attempts. If using Firefox, you can just disable ipv6 because some sites become painfully slow when this is enabled (about:config → filter by ipv6 → and set network.dns.disableIPv6 to true). After that, restart Firefox/ Iceweasel. And I *still *can't access the modem interface in Debian. So, it's looking like a system glitch still. This is what puzzles me because I definitely see no (good|logical) reason for not getting access to the web interface from Debian. Ethernet is one of the most standarized technologies out there so I dunno what can be happening with that DSL modem. Have you tried to get access by telnet (telnet 192.168.1.254). Some routers do also allow to be managed in this way :-? weaver@Bandit:~$ su Password: Bandit:/home/weaver# telnet 192.168.1.254 Trying 192.168.1.254... telnet: Unable to connect to remote host: Connection timed out Bandit:/home/weaver# The latest hint is this pop-up when the browser is loading: Unexpected error updating default notary_list from web: [Exception... Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDataSignatureVerifier.verifyData] nsresult: 0x80004005 (NS_ERROR_FAILURE) location: JS frame :: chrome://perspectives/content/common.js :: TOP_LEVEL :: line 185 data: no] At this stage, I don't think there's anything wrong with the modem. Especially when it is considered that: - This is another new modem, as an exchange for another new one of the same type that I got the same behaviour from; - These modems are noted as being a good model; - I have been able to get an immediate connection to the modem from another laptop with M$'s XP. I think I have messed up my install inadvertently, in a way that the fact that it is SID doesn't account for. Thanks for your attempts. Regards, Weaver. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On Tue, 16 Aug 2011 03:56:46 +1000, Heddle Weaver wrote: On 15 August 2011 21:34, Camaleón noela...@gmail.com wrote: Timeouts for some sites may require more debugging. A site can be having any problem or your ISP may be having a routing issue with that specific server... hard to tell what can be happening. debian.org Al Jazeera English Oxford Dictionaries Online My ISP's home page Just for a few examples. This is not the connection, because I get other pages consistently, but these I am unable to gain access to at all over many attempts. For that failing sites you can run the typical network tests, like a traceroute, a ping, a dns resolution... also, try with different browsers (Opera, Firefox and Chrome) and you can even use an online proxy. And I *still *can't access the modem interface in Debian. So, it's looking like a system glitch still. This is what puzzles me because I definitely see no (good|logical) reason for not getting access to the web interface from Debian. Ethernet is one of the most standarized technologies out there so I dunno what can be happening with that DSL modem. Have you tried to get access by telnet (telnet 192.168.1.254). Some routers do also allow to be managed in this way :-? weaver@Bandit:~$ su Password: Bandit:/home/weaver# telnet 192.168.1.254 Trying 192.168.1.254... telnet: Unable to connect to remote host: Connection timed out Bandit:/home/weaver# Okay, so it seems there is no telnet service available in route :-) How about a simple wget 192.168.1.254? The latest hint is this pop-up when the browser is loading: Unexpected error updating default notary_list from web: [Exception... Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDataSignatureVerifier.verifyData] nsresult: 0x80004005 (NS_ERROR_FAILURE) location: JS frame :: chrome://perspectives/content/common.js :: TOP_LEVEL :: line 185 data: no] Looks like a javascript error/warning but not enough to tell if just this can prevent the whole page from loading :-? At this stage, I don't think there's anything wrong with the modem. Especially when it is considered that: - This is another new modem, as an exchange for another new one of the same type that I got the same behaviour from; - These modems are noted as being a good model; - I have been able to get an immediate connection to the modem from another laptop with M$'s XP. I think I have messed up my install inadvertently, in a way that the fact that it is SID doesn't account for. Really, I can't see how your network configuration can be a problem here. If you have setup static values for your NIC and you can ping/reach your DSL router you should get the same you get when using a Windows client. There is no more magic behind an ethernet device and that's precisely its best bet: it works regardless the OS and does not require for special drivers :-) 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/pan.2011.08.15.19.51...@gmail.com
Re: Fwd: Billion 7800N
On 16 August 2011 05:51, Camaleón noela...@gmail.com wrote: On Tue, 16 Aug 2011 03:56:46 +1000, Heddle Weaver wrote: On 15 August 2011 21:34, Camaleón noela...@gmail.com wrote: Okay, so it seems there is no telnet service available in route :-) How about a simple wget 192.168.1.254? weaver@Bandit:~$ su Password: Bandit:/home/weaver# wget 192.168.1.254 --2011-08-16 06:06:49-- http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. --2011-08-16 06:07:36-- (try: 2) http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. --2011-08-16 06:08:23-- (try: 3) http://192.168.1.254/ Connecting to 192.168.1.254:80... failed: Connection timed out. Retrying. The latest hint is this pop-up when the browser is loading: Unexpected error updating default notary_list from web: [Exception... Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDataSignatureVerifier.verifyData] nsresult: 0x80004005 (NS_ERROR_FAILURE) location: JS frame :: chrome://perspectives/content/common.js :: TOP_LEVEL :: line 185 data: no] Looks like a javascript error/warning but not enough to tell if just this can prevent the whole page from loading :-? At this stage, I don't think there's anything wrong with the modem. Especially when it is considered that: - This is another new modem, as an exchange for another new one of the same type that I got the same behaviour from; - These modems are noted as being a good model; - I have been able to get an immediate connection to the modem from another laptop with M$'s XP. I think I have messed up my install inadvertently, in a way that the fact that it is SID doesn't account for. Really, I can't see how your network configuration can be a problem here. If you have setup static values for your NIC and you can ping/reach your DSL router you should get the same you get when using a Windows client. There is no more magic behind an ethernet device and that's precisely its best bet: it works regardless the OS and does not require for special drivers :-) I'm thinking it must be something under the network config. Something in the O.S. itself that has come adrift. I'll try a reinstall. My /home partition is on an external drive, so the data is safe and a reinstall doesn't represent as much of a problem as it would otherwise. Regards, Weaver. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On 14 August 2011 14:42, Heddle Weaver weaver2wo...@gmail.com wrote: On 13 August 2011 01:44, Camaleón noela...@gmail.com wrote: After configuring the modem through XP laptop, I can now access the net through my Debian laptop. The connection is very glitchy - lots of 'time-outs' - but a definite improvement. At least I have access. I'll just have to iron out the bugs, now, but it's been quite a different experience. Here would appear to be the problem. I can access the net. Some sites I have absolutely no problem with and others just time out. This is with bookmarks I've had regular and unimpeded access to in the past. And I *still *can't access the modem interface in Debian. So, it's looking like a system glitch still. Regards, Weaver. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On 13 August 2011 01:44, Camaleón noela...@gmail.com wrote: On Fri, 12 Aug 2011 10:51:25 +1000, Heddle Weaver wrote: On 11 August 2011 00:01, Camaleón noela...@gmail.com wrote: then point your web browser to http://192.168.1.254;. With two separate browsers, the same message - Network is unreachable Restarted the modem, same result. (...) That's very weird... can you access to that same IP (192.168.1.254) from another computer in the network? I'm afraid that is the network. Just a laptop and the modem. It would be nice if you can bring up another computer and connect it to the same switch to verify if it works or not. I've even borrowed a card and tried a connection through 'eth1' to avoid any port problem potentials also. No different reaction. I assume you have one computer that is connected to one of the ethernet ports of the router, right? Yes. If that's the case, and you already reviewed all of the external symptoms (e.g., network sockets blink when a cable is attached in both ends) there can be happening one of these situations: - The router has no DHCP server enabled and it is configured to listen in another IP address that you don't remember. It's brand new and never been configured before. If this is the case, a reset could be the fatest way to recover from this but be careful with resetting because it can delete your ISP connection settings, so if you are not sure what data do you require to setup your WAN interface, call to service support so thay can guide you -step by step- with a reset procedure. Another option can be also to use a network device discover tool (like angry ip scanner) to find whee is your router located. - The router is locked/blocked somehow and does not respond to pings. Try by power cycling it and check if you can now reach it. yes,I've tried all this, swapped cables everything. - The router can be broken, request for a replacement. No, at least part of the router is fine. I've just borrowed somebodies XP laptop and been able to establish a wireless connection that I'm sending this on. I've got a new (well, new, secondhand) laptop coming in a fortnight. I might have to hang out till then. Thanks. Regards, Weaver. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On 13 August 2011 01:44, Camaleón noela...@gmail.com wrote: After configuring the modem through XP laptop, I can now access the net through my Debian laptop. The connection is very glitchy - lots of 'time-outs' - but a definite improvement. At least I have access. I'll just have to iron out the bugs, now, but it's been quite a different experience. Regards, Weaver. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On Fri, 12 Aug 2011 10:51:25 +1000, Heddle Weaver wrote: On 11 August 2011 00:01, Camaleón noela...@gmail.com wrote: then point your web browser to http://192.168.1.254;. With two separate browsers, the same message - Network is unreachable Restarted the modem, same result. (...) That's very weird... can you access to that same IP (192.168.1.254) from another computer in the network? I'm afraid that is the network. Just a laptop and the modem. It would be nice if you can bring up another computer and connect it to the same switch to verify if it works or not. I've even borrowed a card and tried a connection through 'eth1' to avoid any port problem potentials also. No different reaction. I assume you have one computer that is connected to one of the ethernet ports of the router, right? If that's the case, and you already reviewed all of the external symptoms (e.g., network sockets blink when a cable is attached in both ends) there can be happening one of these situations: - The router has no DHCP server enabled and it is configured to listen in another IP address that you don't remember. If this is the case, a reset could be the fatest way to recover from this but be careful with resetting because it can delete your ISP connection settings, so if you are not sure what data do you require to setup your WAN interface, call to service support so thay can guide you -step by step- with a reset procedure. Another option can be also to use a network device discover tool (like angry ip scanner) to find whee is your router located. - The router is locked/blocked somehow and does not respond to pings. Try by power cycling it and check if you can now reach it. - The router can be broken, request for a replacement. 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/pan.2011.08.12.15.44...@gmail.com
Re: Fwd: Billion 7800N
On 11 August 2011 00:01, Camaleón noela...@gmail.com wrote: snip then point your web browser to http://192.168.1.254;. With two separate browsers, the same message - Network is unreachable Restarted the modem, same result. (...) That's very weird... can you access to that same IP (192.168.1.254) from another computer in the network? I'm afraid that is the network. Just a laptop and the modem. I've even borrowed a card and tried a connection through 'eth1' to avoid any port problem potentials also. No different reaction. Thanks. Regards, Weaver -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On Wed, 10 Aug 2011 12:47:06 +1000, Heddle Weaver wrote: On 9 August 2011 18:51, Darac Marjal mailingl...@darac.org.uk wrote: Here's your problem. eth0 has no address. The only IPv4 connectivity you have is to 127.0.0.1/255.0.0.0 via lo (below). Your computer has no way to reach 192.168.1.254 so is legitimately returning Network is unreachable. Try the following command: # ip addr add 192.168.1.1 broadcast 192.168.1.255 dev eth0 Done! and /sbin/ifconfig now looks like this: (...) then point your web browser to http://192.168.1.254;. With two separate browsers, the same message - Network is unreachable Restarted the modem, same result. (...) That's very weird... can you access to that same IP (192.168.1.254) from another computer in the network? 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/pan.2011.08.10.14.01...@gmail.com
Re: Fwd: Billion 7800N
On Tue, Aug 09, 2011 at 02:53:16PM +1000, Heddle Weaver wrote: On 9 August 2011 01:37, Camaleón [1]noela...@gmail.com wrote: On Mon, 08 Aug 2011 13:14:29 +1000, Heddle Weaver wrote: (...) Tried to ping and tcptraceroute with the only reaction either way 'No network present'. Then you seem to have a network configuration problem. Your router should be configured as stated by the manual and you have to configure your network interface with an IP in the same network so you can reach it. Show us the output of /sbin/ifconfig and then what you get after a ping. Bandit:/sbin# ./ifconfig eth0    Link encap:Ethernet  HWaddr 00:15:60:c2:63:46       inet6 addr: fe80::215:60ff:fec2:6346/64 Scope:Link      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1      RX packets:14321 errors:0 dropped:737 overruns:0 frame:0      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0      collisions:0 txqueuelen:1000      RX bytes:1694113 (1.6 MiB)  TX bytes:0 (0.0 B)      Interrupt:16 Here's your problem. eth0 has no address. The only IPv4 connectivity you have is to 127.0.0.1/255.0.0.0 via lo (below). Your computer has no way to reach 192.168.1.254 so is legitimately returning Network is unreachable. Try the following command: # ip addr add 192.168.1.1 broadcast 192.168.1.255 dev eth0 then point your web browser to http://192.168.1.254;. As Camaléon and others have pointed out, you need to have an address on the same subnet as your router to be able to talk to it. Often, this is done with DHCP, but you may not have that set up if you've previously configured the router. 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:146783 errors:0 dropped:0 overruns:0 frame:0      TX packets:146783 errors:0 dropped:0 overruns:0 carrier:0      collisions:0 txqueuelen:0      RX bytes:11620515 (11.0 MiB)  TX bytes:11620515 (11.0 MiB) And weaver@Bandit:~$ ping 192.168.1.254 connect: Network is unreachable -- Paul Saunders signature.asc Description: Digital signature
Re: Fwd: Billion 7800N
On 9 August 2011 18:51, Darac Marjal mailingl...@darac.org.uk wrote: Here's your problem. eth0 has no address. The only IPv4 connectivity you have is to 127.0.0.1/255.0.0.0 via lo (below). Your computer has no way to reach 192.168.1.254 so is legitimately returning Network is unreachable. Try the following command: # ip addr add 192.168.1.1 broadcast 192.168.1.255 dev eth0 Done! and /sbin/ifconfig now looks like this: Bandit:/home/weaver# /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:15:60:c2:63:46 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.255 inet6 addr: fe80::215:60ff:fec2:6346/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:143 errors:0 dropped:0 overruns:0 frame:0 TX packets:113 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:21888 (21.3 KiB) TX bytes:21435 (20.9 KiB) Interrupt:16 loLink 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:12246 errors:0 dropped:0 overruns:0 frame:0 TX packets:12246 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:955628 (933.2 KiB) TX bytes:955628 (933.2 KiB) then point your web browser to http://192.168.1.254;. With two separate browsers, the same message - Network is unreachable Restarted the modem, same result. As Camaléon and others have pointed out, you need to have an address on the same subnet as your router to be able to talk to it. Often, this is done with DHCP, but you may not have that set up if you've previously configured the router. This is brand new. The second one after I took the first one back, thinking it had a firmware problem. Thanks. Regards, Weaver. -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On Mon, 08 Aug 2011 13:14:29 +1000, Heddle Weaver wrote: (...) Tried to ping and tcptraceroute with the only reaction either way 'No network present'. Then you seem to have a network configuration problem. Your router should be configured as stated by the manual and you have to configure your network interface with an IP in the same network so you can reach it. Show us the output of /sbin/ifconfig and then what you get after a ping. 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/pan.2011.08.08.15.37...@gmail.com
Re: Fwd: Billion 7800N
On 9 August 2011 01:37, Camaleón noela...@gmail.com wrote: On Mon, 08 Aug 2011 13:14:29 +1000, Heddle Weaver wrote: (...) Tried to ping and tcptraceroute with the only reaction either way 'No network present'. Then you seem to have a network configuration problem. Your router should be configured as stated by the manual and you have to configure your network interface with an IP in the same network so you can reach it. Show us the output of /sbin/ifconfig and then what you get after a ping. Bandit:/sbin# ./ifconfig eth0 Link encap:Ethernet HWaddr 00:15:60:c2:63:46 inet6 addr: fe80::215:60ff:fec2:6346/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14321 errors:0 dropped:737 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1694113 (1.6 MiB) TX bytes:0 (0.0 B) Interrupt:16 loLink 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:146783 errors:0 dropped:0 overruns:0 frame:0 TX packets:146783 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:11620515 (11.0 MiB) TX bytes:11620515 (11.0 MiB) And weaver@Bandit:~$ ping 192.168.1.254 connect: Network is unreachable weaver@Bandit:~$ It's almost to the stage of being of 'no never-mind'. I have to do a 'Windows' install for this course coming up anyway. I've just done one and got away with everything with using LibreOffice instead and they were over the moon with all the great work I did with 'Word' This should be kept as an example of how it should be done, etc. but this time I have to use a programme that rides on M$ only, so I'll get that down and convert it over later. I was going to do a 20GB Debian partition after the Windows install, so a new install was going to be necessary anyway. The knowledge would be good though. I'm just beginning to edge under the surface and configure files directly and finding out how many gui apps I can get rid of. I'm finding it quite an enjoyable process. Cheers, Weaver -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On 6 August 2011 01:25, Gavin Elliot Jones ga...@grassfield.co.uk wrote: I'm not sure I understand when you mean was it detected during the install procedure. What I was asking was if it was detected during a new install of Debian, or was it connected to an already established O.S.? For the 7800N there wasn't anything to install. I simply plugged the rounter into the power adapter then connected a laptop directly to it via an ethernet port. If I remember correctly I had to manually set the laptops IP address to initially talk to the 7800N in order to turn on the DHCP server. Once that was done I connected the 7800N to my network and all my computers were able to communicate just fine. I can't get anywhere near it to configure anything. It's looking as though I have a bug of some sort in the operating system. I might have to try a new install. Looks like the only option left. Tried to ping and tcptraceroute with the only reaction either way 'No network present'. Long process getting back to SID with a Lenny disc. Thanks for your help. Regards, Weaver -- Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. — Lucius Annæus Seneca. Terrorism, the new religion.
Re: Fwd: Billion 7800N
On Fri, Aug 05, 2011 at 11:52:41AM +1000, Heddle Weaver wrote: Did you get your modem installed onto an already established O.S. or was it detected during the install procedure. My /home is on an external expansion drive and I'm considering a re-install if that detection procedure would pick it up. I'm sure that once it had been detected, there'd be no further problems. Thanks, Weaver. I'm not sure I understand when you mean was it detected during the install procedure. For the 7800N there wasn't anything to install. I simply plugged the rounter into the power adapter then connected a laptop directly to it via an ethernet port. If I remember correctly I had to manually set the laptops IP address to initially talk to the 7800N in order to turn on the DHCP server. Once that was done I connected the 7800N to my network and all my computers were able to communicate just fine. Gavin -- 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/20110805152553.ga3...@grassfield.co.uk
