PDA

View Full Version : can someone explain this error message. (Linux)



Clueless
11-01-2003, 07:39 PM
"Connection to host chatf1.net.nz is broken"

This is the error i almost always see as i enter Liams chatroom. It seems that there is no problem, as i can proceed as normal anyway.

However i would really like to know what it means.

Browser=konqueror
OS=Linux, SuSE8

.Clueless

Clueless
12-01-2003, 12:34 AM
Further investigating!

The penny dropped. i only get this error when i type "<alt>+<f2>" to get a commandline box, <C> autocomplete makes that into "chatf1.net.nz", enter. This is how i allways start CF1

This opens a fresh window for CF1s login screen.
This explains why i only get this for CF1
It does not explain what the message ACTUALLY means (if anything)

.Clueless

Graham L
12-01-2003, 03:15 PM
It might mean that when you start the process, the connection is broken ... it hasn't been made yet. Then, very shortly, the connection is made. But, as always: have a look at "tail -20 /var/log/messages". :D

Clueless
12-01-2003, 08:02 PM
Well i decided to set it up deliberatly..
I went to Cf1s start page, got the error, and entered "tail -20 /var/log/messages" into Konsole

Heres the output, it doesnt seem to have anything to do with the error, it does however reveal my nickname to you all. I'll just stay confused for a bit longer over this one.

hippy@sam:~> tail -20 /var/log/messages
Jan 12 19:34:15 sam su: (to root) hippy on /dev/pts/2
Jan 12 19:34:15 sam su: pam_unix2: session started for user root, service su
Jan 12 19:34:15 sam su: pam_unix2: session finished for user root, service su
Jan 12 19:34:15 sam su: (to root) hippy on /dev/pts/2
Jan 12 19:34:15 sam su: pam_unix2: session started for user root, service su
Jan 12 19:34:26 sam kernel: SuSE-FW-DROP-DEFAULT IN=eth1 OUT= MAC=00:60:97:d2:59:de:00:b0:8e:42:77:84:08:00 SRC=211.189.26.130 DST=202.0.37.227 LEN=33 TOS=0x00 PREC=0x00 TTL=115 ID=44020 PROTO=UDP SPT=1165 DPT=1434 LEN=13
Jan 12 19:36:20 sam kernel: SuSE-FW-UNAUTHORIZED-TARGET IN=eth1 OUT= MAC=01:00:5e:00:00:01:00:20:40:74:f1:fd:08:00 SRC=192.168.100.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=0 PROTO=2
Jan 12 19:39:20 sam kernel: SuSE-FW-UNAUTHORIZED-TARGET IN=eth1 OUT= MAC=01:00:5e:00:00:01:00:20:40:74:f1:fd:08:00 SRC=192.168.100.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=0 PROTO=2
Jan 12 19:42:20 sam kernel: SuSE-FW-UNAUTHORIZED-TARGET IN=eth1 OUT= MAC=01:00:5e:00:00:01:00:20:40:74:f1:fd:08:00 SRC=192.168.100.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=0 PROTO=2
Jan 12 19:43:24 sam su: pam_unix2: session finished for user root, service su
Jan 12 19:44:10 sam kdm[7916]: pam_unix2: session finished for user hippy, service xdm
Jan 12 19:44:26 sam kdm[10027]: pam_unix2: session started for user hippy, service xdm
Jan 12 19:45:20 sam kernel: SuSE-FW-UNAUTHORIZED-TARGET IN=eth1 OUT= MAC=01:00:5e:00:00:01:00:20:40:74:f1:fd:08:00 SRC=192.168.100.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=0 PROTO=2
Jan 12 19:48:20 sam kernel: SuSE-FW-UNAUTHORIZED-TARGET IN=eth1 OUT= MAC=01:00:5e:00:00:01:00:20:40:74:f1:fd:08:00 SRC=192.168.100.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=0 PROTO=2
Jan 12 19:50:04 sam kernel: SuSE-FW-DROP-DEFAULT IN=eth1 OUT= MAC=00:60:97:d2:59:de:00:b0:8e:42:77:84:08:00 SRC=61.251.165.113 DST=202.0.37.227 LEN=60 TOS=0x00 PREC=0x20 TTL=51 ID=27466 DF PROTO=TCP SPT=54892 DPT=21 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40101080A86CCD48A0000000001030300)
Jan 12 19:50:07 sam kernel: SuSE-FW-DROP-DEFAULT IN=eth1 OUT= MAC=00:60:97:d2:59:de:00:b0:8e:42:77:84:08:00 SRC=61.251.165.113 DST=202.0.37.227 LEN=60 TOS=0x00 PREC=0x20 TTL=51 ID=27467 DF PROTO=TCP SPT=54892 DPT=21 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40101080A86CCD5B60000000001030300)
Jan 12 19:50:13 sam kernel: SuSE-FW-DROP-DEFAULT IN=eth1 OUT= MAC=00:60:97:d2:59:de:00:b0:8e:42:77:84:08:00 SRC=61.251.165.113 DST=202.0.37.227 LEN=60 TOS=0x00 PREC=0x20 TTL=51 ID=27468 DF PROTO=TCP SPT=54892 DPT=21 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40101080A86CCD80E0000000001030300)
Jan 12 19:50:25 sam kernel: SuSE-FW-DROP-DEFAULT IN=eth1 OUT= MAC=00:60:97:d2:59:de:00:b0:8e:42:77:84:08:00 SRC=61.251.165.113 DST=202.0.37.227 LEN=60 TOS=0x00 PREC=0x20 TTL=51 ID=27469 DF PROTO=TCP SPT=54892 DPT=21 WINDOW=5840 RES=0x00 SYN URGP=0 OPT (020405B40101080A86CCDCBE0000000001030300)
Jan 12 19:51:20 sam kernel: SuSE-FW-UNAUTHORIZED-TARGET IN=eth1 OUT= MAC=01:00:5e:00:00:01:00:20:40:74:f1:fd:08:00 SRC=192.168.100.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=0 PROTO=2
Jan 12 19:54:20 sam kernel: SuSE-FW-UNAUTHORIZED-TARGET IN=eth1 OUT= MAC=01:00:5e:00:00:01:00:20:40:74:f1:fd:08:00 SRC=192.168.100.1 DST=224.0.0.1 LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=0 PROTO=2

