Hi,
Oliver wrote:
>like you wrote your ip�s under ifconfig, your route.conf should look like
>this:
>is 195.112.*.* your fixed ip? did you use them for your ippp0 or for what?
>then your route.conf should looks like this with your configuration:
>195.112.4.11 0.0.0.0 255.255.255.255 ippp0
>195.112.4.0 0.0.0.0 255.255.255.0 ippp0
No. 195.112.something.something is not my fixed IP. I do not have a fixed IP
The ISP should automatically assign them (that's what I am trying to get
anyway).
When you write (195.112.4.0), could that be (195.112.4.something)?
In /var/log/messages, everytime I connected with 'isdnctrl dial ippp0'
the Local IP address was (195.112.47.something) and the Remote IP address was
(195.112.4.11)
note: the ippp0 is configured (via YaST) with (192.168.0.99) for the Host
and (192.168.0.1) for the point-to-point partner. This is the setup to access
the SuSE server and test the syncPPP connection (I cannot dial the number
provided from the UK so I did not test it that way).
Now by using the same settings (client IP + Server IP) + the correct phone nbr
of my ISP + login + password + nameservers (which I need to double check to see
if they really are 192.112.4.4 & 192.112.4.7) then when I will connect with
'isdnctrl dial ippp0' the ISP will provide dynamic IP addresses.
These dynamic IP addresses are:
client 195.112.47.something (not really important)
Server 195.112.4.11 FIXED, the one I need
Oliver wrote:
>why should ping 192.168.0.1 gives you an answer? where should it be? if
>this ip is on your eth0 you need to configurate it, with yast or
>manually. and then you have to configure your route.conf too like:
>192.168.0.0 0.0.0.0 255.255.255.0 eth0
I do not have any ethernet card. The PC is used as a workstation with only
an external modem and an ELSA QS1000 Pro PCI to connect to the outside world.
I am not using ping properly here, sorry.
Oliver wrote:
>> o 'route' once connected gives me nothing...
>route without "-n" wants to reverse dns-lookups. if you don�t have
>installed a local dns it cannot gives you something if your connection is
>closed. use route -n instead. it will gives you the route with just the
>ip�s and without to reverse nameserver lookups.
Ok. I will try 'route -n'
Oliver wrote:
>> o If I launch Netscape then it does not pick up the connection
>> (actually it tries to look up www.suse.de and stays in that
>> state indefinitely like a big lemon!)
>sure. you wrote you wanna open your connection manually. so you still have
>to do ist before you want to surf with netscape. else you should configure
>your isdn-device with "auto".
No. I launch Netscape after 'isdnctrl dial ippp0' therefore a connection of
some sort was opened (probably with incorrect routing definition..).
That's what I want to do. I want to control all outgoing calls to my ISP.
Oliver wrote:
>> May 12 19:08:07 wallaby kernel: HiSax: Elsa driver Rev. 2.12
>> May 12 19:08:07 wallaby kernel: Elsa: QS 1000 PCI defined at
>> 0xfcec/0xfc00 IRQ 5
>> May 12 19:08:07 wallaby kernel: Elsa: You may have a wrong PCI bios
>> May 12 19:08:07 wallaby kernel: Elsa: If your system hangs now, read
>> May 12 19:08:07 wallaby kernel: Elsa: Documentation/isdn/README.HiSax
>did you read the doc? did you compiled the kernel for yourself? maybe you
>made there a mistake.
The kernel is the SuSE 6.1 kernel with ISDN support (2.2.5 + patch). I did
not change it. It comes straight out from the box.
Oliver wrote:
>> C. Messages when 'isdnctrl hangup ippp0'
>> May 12 21:24:35 wallaby kernel: isdn_net: ippp0: dial rejected:
>> interface not in dialmode `auto', signalling dst_link_failure
>this looks like something wanna reconnect over your isdn-dev. and this
>doesn�t work because you did your device configured for manually-dialing
>and not with "auto". check what and why wanna reconnect.
Yes, but I have no idea what is trying to reconnect :-0
Oliver wrote:
>> F. /etc/Hosts
>> 127.0.0.1 localhost
>> 192.168.0.99 wallaby.primex.co.uk wallaby
>add the ip and name for your provider here!
Knowing that my ISP (server) IP (fixed) is 195.112.4.11 shouldn't the
/etc/hosts look like this:
127.0.0.1 localhost
195.112.4.11 primex.co.uk primex
195.112.47.* wallaby.primex.co.uk wallaby << maybe not necessary??
Oliver wrote:
>>
>>
>> G. /etc/networks
>> loopback 127.0.0.0
>add here primex 195.112.4.0
Would /etc/networks then be:
loopback 127.0.0.0
primex 195.112.4.11
>>
>>
>> H. /etc/resolv.conf
>> search primex.co.uk
>> nameserver 192.112.4.4
>> nameserver 192.112.4.7
>wrong ip-addresses! should be 195.112.4.4 and 195.112.4.7
>both ip�s doesn�t exit. you can check this with nslookup.
Here I will double check whether the name servers IP should be
195.112.4.4 & 195.112.4.7 instead.
>> I. /etc/route.conf
>> 192.168.0.1 0.0.0.0 255.255.255.255 ippp0
>> default 192.168.0.1
>look above what i wrote aboute the routing. you made here a mistake too.
>even you have a fixed ip like 195.112.some.thing or you get a dynamic ip.
>for the last you have also to activate in /etc/rc.config or with yast
>"activating dynamic-ip patch".
Ok. will check "dynamic-ip patch" in /etc/rc.config (but I think I saw
it set as "yes" yesterday).
Then will the /etc/route.conf look like:
195.112.4.11 0.0.0.0 255.255.255.255 ippp0
195.112.47.* 0.0.0.0 255.255.255.0 ippp0
Sorry if I am asking/suggesting silly things. I am just trying to
understand a bit more.
Thanks for any comments, it is greatly appreciated.
Ciao
Fred
