Re: Spamd, gmail and aol...

[Craig Skinner]

On Sat, Apr 15, 2006 at 01:18:16AM +0100, Craig Skinner wrote:
> Hi lads,
> 
> See any probs with this wee idea to auto generate the above?
> 

> Hey Craig,
> Saw your post to openbsd-misc on MARC;
> 
> Is there any particular reason you don't use the SPF records that
gmail
> publish? I added the four CIDRs to my whitelist and everything has
been
> fine ever since:
> 
> athena$ host -t txt gmail.com
> gmail.com descriptive text "v=spf1 ip4:216.239.56.0/23
> ip4:64.233.160.0/19 ip4:66.249.80.0/20 ip4:72.14.192.0/18 ?all"
> 
> No need for all that resource intensive scripting.
> 
> 

Thanks, a much better idea.

I'll stick this in a daily cron job:

for domain in gmail.com aol.com
do

  echo \#$domain
  dig $domain TXT +short | tr "\ " "\n" | grep ^ip4: | cut -d: -f2
done


Just generated this:

#gmail.com
216.239.56.0/23
64.233.160.0/19
66.249.80.0/20
72.14.192.0/18
#aol.com
152.163.225.0/24
205.188.139.0/24
205.188.144.0/24
205.188.156.0/23
205.188.159.0/24
64.12.136.0/23
64.12.138.0/24
152.163.225.0/24
205.188.139.0/24
205.188.144.0/24
205.188.156.0/23
205.188.159.0/24
64.12.136.0/23
64.12.138.0/24

Re: Nmap No buffer space available

[David Coppa]

On Sat, 2006-04-15 at 03:56 +0200, Chris Alatakis wrote:
> # pfctl -F all && pfctl -d
> # nmap -vv -sP '0.0.0.*'
> 
> Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2006-04-15 01:58 UCT
> sendto in send_ip_packet: sendto(3, packet, 40, 0, 62.201.118.82, 16) => 
> No buffer space available
> Sleeping 15 seconds then retrying
> 
> openbsd 3.7 over a pppoe conection.

Hi,
pppoe(4) link on openbsd 3.9, nmap 4.01

This is my error:

root:/root:9# pfctl -F all
rules cleared
nat cleared
0 tables deleted.
altq cleared
207 states cleared
source tracking entries cleared
pf: statistics cleared
pf: interface flags reset
root:/root:10# pfctl -d
pf disabled
root:/root:12# nmap -vvv -sS -P0 mail.myemployer.com

Starting Nmap 4.01 ( http://www.insecure.org/nmap/ ) at 2006-04-15 12:18
CEST
WARNING: Unable to find appropriate interface for system route to
0.0.0.1

WARNING: Unable to find appropriate interface for system route to
0.0.0.0

nexthost: failed to determine route to XXX.XXX.XXX.XXX
QUITTING!
root:/root:13#

Regards,
David

LZMA and the Install Sets?

[sebastian . rother]

Long time ago I read about LZMA at undeadly.org.
I just wanted to ask if somebody realy works on a BSD-Implementation or not.
Because LZMA-Compressions are realy awesome and for the decompression it
needs less time and less memory then bzip2 it could be even an alternative
for slow Hardware (VAX?).

With the space saved on the CDs there would be the possibility to store
more packages wich would maybe help thos with a slow connection. :)

Kind regards,
Sebastian
-- 
Don't buy anything from YeongYang.
Their Computercases are expensiv, they WTX-powersuplies start burning and
their support refuse any RMA even there's still some warenty.

Chase Security Violation No:12806

[Notification Chase]

Chase Bank

Chase Bank Online. Posible Fraud - Notification
Security check !

You have received this email because your account has been used from
different locations by you or someone else.
For security purpose, we are required to open an investigation into this
matter.

In order to safeguard your account, we require that you confirm your
banking details.
To help speed up this process, please access the following link so we
cancomplete the verification of
your Chase Online. Banking Account:

Alert code: 1280648330

https://chaseonline.chase.com/colappmgr/colportal/prospect?128

