On Thu, 27 Nov 2003 23:17, you wrote: > First things first: > > Quoting Christopher Sawtell <[EMAIL PROTECTED]>: > > On Tue, 25 Nov 2003 23:19, you wrote: > > > This is the results I got - and I still couldn't connect to any site. > > > > > > Wesley Parish > > > > Would you be so kind as to remind me of a few pertinent facts:- > > Which distribution you are using? > > Mandrake 9.2 I have heard from the rumour mill that this was flushed out the door in only 3 weeks from code freeze to "ready". That's just not long enough. I suspect that they wanted to get a new point version into the shops in time for Christmas. So much for the Linux motto of "It'll be ready when it's done". Mandrake are stuck into it right up to their necks financially and I'm sure the temptation to cut corners is intense.
> > Did these problems suddenly start one day after everything worked fine? > > No, I installed it after getting into my machine one day and putting in one > disk while taking one out. I had problems with the file systems, etc, but > that was simply a misstep on my part. I've been unable to connect to the > paradise http and pop3 sites ever since. > > > Or have you never had networking going propherly at all? > > Networking was going fine with 9.0 and 9.1 - apart from that time this year > when I couldn't connect to slashdot.org, etc. > > > Did you install with the security level set to paranoid? > > I started installing to Higher, but switched back to Normal. Oh dear. I think what has happened is that the software for iptables has been installed but the tables files have not been installed correctly. Thus everything is blocked. There will a file in the /etc/rc.d neck of the woods which sets up the ip-tables filter system. I suspect that it is not properly set up. > > > > ifconfig -a > > > > > > eth0 Link encap:Ethernet HWaddr 00:02:44:25:70:7F > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > > TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 > > > collisions:0 txqueuelen:100 > > > RX bytes:0 (0.0 b) TX bytes:2394 (2.3 Kb) > > > Interrupt:10 Base address:0x4000 > > > > I notice that you have not allocated an address to this interface. > > It is therefore strange that it claims to be UP. > > I realise that you probably are not using it, but you _might_ get a > > solution > > to the problem if you were to give it a number from one of the private > > netblocks perhaps something like 10.11.12.13 > > The command to do this is:- > > ifconfig eth0 10.11.12.13 > > > > That command will give the interface the number until you reboot. > > To make the change permanent you will have to alter the config files for > > you > > dist. in the time honoured way using a text editor or alternatively the > > GUI > > gizmolackey which comes with your distribution. > > I tried this, still no luck. > > <snip> > > > > > cat /etc/resolve.conf > > > > > > domain paradise.net.nz #kppp temp entry > > > ##search net.nz > > > > Could you, in addition, try these commands;- > > ping -c2 127.0.0.1 # This proves that networking is installed > > ping -c2 localhost # This proves that local name resolution works > > it works. The rest didn't - or at least, not yet. Ah, so the built-in firewall code stops _everything_ getting out. > > ping -c2 <the address given to ppp0> > > > > i.e. quoting from the ppp0 config above > > inet addr:210.246.28.17 but we want the new number which is given to you > > for > > the current session. > > > > ping -c2 <the address at the other end of the p-to-p>. > > P-t-P:202.0.46.83 but you should use the new number which is given to > > you for > > the current session. > > > > ping -c2 <one of the numbers of the name server given to you for the > > session> > > > > You will find this in the /etc/resolve.conf file > > > > Once you have got this far, you have an ip network route to the outside > > world. > > > > Test with full names instead of the numbers:- > > > > ping -c2 rachel.paradise.net.nz > > ping -c2 kirsty.paradise.net.nz > > > > or, if your allegeancies lie elsewhere:- > > > > ping -c2 alien.xtra.co.nz > > ping -c2 terminator.xtra.co.nz > > I've just recently bought myself a somewhat bigger hard drive anyway, so I > think I might well move home over to it, and reinstall 9.2, and take it > from there. With any luck, it'll be up and running as good as new. I'd suggest that unless there is a good and positive reason to install Mdk-9.2 that you stay away from it until its been hammered on a bit more. > Thanks for all the help you've been - I appreciate it. NP. I'd suggest that you bring the machine into the club night on the next meeting evening and I'm sure somebody will either be able to get it to go, or to definitively tell you to back up your precious data and re-install from scratch. > Anyone got any ideas on how well BTC Combos work under Linux? I have no idea, sorry. [ ... ] -- Sincerely etc. Christopher Sawtell NB. This PC runs Linux. If you find a virus apparently from me, it has forged the e-mail headers on someone else's machine. Please do not notify me when this occurs. Thanks.
