And if you use the real dns name, for exemple www.google.com or one other, what is the anserwing. And wget what the command line use ?
---------------------------------------------------------- Rien de grand ne s'est accompli dans le monde sans passion (A.ENGEL) ---------------------------------------------------------- Laurent DIDIER ([EMAIL PROTECTED]) FORLAN (http://www.forlan.com) tél : 03 84 21 00 10 Gsm : 06 80 32 60 43 Fax : 03 84 54 35 50 -----Message d'origine----- De : Gary Stainburn [mailto:[EMAIL PROTECTED] Envoyé : lundi 24 février 2003 11:35 À : [EMAIL PROTECTED]; Laurent didier Objet : Re: Linux Firewall and Cisco Router On Monday 24 February 2003 9:41 am, Laurent didier wrote: qq> have you an DNS resolution No, but that shouldn't matter as I'm using IP address notation, i.e. wget http://10.10.1.100/index.html which relates to the following that I used from the cisco connect 10.10.1.100 80 GET /index.html HTTP 1.0 which returned the page > > ---------------------------------------------------------- > Rien de grand ne s'est accompli dans le monde sans passion (A.ENGEL) > ---------------------------------------------------------- > Laurent DIDIER ([EMAIL PROTECTED]) > FORLAN (http://www.forlan.com) > tél : 03 84 21 00 10 > Gsm : 06 80 32 60 43 > Fax : 03 84 54 35 50 > > -----Message d'origine----- > De : Gary Stainburn [mailto:[EMAIL PROTECTED] > Envoyé : lundi 24 février 2003 10:36 > À : [EMAIL PROTECTED] > Objet : Linux Firewall and Cisco Router > > > Hi folks, > > I don't know if this is a linux problem or a Cisco one. > > I've got a Cisco 801 configured to dial-on-demand to a fleet management > clearing house. If I telnet to the cisco and use the 'connect' command to > pull down a web page it dials out, connects and then returns the web page. > > I've got this attached to a Linux box via a cross-over cable. From the > Linux > box I can telnet to the cisco to program it etc. > > If I use wget to pull down the same web page, the cisco dials out and > connects > fine, but the wget never sees anything, and then times out and tries again. > > Ping and traceroute etc also bring up the line, but I get no ping responses > and the traceroute stops at the Cisco. > > I've tried turning off iptables to see if that fixes it, but it makes no > differqence. > > Anyone got any ideas? -- Gary Stainburn This email does not contain private or confidential material as it may be snooped on by interested government parties for unknown and undisclosed purposes - Regulation of Investigatory Powers Act, 2000 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list