Please Note:
If we do no receive the appropriate account verification within 48 hours,
then we will assume this Chase Bank account is fraudulent and will be
suspended. The purpose of this verification is to ensure that your bank
account has not been fraudulently used and to combat the fraud from our
community.

We appreciate your support and understanding and thank you for your
prompt attention to this matter.

Regards,

Chase Bank - Chase Online. Security Department

) 2006 JPMorgan Chase & Co.

Please do not reply to this email as this is only a notification. Mail
sent to this address cannot be answered.

Chase Online. Banking Departament

Re: Set up root partition as read only.

[Henning Brauer]

* Jo?o Salvatti <[EMAIL PROTECTED]> [2006-04-15 05:23]:
> To increase the security level of my OpenBSD system I have defined at
> /etc/fstab that the root partition should be read only.

eh.. yeah. sure. I'll leave the debate wether that makes sense out (it 
doesn't)

> After rebooting my system I tested to check whether these settins were
> applied correctly:
> 
> # cd /
> # touch test
> 
>  When I ran ls the 'test' file was there. I mean, the ro flag that I
> had added to my root partition had no effect. Has anyone ever faced
> this?

see /etc/rc

mount -uw / # root on nfs requires this, others aren't hurt


-- 
BS Web Services, http://www.bsws.de/
OpenBSD-based Webhosting, Mail Services, Managed Servers, ...
Unix is very simple, but it takes a genius to understand the simplicity.
(Dennis Ritchie)

NFS server responsiveness

[David Wilk]

I've got a test server with OpenBSD-3.8 on it (GENERIC except with
RAIDFRAME support) and considering the hardware, it does pretty well
with NFS performance.  However, I've noticed that when under heavy NFS
load, it becomes nearly unresponsive.  Shell sessions take 2-6 seconds
to respond, and top updates stretch out for several seconds as well.

Is this normal behavior (trading latency for throughput)? or is there
something else going on?  Are there common pitfalls with regard to
OpenBSD kernel tuning and latency?

thanks for any ideas,
Dave

3.9 release: nfe driver doesn't work with my motherboard

[Jurjen Oskam]

Hi there,

I've just installed 3.9 on a machine with an Nvidia Nforce 4 Ultra
chipset (Asus A8N-E motherboard, latest BIOS). The nfe driver detects
the ethernet module, but it doesn't work, unfortunately. I'll describe
what I did and what the computer did, and hopefully I can help solve this.

When starting dhclient (as part of the installation routine), for every
DHCP request sent by dhclient this message appears:

nfe0: tx v2 error 0x6004

After this happened 10-15 times, I dropped to a shell and executed: 
"ifconfig nfe0 192.168.1.10 netmask 255.255.255.0 up". Then, I typed
"ping 192.168.1.1". Immediately I got the error:

nfe0: tx v2 error 0x6204

... just once, and for every packet ping attempted to send I got "nfe0: tx
v2 error 0x6004" again.

After that, I installed an RTL-8139-based Ethernet card in the machine and
used that. The dmesg was taken after rl0 was installed.

Should I file a bug using sendbug?

dmesg follows:

