redirecting error on internet access
I am getting an error on one of my internet access points, if you try and access a web page using say iceweasel one gets a delay of around 3 or 4 seconds then an error message is displayed saying something like "Iceweasel has detected the request being redireted to many times and its not likely to succeed, problem could be cured by enabling or disabling cookies or it could be a server error". Anything else such as an ftp transfer simple gets no response. Now I have a small network here one of the machines acting as the internet access point and firewall. The fire wall is just a small script enacting a "don't speak until spoken to" firewall, the script only acting on a single interface ppp0. There are two access points the first is a 3g mobile broadband modem using Virgin, the second a telephone line dial up modem. This is kept as a backup as the the 3g __CANNOT__ be relied on. Both of these are accessed via the "pon" command, only one is ever used at a time, hence only ppp0 is used. The problem __ONLY__ occurs on the 3g broadband access, the land line being quite OK. Anyone have any ideas on this, it would seem to me that virgin network is doing something strange. Lindsay
I am a little surprised considering the knowledge of networks around this list there has been no response, anyway............. I decided to have a look at what was happening on the link through ppp0 to try and isolate the problem. This was done using tcpdump, the output of this showed what was comming out of the nameserver set up on the firewall machine bore no resembelance to the address being requested. I went no further than that. This machine uses pdnsd as a caching nameserver. I assume a problem within the namserver setup would explain why it worked on one destination and not on the other. The firewall machine is now 6 years and 8 months old, using debian 5.?. It has been updated although this was long ago. The above error was the "last straw", the machine has been doing a number of oddish things for a while now and I have decided to drag it into the present. Previous experience shows a machine this old that has not the operating system and related software updated can cause some really wierd problems. I would assume its not the oldest Debian box that has been run daily with out an update but it must be getting up there. The machine itself uses a Gigabyte 6BXD motherboard with a couple of 600 mhz P3's and would be around 12-14 years old, the year 1999 comes to mind as a date on the motherboard. Fans probaly need cleaning also............ Using Linux for over 20 years now. Lindsay
participants (1)
-
Lindsay Sprinter