On Thursday 19 September 2002 10:24 pm, Vince Littler wrote:
I have 2 pcs, A and B and a router R. traffic is routed from A to the internet via B acting as a router to R and R routing to an ISDN line. Router R has some capability of operating as a name server on behalf of the internet.
If I telnet R from A or B, it immediately opens the ISDN connection, which I don't want, because it costs. Why is this and how can I stop it?
More info. B has eth0 and eth1 interfaces, and runs SuSE 8.0. It also does OS/2, in which case everything works perfectly. I think ping causes the same problem on Linux, but again not on OS/2.
I am wondering whether Linux sees the connection out and goes sniffing for routing info or Name Server info or some such. If this is the case, I would appreciate knowing what, and how to turn it off.
Any help on this appreciated, so I can complete the migration of B to Linux
TIA
Finally I have solved this one and maybe found a small bug in the host name resolution at the same time. If I do telnet 192.168.1.1 or whatever [by IP address] to my router, it opens an ISDN connection, and takes a number of seconds before opening the telnet session. However, after putting an entry for the router in the hosts table, the telnet session opens immediately whether I use the IP address or the host name, and the router does not connect to outside. So the bug seems to be that if one is invoking telnet with an IP address, it is not recognised as an IP address initially, rather it is treated as a name. First the hosts table is searched and then the DNS on the router, which then presumbly goes to my ISP's DNS which then says rather cleverly 'the IP address for hostname 192.168.1.1 is 192.168.1.1'. So, 1] is this a bug or is it expected behaviour? 2] If it is a bug, what is the correct place to take it? Regards Vince Littler