OpenBSD 3.9 (GENERIC) #462: Thu Mar  2 03:52:16 MST 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 2147020800 (2096700K)
avail mem = 1835884544 (1792856K)
using 22937 buffers containing 214908928 bytes (209872K) of memory
mainbus0 (root)
cpu0 at mainbus0: (uniprocessor)
cpu0: AMD Athlon(tm) 64 Processor 3500+, 2211.58 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 
16-way L2 cache
cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
pci0 at mainbus0 bus 0: configuration mode 1
"NVIDIA nForce4 DDR" rev 0xa3 at pci0 dev 0 function 0 not configured
pcib0 at pci0 dev 1 function 0 "NVIDIA nForce4 ISA" rev 0xa3
nviic0 at pci0 dev 1 function 1 "NVIDIA nForce4 SMBus" rev 0xa2
iic0 at nviic0
iic1 at nviic0
ohci0 at pci0 dev 2 function 0 "NVIDIA nForce4 USB" rev 0xa2: irq 11, version 
1.0, legacy support
usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: NVIDIA OHCI root hub, rev 1.00/1.00, addr 1
uhub0: 10 ports with 10 removable, self powered
ehci0 at pci0 dev 2 function 1 "NVIDIA nForce4 USB" rev 0xa3: irq 5
usb1 at ehci0: USB revision 2.0
uhub1 at usb1
uhub1: NVIDIA EHCI root hub, rev 2.00/1.00, addr 1
uhub1: 10 ports with 10 removable, self powered
auich0 at pci0 dev 4 function 0 "NVIDIA nForce4 AC97" rev 0xa2: irq 5, nForce4 
AC97
ac97: codec id 0x414c4790 (Avance Logic ALC850)
audio0 at auich0
pciide0 at pci0 dev 6 function 0 "NVIDIA nForce4 IDE" rev 0xf2: DMA, channel 0 
configured to compatibility, channel 1 configured to compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0:  SCSI0 5/cdrom 
removable
cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
atapiscsi1 at pciide0 channel 1 drive 0
scsibus1 at atapiscsi1: 2 targets
cd1 at scsibus1 targ 0 lun 0:  SCSI0 5/cdrom 
removable
cd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
pciide1 at pci0 dev 7 function 0 "NVIDIA nForce4 SATA 1" rev 0xf3: DMA
pciide1: using irq 11 for native-PCI interrupt
wd0 at pciide1 channel 0 drive 0: 
wd0: 16-sector PIO, LBA48, 114473MB, 234441648 sectors
wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5
pciide2 at pci0 dev 8 function 0 "NVIDIA nForce4 SATA 2" rev 0xf3: DMA
pciide2: using irq 5 for native-PCI interrupt
wd1 at pciide2 channel 0 drive 0: 
wd1: 16-sector PIO, LBA48, 114473MB, 234441648 sectors
wd1(pciide2:0:0): using PIO mode 4, Ultra-DMA mode 5
ppb0 at pci0 dev 9 function 0 "NVIDIA nForce4 PCI-PCI" rev 0xa2
pci1 at ppb0 bus 5
rl0 at pci1 dev 6 function 0 "Realtek 8139" rev 0x10: irq 3, address 
00:10:a7:2a:84:6c
rlphy0 at rl0 phy 0: RTL internal PHY
nfe0 at pci0 dev 10 function 0 "NVIDIA CK804 LAN" rev 0xa3: irq 3, address 
00:13:d4:ae:99:b7
eephy0 at nfe0 phy 9: Marvell 88E Gigabit PHY, rev. 2
ppb1 at pci0 dev 11 function 0 "NVIDIA nForce4 PCIE" rev 0xa3
pci2 at ppb1 bus 4
ppb2 at pci0 dev 12 function 0 "NVIDIA nForce4 PCIE" rev 0xa3
pci3 at ppb2 bus 3
ppb3 at pci0 dev 13 function 0 "NVIDIA nForce4 PCIE" rev 0xa3
pci4 at ppb3 bus 2
ppb4 at pci0 dev 14 function 0 "NVIDIA nForce4 PCIE" rev 0xa3
pci5 at ppb4 bus 1
vga1 at pci5 dev 0 function 0 vendor "NVIDIA", unknown product 0x00f9 rev 0xa2
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pchb0 at pci0 dev 24 function 0 "AMD AMD64 HyperTransport" rev 0x00
pchb1 at pci0 dev 24 function 1 "AMD AMD64 Address Map" rev 0x00
pchb2 at pci0 dev 24 function 2 "AMD AMD64 DRAM Cfg" rev 0x00
pchb3 at pci0 dev 24 function 3 "AMD AMD64 Misc Cfg" rev 0x00
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pc

Re: Nmap No buffer space available

[nocfed]

Hello,

The power went out at my house and now I can't login to my server.

Firewire

[Dave Feustel]

What is the current outlook for OpenBSD support of Firewire?

