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 -- Per Jessen, Zürich (15.6°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org