On Monday 24 Aug 2009 11:59:02 Per Jessen wrote:
Peter Nikolic wrote:
Not even sure what to put in a bug report on this one althou it has plaged me for some time i have never found anything in the logs to base a report on other than how it actually appears here
You could always swap out into a console and check your network config. Interface definition, routing, name-server etc. Just use Crlt-Alt-F1. I have my doubts about YaST being to blame here, but if you want to pursue the issue, I think your network config at the time of failure is the first thing to look at.
Not that i am aware of i use suse 10.0 as a firewall / router on a dedicated PC that connects via WiFi to my connection , I then use a local nameserver on the machine with an IP of 192.168.3.1. All internal IP's are 192.168.3.xx the external is 192.168.0.103 (i piggy back on a friends connection with permission saves me the need for a landline and the associated charges) i use an internal Nameserver as i find it better than using the one on his router
Doesn't sound particularly unusual, no.
/Per HI .
I meant to add that when it auto configures the network it always seems to get the IP address of the router at my friends house which does not work thru my firewall router . One of these days i will get round to finding the spanner in the works Pete .