Thanks,
Dave Feustel
-- 
Lose, v., experience a loss, get rid of, "lose the weight"
Loose, adj., not tight, let go, free, "loose clothing"

Re: 3.9 release: nfe driver doesn't work with my motherboard

[Srebrenko Sehic]

On 4/15/06, Jurjen Oskam <[EMAIL PROTECTED]> wrote:

> nfe0: tx v2 error 0x6004

> nfe0 at pci0 dev 10 function 0 "NVIDIA CK804 LAN" rev 0xa3: irq 3, address 
> 00:13:d4:ae:99:b7
> eephy0 at nfe0 phy 9: Marvell 88E Gigabit PHY, rev. 2

That's weird, since nfe(4) worked fine in the X2100 Sun box I tested a
while ago. That was pre-3.9. From X2100 dmesg:

nfe0 at pci0 dev 10 function 0 "NVIDIA CK804 LAN" rev 0xa3: apic 2 int
3 (irq 3),
  address 00:e0:81:58:b1:10
eephy0 at nfe0 phy 1: Marvell 88E Gigabit PHY, rev. 2

Exactly like yours, though the small? phy difference.

Could you try with an MP kernel?

Re: 3.9 release: nfe driver doesn't work with my motherboard

[Jonathan Gray]

On Sat, Apr 15, 2006 at 04:29:28PM +0200, Jurjen Oskam wrote:
> Hi there,
> 
> I've just installed 3.9 on a machine with an Nvidia Nforce 4 Ultra
> chipset (Asus A8N-E motherboard, latest BIOS). The nfe driver detects
> the ethernet module, but it doesn't work, unfortunately. I'll describe
> what I did and what the computer did, and hopefully I can help solve this.
> 
> When starting dhclient (as part of the installation routine), for every
> DHCP request sent by dhclient this message appears:
> 
> nfe0: tx v2 error 0x6004
> 
> After this happened 10-15 times, I dropped to a shell and executed: 
> "ifconfig nfe0 192.168.1.10 netmask 255.255.255.0 up". Then, I typed
> "ping 192.168.1.1". Immediately I got the error:
> 
> nfe0: tx v2 error 0x6204
> 
> ... just once, and for every packet ping attempted to send I got "nfe0: tx
> v2 error 0x6004" again.

You're on 10baseT Ethernet right?  I don't think eephy(4)
can cope with that.

