OpenBSD oddity

[xyyz]

i've noticed a really werid issue. this happens frequently, and usually it fixes itself after about 20 mins or so, but for some reason, my OpenBSD box, which is acting as my firewall, does something where i can't contact my gateway (which is my BEFSR41).

if i manually go in and delete the route (route delete 1.2.3.4) the problem clears up right away.

any ideas on what's causing this?

i'm running 3.5 on this box at the moment.

 

[n0cmonkey]

Update, 3.5 is dead. There's been a LOT of work since then. Hell, there's been a lot of work since 3.7.

 

[xyyz]

i guess this gives me reason to finally get off the ass and update like i should have done a long time ago. i can also drop in two larger capacity drives.

the funny thing is i even bought the 3.6 CD's but left the firewall alone since it was running great.

 

[n0cmonkey]

Originally posted by: xyyz
i guess this gives me reason to finally get off the ass and update like i should have done a long time ago. i can also drop in two larger capacity drives.

the funny thing is i even bought the 3.6 CD's but left the firewall alone since it was running great.

I've done that too, in the past.

There should be some neat improvements, including some fairly big performance increases (hlt hlt bug was kinda icky).

 

[xyyz]

i've upgraded to 3.6 before the 3.7 upgrade, and i'm still having the same problem.

and ideas what's going on?

EDIT.

upgraded to 3.7 and still the same problem.

oh yeah... another thing, ever since the upgrade from 3.5 i can't SSH into the box. the connection isn't refused, it just sits there doing nothing.

 

[imported_Kiwi]

Originally posted by: xyyz
(snip!) OpenBSD box, which is acting as my firewall ...

Not having used a *nix system in maybe 25 years, I probably should be thinking Linux, for all the good that the long-ago stuff I'd gone through with Unix might do for me. But I am developing an interest in using an old Socket A box as a Firewall for my home LAN (still dial-up due to the current high expense of broadband in my area).

Anyone here who can do me a better filtering job than Google, for finding some sites on which to study up on current OpenBSD capabilities, developments, suggestions, etc. etc. , I'd be most grateful for some URL's.

?

 

[The Scientist]

Originally posted by: Kiwi

Originally posted by: xyyz
(snip!) OpenBSD box, which is acting as my firewall ...

Not having used a *nix system in maybe 25 years, I probably should be thinking Linux, for all the good that the long-ago stuff I'd gone through with Unix might do for me. But I am developing an interest in using an old Socket A box as a Firewall for my home LAN (still dial-up due to the current high expense of broadband in my area).

Anyone here who can do me a better filtering job than Google, for finding some sites on which to study up on current OpenBSD capabilities, developments, suggestions, etc. etc. , I'd be most grateful for some URL's.

?

www.openbsd.org click the documentation links, if you have a lot of paper and ink, print it.

OpenBSD is by FAR the best safety link to the net i know of.

If you need to go linux, forget anything but Slackware.

 

[xyyz]

why do threads get hijacked like this?

how about starting your own thread... they're easily done and free.

 

[Sunner]

Weird, been running my OpenBSD box since 2.9 and I've upgraded every few versions.
I've installed a bunch of those for other people as well and have never seen or heard of a problem like this.

Something funny with that Netgear maybe?
Nothing exciting in the system log?

 

[n0cmonkey]

Anything in the logs? Does SSH clear up at all if you restart it?

 

[xyyz]

nothing... unless... well where should i look?

it's still happening even with the 3.7 upgrade.

 

[Sunner]

What error do you get if you try to ping the router by the way?

 

[n0cmonkey]

Look in /var/log/messages for anything wierd.
Try a fresh install of 3.7 and test your ram.

 

[xyyz]

gonna do that tomorrow and see what happens. i'll also give the message.

what i did, and i don't know if it'll work... i put the route delete comand into a file and stuck that as a cronjob that is to run every minute.

 

[n0cmonkey]

I haven't seen anything about problems like this on the mailing lists. I'm wondering if it's an errant cronjob or bad ram or something...

 

[xyyz]

i'm leaning towards fault hardware. i think the internal interface has gone bad or something.

why would faulty ram cause problems on a particular interface?

btw, the cronjob method didn't work. i need to manually delete the route.

 

[n0cmonkey]

Fault ram affects everything, since pretty much every bit goes through ram.

 

[xyyz]

nothing outta the ordinary.

this is what happens when i try pinging from the box itself:


ping 10.10.100.1
PING 10.10.100.1 (10.10.100.1): 56 data bytes
--- 10.10.100.1 ping statistics ---
8 packets transmitted, 0 packets received, 100.0% packet loss


from my winxp box


Pinging 10.10.100.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 10.10.100.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


here's what's in /var/log/messages:


Aug 14 22:00:01 uranus newsyslog[5325]: logfile turned over
Aug 14 22:00:01 uranus syslogd: restart
Aug 15 14:00:01 uranus syslogd: restart
Aug 15 15:17:16 uranus reboot: rebooted by austin
Aug 15 15:17:20 uranus syslogd: exiting on signal 15
Aug 15 15:17:20 uranus syslogd: exiting on signal 15
Aug 15 15:18:15 uranus syslogd: restart
Aug 15 15:18:15 uranus /bsd: syncing disks... done
Aug 15 15:18:15 uranus /bsd: console is /sbus@1f,0/zs@f,1100000:a
Aug 15 15:18:15 uranus /bsd: Copyright (c) 1982, 1986, 1989, 1991, 1993
Aug 15 15:18:15 uranus /bsd: The Regents of the University of California. All rights reserved.
Aug 15 15:18:15 uranus /bsd: Copyright (c) 1995-2004 OpenBSD. All rights reserved. http://www.OpenBSD.org
Aug 15 15:18:16 uranus /bsd: Copyright (c) 1995-2004 OpenBSD. All rights reserved. http://www.OpenBSD.org
Aug 15 15:18:16 uranus /bsd: OpenBSD 3.6 (GENERIC) #304: Fri Sep 17 13:01:33 MDT 2004
Aug 15 15:18:16 uranus /bsd: deraadt@sparc64.openbsd.org:/usr/src/sys/arch/sparc64/compile/GENERIC
Aug 15 15:18:16 uranus /bsd: total memory = 67108864
Aug 15 15:18:16 uranus /bsd: avail memory = 48275456
Aug 15 15:18:16 uranus /bsd: using 409 buffers containing 3350528 bytes of memory
Aug 15 15:18:16 uranus /bsd: bootpath: /sbus@1f,0/SUNW,fas@e,8800000/sd@1,0
Aug 15 15:18:16 uranus /bsd: mainbus0 (root): Sun Ultra 1 UPA/SBus (UltraSPARC 200MHz)
Aug 15 15:18:16 uranus /bsd: cpu0 at mainbus0: SUNW,UltraSPARC @ 199.955 MHz, version 0 FPU
Aug 15 15:18:16 uranus /bsd: cpu0: physical 32K instruction (32 b/l), 16K data (32 b/l), 512K external (64 b/l)
Aug 15 15:18:16 uranus /bsd: timer0 at mainbus0 addr 0xfffc7c00 irq vectors 7f0 and 7f1
Aug 15 15:18:16 uranus /bsd: sbus0 at mainbus0 addr 0xfffcc000: clock = 25 MHz
Aug 15 15:18:16 uranus /bsd: STC0 on /mainbus enabled
Aug 15 15:18:16 uranus /bsd: DVMA map: ff800000 to ffffe000
Aug 15 15:18:17 uranus /bsd: IOTDB: 307ea000 to 307ec000
Aug 15 15:18:17 uranus /bsd: audiocs0 at sbus0 slot 13 offset 0xc000000 vector 24 ipl 13
Aug 15 15:18:17 uranus /bsd: audio0 at audiocs0
Aug 15 15:18:17 uranus /bsd: auxio0 at sbus0 slot 15 offset 0x1900000
Aug 15 15:18:17 uranus /bsd: flashprom at sbus0 slot 15 offset 0x0 not configured
Aug 15 15:18:17 uranus /bsd: SUNW,fdtwo at sbus0 class block slot 15 offset 0x1400000 vector 29 ipl 11 not configured
Aug 15 15:18:17 uranus /bsd: clock0 at sbus0 slot 15 offset 0x1200000: mk48t59: hostid 80817eeb
Aug 15 15:18:17 uranus /bsd: zs0 at sbus0 slot 15 offset 0x1100000 vector 28 ipl 12 softpri 6
Aug 15 15:18:17 uranus /bsd: zstty0 at zs0 channel 0 (console i/o)
Aug 15 15:18:17 uranus /bsd: zstty1 at zs0 channel 1
Aug 15 15:18:17 uranus /bsd: zs1 at sbus0 slot 15 offset 0x1000000 vector 28 ipl 12 softpri 6
Aug 15 15:18:17 uranus /bsd: zskbd0 at zs1 channel 0: reset timeout
Aug 15 15:18:17 uranus /bsd: zskbd0: no keyboard
Aug 15 15:18:17 uranus /bsd: zstty2 at zs1 channel 1, mouse
Aug 15 15:18:17 uranus /bsd: uperf0 at sbus0 slot 15 offset 0x1300000: model SUNW,sc-up (0/0) ports 3
Aug 15 15:18:17 uranus /bsd: SUNW,pll at sbus0 slot 15 offset 0x1304000 not configured
Aug 15 15:18:17 uranus /bsd: esp0 at sbus0 slot 14 offset 0x8800000 vector 20 ipl 3: dma rev fas
Aug 15 15:18:18 uranus /bsd: esp0: FAS366/HME, 40MHz, SCSI ID 7
Aug 15 15:18:18 uranus /bsd: scsibus0 at esp0: 8 targets
Aug 15 15:18:18 uranus /bsd: sd0 at scsibus0 targ 1 lun 0: <SEAGATE, ST32171W SUN2.1G, 7462> SCSI2 0/direct fixed
Aug 15 15:18:18 uranus /bsd: sd0: 2029MB, 2735 cyl, 19 head, 80 sec, 512 bytes/sec, 4157201 sec total
Aug 15 15:18:18 uranus /bsd: cd0 at scsibus0 targ 6 lun 0: <TOSHIBA, CD-ROM XM-5401TA, 3605> SCSI2 5/cdrom removable
Aug 15 15:18:18 uranus /bsd: hme0 at sbus0 slot 14 offset 0x8c00000 vector 21 ipl 6: address 08:00:20:81:7e:eb
Aug 15 15:18:18 uranus /bsd: nsphy0 at hme0 phy 1: DP83840 10/100 media interface, rev. 0
Aug 15 15:18:18 uranus /bsd: SUNW,bpp at sbus0 slot 14 offset 0xc800000 vector 22 ipl 2 not configured
Aug 15 15:18:18 uranus /bsd: hme1 at sbus0 slot 1 offset 0x8c00000 vector 4 ipl 6: address 08:00:20:8a5:a0
Aug 15 15:18:18 uranus /bsd: qsphy0 at hme1 phy 1: QS6612 10/100 media interface, rev. 1
Aug 15 15:18:18 uranus /bsd: hme2 at sbus0 slot 1 offset 0x8c10000 vector 4 ipl 6: address 08:00:20:8a5:a1
Aug 15 15:18:18 uranus /bsd: qsphy1 at hme2 phy 1: QS6612 10/100 media interface, rev. 1
Aug 15 15:18:18 uranus /bsd: hme3 at sbus0 slot 1 offset 0x8c20000 vector 4 ipl 6: address 08:00:20:8a5:a2
Aug 15 15:18:18 uranus /bsd: qsphy2 at hme3 phy 1: QS6612 10/100 media interface, rev. 1
Aug 15 15:18:18 uranus /bsd: hme4 at sbus0 slot 1 offset 0x8c30000 vector 4 ipl 6: address 08:00:20:8a5:a3
Aug 15 15:18:18 uranus /bsd: qsphy3 at hme4 phy 1: QS6612 10/100 media interface, rev. 1
Aug 15 15:18:18 uranus /bsd: creator0 at mainbus0 addr 0xfec00000: Creator3D, model SUNW,501-2633, dac 10
Aug 15 15:18:18 uranus /bsd: wsdisplay0 at creator0
Aug 15 15:18:18 uranus /bsd: wsdisplay0: screen 0 added (std, sun emulation)
Aug 15 15:18:18 uranus /bsd: pcons at mainbus0 not configured
Aug 15 15:18:18 uranus /bsd: root on sd0a
Aug 15 15:18:19 uranus /bsd: rootdev=0x700 rrootdev=0x1100 rawdev=0x1102
Aug 15 15:18:18 uranus savecore: no core dump
Aug 15 15:36:11 uranus reboot: rebooted by austin
Aug 15 15:36:15 uranus syslogd: exiting on signal 15
Aug 15 15:36:15 uranus syslogd: exiting on signal 15
Aug 15 16:09:52 uranus syslogd: restart
Aug 15 16:09:52 uranus /bsd: syncing disks...
Aug 15 16:09:54 uranus savecore: no core dump
Aug 15 17:00:01 uranus syslogd: restart