agent
12-01-2003, 08:13 PM
Your user name is "hippy" I see...

Graham L
13-01-2003, 02:50 PM
It has a lot to do with that message: It tells you that "SuSe-FW" (presumably, the firewall) has decided that it has seen an UNAUTHORISED TARGET, and disconnected it. It's protecting you. :D Somehow, it must decide to let you live dangerously, anyway.

Clueless
13-01-2003, 03:10 PM
OK... how come this IP 192.168.100.1 keeps coming up in the error, i have no such IP in my network, atleast i thought i didn't!

(I'm starting to get just the slightest grasp on all of this, and fully aware that i have a long way to go, and looking for any of the bits of the jigsaw that make sense)

.Clueless

Graham L
13-01-2003, 03:35 PM
Mmmm. Even more interesting, the destination 224.0.0.1 is "all multicast receivers on this network". ifconfig should show you who is being 192.168.100.1 ... maybe the firewall is multihosted with your main host.

Clueless
13-01-2003, 03:41 PM
>firewall is multihosted with your main host.

?:|

el pardon?

.Clueless

Clueless
13-01-2003, 03:49 PM
"ifconfig" is not a recognised command, nor os ipconfig ( i thought ifconfig might have been a typo)

Me is getting more confused by the moment!

.Clueless

Graham L
13-01-2003, 03:59 PM
ifconfig not recognised???? A quick look on google for "ifconfig suse" found lots of mentions. (MS call their one ipconfig; *nix have ifconfig). Try "man ifconfig" and "which ifconfig". It might be in the root path but not the "user" path?

Multihosting is assigning two (or more) IP addresses to one network card. This might be done when you have a firewall on the same machine as the protected processes, with only one NIC. (Normally a firewall, like a router, uses two NICs so that one is on the Wild World side, and the other is conected to the playpen).

Clueless
13-01-2003, 04:05 PM
(Normally a firewall, like a router, uses two NICs so that one is on the Wild World side, and the other is conected to the playpen).

That is precisly Sams set up, one card goes to the cable modem, the other goes to Vanessa

Got to go out.. will investigate further on return

.Clueless