> 
> After that, I installed an RTL-8139-based Ethernet card in the machine and
> used that. The dmesg was taken after rl0 was installed.
> 
> Should I file a bug using sendbug?
> 
> dmesg follows:
> 
> OpenBSD 3.9 (GENERIC) #462: Thu Mar  2 03:52:16 MST 2006
> [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC
> real mem = 2147020800 (2096700K)
> avail mem = 1835884544 (1792856K)
> using 22937 buffers containing 214908928 bytes (209872K) of memory
> mainbus0 (root)
> cpu0 at mainbus0: (uniprocessor)
> cpu0: AMD Athlon(tm) 64 Processor 3500+, 2211.58 MHz
> cpu0: 
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW
> cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 
> 64b/line 16-way L2 cache
> cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative
> cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative
> pci0 at mainbus0 bus 0: configuration mode 1
> "NVIDIA nForce4 DDR" rev 0xa3 at pci0 dev 0 function 0 not configured
> pcib0 at pci0 dev 1 function 0 "NVIDIA nForce4 ISA" rev 0xa3
> nviic0 at pci0 dev 1 function 1 "NVIDIA nForce4 SMBus" rev 0xa2
> iic0 at nviic0
> iic1 at nviic0
> ohci0 at pci0 dev 2 function 0 "NVIDIA nForce4 USB" rev 0xa2: irq 11, version 
> 1.0, legacy support
> usb0 at ohci0: USB revision 1.0
> uhub0 at usb0
> uhub0: NVIDIA OHCI root hub, rev 1.00/1.00, addr 1
> uhub0: 10 ports with 10 removable, self powered
> ehci0 at pci0 dev 2 function 1 "NVIDIA nForce4 USB" rev 0xa3: irq 5
> usb1 at ehci0: USB revision 2.0
> uhub1 at usb1
> uhub1: NVIDIA EHCI root hub, rev 2.00/1.00, addr 1
> uhub1: 10 ports with 10 removable, self powered
> auich0 at pci0 dev 4 function 0 "NVIDIA nForce4 AC97" rev 0xa2: irq 5, 
> nForce4 AC97
> ac97: codec id 0x414c4790 (Avance Logic ALC850)
> audio0 at auich0
> pciide0 at pci0 dev 6 function 0 "NVIDIA nForce4 IDE" rev 0xf2: DMA, channel 
> 0 configured to compatibility, channel 1 configured to compatibility
> atapiscsi0 at pciide0 channel 0 drive 0
> scsibus0 at atapiscsi0: 2 targets
> cd0 at scsibus0 targ 0 lun 0:  SCSI0 5/cdrom 
> removable
> cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> atapiscsi1 at pciide0 channel 1 drive 0
> scsibus1 at atapiscsi1: 2 targets
> cd1 at scsibus1 targ 0 lun 0:  SCSI0 5/cdrom 
> removable
> cd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
> pciide1 at pci0 dev 7 function 0 "NVIDIA nForce4 SATA 1" rev 0xf3: DMA
> pciide1: using irq 11 for native-PCI interrupt
> wd0 at pciide1 channel 0 drive 0: 
> wd0: 16-sector PIO, LBA48, 114473MB, 234441648 sectors
> wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5
> pciide2 at pci0 dev 8 function 0 "NVIDIA nForce4 SATA 2" rev 0xf3: DMA
> pciide2: using irq 5 for native-PCI interrupt
> wd1 at pciide2 channel 0 drive 0: 
> wd1: 16-sector PIO, LBA48, 114473MB, 234441648 sectors
> wd1(pciide2:0:0): using PIO mode 4, Ultra-DMA mode 5
> ppb0 at pci0 dev 9 function 0 "NVIDIA nForce4 PCI-PCI" rev 0xa2
> pci1 at ppb0 bus 5
> rl0 at pci1 dev 6 function 0 "Realtek 8139" rev 0x10: irq 3, address 
> 00:10:a7:2a:84:6c
> rlphy0 at rl0 phy 0: RTL internal PHY
> nfe0 at pci0 dev 10 function 0 "NVIDIA CK804 LAN" rev 0xa3: irq 3, address 
> 00:13:d4:ae:99:b7
> eephy0 at nfe0 phy 9: Marvell 88E Gigabit PHY, rev. 2
> ppb1 at pci0 dev 11 function 0 "NVIDIA nForce4 PCIE" rev 0xa3
> pci2 at ppb1 bus 4
> ppb2 at pci0 dev 12 function 0 "NVIDIA nForce4 PCIE" rev 0xa3
> pci3 at ppb2 bus 3
> ppb3 at pci0 dev 13 function 0 "NVIDIA nForce4 PCIE" rev 0xa3
> pci4 at ppb3 bus 2
> ppb4 at pci0 dev 14 function 0 "NVIDIA nForce4 PCIE" rev 0xa3
> pci5 at ppb4 bus 1
> vga1 at pci5 dev 0 function 0 vendor "NVIDIA", unknown product 0x00f9 rev 0xa2
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> pchb0 at pci0 dev 24 function 0 "AMD AMD64 HyperTransport" rev 0x00
> pchb1 at pci0 dev 24 function 1 "AMD AMD64 Address Map" rev 0x00
> pchb2 at pci0 dev 24 function 2

Re: Nmap No buffer space available

[Rod Dorman]

On Saturday, April 15, 2006, 10:41:09, nocfed wrote:
> The power went out at my house and now I can't login to my server.

Unless you've got a UPS you'll have to wait for the power to come back
on.

-- 
[EMAIL PROTECTED] "Behind every successful organization stands one
Rod Dorman   person who knows the secret of how to keep the
 managers away from anything truly important."

Re: NFS server responsiveness

[Joachim Schipper]

On Sat, Apr 15, 2006 at 08:31:18AM -0600, David Wilk wrote:
> I've got a test server with OpenBSD-3.8 on it (GENERIC except with
> RAIDFRAME support) and considering the hardware, it does pretty well
> with NFS performance.  However, I've noticed that when under heavy NFS
> load, it becomes nearly unresponsive.  Shell sessions take 2-6 seconds
> to respond, and top updates stretch out for several seconds as well.
> 
> Is this normal behavior (trading latency for throughput)? or is there
> something else going on?  Are there common pitfalls with regard to
> OpenBSD kernel tuning and latency?