(snip... the exact same everyday)

Sep 11 21:00:02 uranus syslogd: restart


*scratches head*

how can i test the ram?

EDIT...

i noticed that that message file shows the device to be a 3.6 machine... but it's a 3.7 machine.


OpenBSD 3.7 (GENERIC) #431: Sun Mar 20 14:10:02 MST 2005

 

[Sunner]

Good way to test the RAM is with Memtest86.

As for 3.6 vs 3.7, is that an upgraded box or a fresh 3.7 install?
Supposedly very strange things can happen if you do an upgrade and mess up somewhere along the way, for example mismatching userland and kernel.

Oh yeah, have you tried swapping interfaces?
Looks like you have 5 happy meal interfaces in there, hme's are junk.

 

[n0cmonkey]

Originally posted by: Sunner
Good way to test the RAM is with Memtest86.

Does that work with Sparc systems?

 

[n0cmonkey]

Originally posted by: xyyz
i noticed that that message file shows the device to be a 3.6 machine... but it's a 3.7 machine.


OpenBSD 3.7 (GENERIC) #431: Sun Mar 20 14:10:02 MST 2005

Yeah, I'd try a reinstall to see if that helps at all. Make sure to backup the important files (pf.conf, hostname.if, etc).

 

[Sunner]

Originally posted by: n0cmonkey

Originally posted by: Sunner
Good way to test the RAM is with Memtest86.

Does that work with Sparc systems?

DOH!

(And to think, I even saw that it was a SPARC...brain fart deluxe...)

 

[xyyz]

it was an upgrade from 3.5 to 3.6 then to 3.7

ad you beat me to it... i was gonna ask if it would work on the sparc architecture.

*sigh* i so didn't wanna do a fresh reinstall, but i'm willing to try anything.