Lost KInternet after upgrade SuSE 9.1->9.2

I upgraded a SuSE Pro 9.1 system to 9.2 and now cannot access the
Internet with that machine. The KInternet icon briefly shows a
lightning bolt and then reverts to the closed state; nothing is in the
log. A quick test with Kermit gets an un able to connect error message
on the SET LINE command. This doesn't happen if I do a complete
install in another partition.

Could there be something in the upgrade the affects the definition of,
e.g., /dev/ttys0? Any advice on tracking this down and preventing it
the next time? Thanks.

--
Shmuel (Seymour J.) Metz, SysProg and JOAT <http://patriot.net/~shmuel>

Unsolicited bulk E-mail subject to legal action. I reserve the
right to publicly post or ridicule any abusive E-mail. Reply to
domain Patriot dot net user shmuel+news to contact me. Do not
reply to (E-Mail Removed)

On Tue, 28 Dec 2004 12:06:57 -0500, Shmuel (Seymour J.) Metz wrote:
> I upgraded a SuSE Pro 9.1 system to 9.2 and now cannot access the
> Internet with that machine. The KInternet icon briefly shows a
> lightning bolt and then reverts to the closed state; nothing is in the
> log. A quick test with Kermit gets an un able to connect error message
> on the SET LINE command. This doesn't happen if I do a complete
> install in another partition.
>
> Could there be something in the upgrade the affects the definition of,
> e.g., /dev/ttys0? Any advice on tracking this down and preventing it
> the next time? Thanks.

Modem? ISDN? Have you run through the yast2 configuration
for your network connection device after the upgrade? What
happened?

Bjørn
--
Bjørn Tore Sund "When in fear, and when in doubt;
(E-Mail Removed) Run in circles, scream and shout!"
Interaction! - Anonymous
http://www.interaction.worldcon.org.uk/

Bjørn Tore Sund wrote:
> On Tue, 28 Dec 2004 12:06:57 -0500, Shmuel (Seymour J.) Metz wrote:
> > I upgraded a SuSE Pro 9.1 system to 9.2 and now cannot access the
> > Internet with that machine. The KInternet icon briefly shows a
> > lightning bolt and then reverts to the closed state; nothing is in
the
> > log. A quick test with Kermit gets an un able to connect error
message
> > on the SET LINE command. This doesn't happen if I do a complete
> > install in another partition.
> >
> > Could there be something in the upgrade the affects the definition
of,
> > e.g., /dev/ttys0? Any advice on tracking this down and preventing
it
> > the next time? Thanks.
>
> Modem? ISDN? Have you run through the yast2 configuration
> for your network connection device after the upgrade? What
> happened?
>
> Bjørn
> --
> Bjørn Tore Sund "When in fear, and when in doubt;
> (E-Mail Removed) Run in circles, scream and shout!"
> Interaction! - Anonymous
> http://www.interaction.worldcon.org.uk/

I have an even wierder problem. I have a cable connection via
Aldephia.net. today, in th emidst of operations, I lost my internet
connection. The activity light stopped blinking.
I rebooted under Windows 2000 and got a connection. I tried Knoppix 3.7
and no connection. I want back to Knoppix 3.4 and got a connection.
Knoppix 3.4 has th epeculiarity that the eth0 and eth1 cards get
switched compared to Slackware or even Knoppix 3.6 or 3.7.

Anyhow I did an ifconfig anw wrote down the internet address of the
eth1 card, the one that actually connects to the
internet. Then I rebooted Slack 10. ifconfog showed thae same card,
this time as eth0, with the same internet address. But lynx does not
connect. I cannot ping anything under etiher slack 10 partition.
Currently I am running Knoppix 3.4, the only form of linux that I have
that will connect.

PLease give me your best guess. I will check back this evening.
John Culleton
(E-Mail Removed)
69.174.190.44

(E-Mail Removed) wrote:

> Anyhow I did an ifconfig anw wrote down the internet address of the
> eth1 card, the one that actually connects to the
> internet. Then I rebooted Slack 10. ifconfog showed thae same card,
> this time as eth0, with the same internet address. But lynx does not
> connect. I cannot ping anything under etiher slack 10 partition.
> Currently I am running Knoppix 3.4, the only form of linux that I
have
> that will connect.
>
> PLease give me your best guess. I will check back this evening.
> John Culleton
> (E-Mail Removed)
> 69.174.190.44

Found the problem. I have a firewall for my secondary computer. The
commands are in rc.local.
apparently one of the addresses in there is no longer valid (iptables
statement.) so I have to dig back in to the manual and figure out how
to find the current address for iptables.

John Culleton