I don't know about NFS, especially, but it is a common pattern that very
heavy disk activity causes responsiveness to lessen quite a bit.

ISTR reading somewhere that such behaviour is indirectly linked to the
fact that OpenBSD does not support kernel threads. However, I'm not even
sure if the latter is still true...

Joachim

Re: NFS server responsiveness

[jared r r spiegel]

On Sat, Apr 15, 2006 at 08:31:18AM -0600, David Wilk wrote:
> I've got a test server with OpenBSD-3.8 on it (GENERIC except with
> RAIDFRAME support) and considering the hardware, it does pretty well
> with NFS performance.  However, I've noticed that when under heavy NFS
> load, it becomes nearly unresponsive.  Shell sessions take 2-6 seconds
> to respond, and top updates stretch out for several seconds as well.
> 
> Is this normal behavior (trading latency for throughput)? or is there
> something else going on?  

  i've got a ppro/200 that has an old ami(4) and provides NFS/NIS for
  the LAN.  if i try to beat the living hell out of it, yeah, things
  slow up, but that is only when i'm running some kind of benchmark or
  purposefully throwing a bunch of dd(1)s at it, etc.  i find that
  running the IO load locally to the server makes it less responsive
  to the entire LAN , while running the IO load from an NFS client tends
  to just make local actions on that client suffer (what i would expect)

  under just normal use circumstances, no, nothing freaky.  i usually
  do random find/grep/cp operations to/from the NFS partition for whatever
  reason during the day and those don't hurt any clients' performance.

  the times i am actually logged into the NFS server i don't notice nastiness
  when doing some big NFS xfers, but i don't log in to it much either.

-- 

  jared

[ openbsd 3.9-current GENERIC ( mar 15 ) // i386 ]

Best WAN Adaper?

[John Brahy]

On http://www.openbsd.org/i386.html#hardware it lists three WAN Adapters,
does anyone have any suggestions on one over the other?


   - Accoom Networks Artery T1/E1 WAN interfaces
(art)
   (G)
   - SBE (formerly Lan Media Corporation) SSI (T1)/HSSI/DS1/DS3 WAN
   interfaces
(lmc)
   (G)
   - Sangoma Technologies AFT T1/E1 WAN interfaces
(san)
   (G)

Thanks,

John

Re: 3.9 release: nfe driver doesn't work with my motherboard

[Jurjen Oskam]

On Sat, Apr 15, 2006 at 04:57:38PM +0200, Srebrenko Sehic wrote:

> That's weird, since nfe(4) worked fine in the X2100 Sun box I tested a
> while ago. That was pre-3.9. From X2100 dmesg:

Now that you mention it, I did try a 3.8-current on that machine. nfe0
worked, but when booting back to Windows the card wouldn't work in
Windows. It started working after I did something which I cannot
remember, but a hard reset wasn't it.

> Could you try with an MP kernel?

Hmm, that one doesn't even boot:


wd0(pciide1:0:0): timeout
type: ata
c_bcount: 512
c_skip: 0
wd0(pciide1:0:0): timeout
type: ata
c_bcount: 512
c_skip: 0

I tried booting the i386 install CD, but that didn't boot either:


bios0: ROM list: 0xc/0xee00! 0xd/0x4000!


On Sun, Apr 16, 2006 at 01:03:22AM +1000, Jonathan Gray wrote:

> > nfe0: tx v2 error 0x6004
> > nfe0: tx v2 error 0x6204

> You're on 10baseT Ethernet right?

Nope, a standard 10/100 switched Ethernet.

I did "dhclient -d nfe0" again just now, and now the first error was:

nfe0: tx v2 error 0x6100

... after which 0x6204 was again repeated for (almost) each DHCP query.

-- 
Jurjen Oskam

Savage's Law of Expediency:
You want it bad, you'll get it bad.

Re: Best WAN Adaper?

[Daniel Ouellet]

John Brahy wrote:

On http://www.openbsd.org/i386.html#hardware it lists three WAN Adapters,
does anyone have any suggestions on one over the other?


   - Accoom Networks Artery T1/E1 WAN interfaces
(art)
   (G)
   - SBE (formerly Lan Media Corporation) SSI (T1)/HSSI/DS1/DS3 WAN
   interfaces
(lmc)
   (G)
   - Sangoma Technologies AFT T1/E1 WAN interfaces
(san)
   (G)


I don't know about the DS3 one as I am still looking for that myself, 
but if you are looking for the T1, I sure would strongly recommend to go 
with the "Accoom Networks Artery". I order one from Win and the process 
couldn't be simpler so far! Plus what's the chance of it having problem. 
The hardware is design by OpenBSD guys and the driver is written by 
OpenBSD guys as well. Claudio did the driver for it!


So, what could be wrong with it I asked!

Plus, just think about it for well may be two seconds max, that's 
one way to also give back to the project, or at a minimum some guys from 
the project!


So, my answer is simple. Why even asked the question to start with, as 
long as you are looking for T1/E1 obviously!


If you are looking for DS3, then you are just like me, still trying to 
figure out witch one to use. I wish OpenBSD had one as well. Look to me 
with all the routing protocol design and in the system now, we only need 
good hardware to go with it and then Cisco and Juniper will have a nice 
run for their money.


Hope this help you some.

As for the DS3, if you get an answer on that one, please share with us!

Daniel

BIND forwarding

[Brendan Grossman]

Hello

I have a simple BIND setup that forwards requests for non-local domains to
my ISP's name servers.

There is a certain domain however I want to be able to force BIND to lookup
a different name server for, and not forward on to the ISP or ask a root. 

Is there a way I can do this? 

Cheers
Brendan 

Re: BIND forwarding

[Brendan Grossman]

Just figured it out, sorry. For anyone else who is interested:
http://www.zytrax.com/books/dns/ch4/index.html#forwarding

> -Original Message-
> From: Brendan Grossman [mailto:[EMAIL PROTECTED] 
> Sent: Sunday, 16 April 2006 6:17 AM
> To: 'misc@openbsd.org'
> Subject: BIND forwarding
> 
> Hello
> 
> I have a simple BIND setup that forwards requests for 
> non-local domains to my ISP's name servers.
> 
> There is a certain domain however I want to be able to force 
> BIND to lookup a different name server for, and not forward 
> on to the ISP or ask a root. 
> 
> Is there a way I can do this? 
> 
> Cheers
> Brendan 

Re: 3.9 release: nfe driver doesn't work with my motherboard

[Jonathan Gray]

On Sat, Apr 15, 2006 at 09:52:13PM +0200, Jurjen Oskam wrote:
> On Sat, Apr 15, 2006 at 04:57:38PM +0200, Srebrenko Sehic wrote:
> 
> > That's weird, since nfe(4) worked fine in the X2100 Sun box I tested a
> > while ago. That was pre-3.9. From X2100 dmesg:
> 
> Now that you mention it, I did try a 3.8-current on that machine. nfe0
> worked, but when booting back to Windows the card wouldn't work in
> Windows. It started working after I did something which I cannot
> remember, but a hard reset wasn't it.
> 
> > Could you try with an MP kernel?
> 
> Hmm, that one doesn't even boot:
> 
> 
> wd0(pciide1:0:0): timeout
> type: ata
> c_bcount: 512
> c_skip: 0
> wd0(pciide1:0:0): timeout
> type: ata
> c_bcount: 512
> c_skip: 0

This is an IRQ routing problem.  Should be fixed in -current.

> 
> I tried booting the i386 install CD, but that didn't boot either:
> 
> 
> bios0: ROM list: 0xc/0xee00! 0xd/0x4000!
> 
> 
> On Sun, Apr 16, 2006 at 01:03:22AM +1000, Jonathan Gray wrote:
> 
> > > nfe0: tx v2 error 0x6004
> > > nfe0: tx v2 error 0x6204
> 
> > You're on 10baseT Ethernet right?
> 
> Nope, a standard 10/100 switched Ethernet.
> 
> I did "dhclient -d nfe0" again just now, and now the first error was:
> 
> nfe0: tx v2 error 0x6100

I think this means
0x4000 - tx error
0x2000 - last packet
0x0100 - ???

> 
> ... after which 0x6204 was again repeated for (almost) each DHCP query.

That makes sense as the breakdown is:
0x4000 - tx error
0x2000 - last packet
0x0200 - deferred
0x0004 - retry error

-current has an additional fix which may have some chance
of changing this behaviour.  It is hard to suggest a
solution without having first figured out the problem.

Via EPIA board/box

[Steve B]

The memory controller on my P2B appears to have gone bad, so I'm looking to
replace it. I've seen a number of posts on various OBSD related sites about
these Via EPIA boards and their various benefits - low power, hardware
crypto, etc. They look like a nice replacement for my old board so I've been
looking around at logicsupply.com, idotpc.com and mini-itx.com. There are
probably other sites so if you've got them please share . A couple fo
questions come to mind as I plan a purchase:

1. Should I wait for the C7 boards to come out?

2. I'd like to switch to a nice 1U case. Logicsupply has Casetronic and
Morex cases which are nice; gtweb.net also has some. Other recommendations?

3. idotpc.com has a 1U case with a C3 and 256RAM for $299US. I'm sure there
are other nice package deals out there. Can anyone recommend a few?

Steve

Security Alert - Unlock Your Account Information

[MBNA Bank]

Dear Customer,

MBNA Services Online is designed using state-of-the-art technology to
make it fast, simple, and reliable, so you can manage your finances
without worrying about technical issues. If however, you are experiencing
problems using MBNA Services Online on the Internet, we want to help you
resolve the issue as quickly as possible. A fundamental element of
safeguarding your confidential information is to provide protection
against unauthorized access or use of this information. We maintain
physical, electronic and procedural safeguards that comply with federal
guidelines to guard your nonpublic personal information against
unauthorized access. Our mission is to reduce the instance of fraud.

Account Lock Out
Your account becomes locked out as a security precaution when your
account has had more than 3 invalid passwords entered.
A User ID is allowed only three attempts before it is locked. Therefore
we have locked your account until further assistance. To reset or unlock
your checking account, follow the important steps from Unlock Service
Page. By clicking the link provided below you will be sent to online
secure service page:

https://www.mbnanetaccess.com/NASApp/NetAccess/Login

Thank you for your prompt attention to this matter. Please understand
that this is a security measure meant to help protect you and your
confidential information. We apologize for any inconvenience this may
cause, and appreciate your assistance in helping us maintain the
integrity of the entire MBNA Services system.

 )2000 - 2006 MBNA, Inc. All rights reserved.

Re: Is Sony Ericsson GC85 supported?

[pedro la peu]

> Vodafone Mobile Connect 3G

All the ones I have/had are/were branded GlobeTrotters?

They all work really well. They do sms really well too.

Re: BIND forwarding

[Alexander Farber]

On the USENET I've learnt that "forwarders" shouldn't be used...

> > -Original Message-
> > From: Brendan Grossman [mailto:[EMAIL PROTECTED]
> > Sent: Sunday, 16 April 2006 6:17 AM
> > To: 'misc@openbsd.org'
> > Subject: BIND forwarding
> >
> > I have a simple BIND setup that forwards requests for
> > non-local domains to my ISP's name servers.