[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SIOCAIFADDR: File Exists on network startup
Sorry for the slow response... :)
I have only guesses at this point. My first guess, isthat the hostname.*
files might be missing some important data (or .. I wonder if any checks
are done on owners/permissions to allow only good data to be read from
there..) -- mine look like this:
# cat /etc/hostname.xl*
inet 192.168.0.1 255.255.255.0 NONE media 100baseTX mediaopt full-duplex
inet 24.20.70.203 255.255.255.128 NONE media autoselect
Perhaps you just need to insert some media information..?
*Maybe* it is barfing on the strange netmask you have assigned for
1.1.1.1 -- maybe it isn't liking the 1.1.1.1 address anyway, figuring it
to be fake. (What if a.root-servers.net wanted to run on OpenBSD, if
this were the case? No, it probably isn't the case.)
But, try using the 10.x.y.z or other reserved ranges of bogus addresses.
:)
No, you shouldn't need to change the /etc/netstart script -- it should
be generic enough for practically everyone. :)
Sadly, looking through the ifconfig source code, I can't figure out what
on earth sets this error off. :-/
best of luck :)
* Roelker, Daniel J. <Daniel.Roelker@jhuapl.edu> [001201 07:12]:
> The default ipf rules are installed.
>
> pass out from any to any
> pass in from any to any
>
> two network interfaces:
>
> hostname.fxp0
> inet 1.1.1.1 255.255.255.0 NONE
> hostname.rl0
> inet 1.1.1.2 255.255.255.0 NONE
>
> I tried changing the netmask on rl0 to 255.255.0.0 and it doesn't give me
> the SIOCAIFADDR: File Exists.
>
> The exact error is on startup:
> starting network
> ifconfig: SIOCAIFADDR: File Exists
>
> As for routing, the routing table only includes routes from the fxp0
> interface. rl0 is shutdown effectively. So it possibly could be a routing
> problem. I haven't changed any of the netstart code, do I need too?
>
> Dan
>
> -----Original Message-----
> From: Seth Arnold [mailto:sarnold@willamette.edu]
> Sent: Friday, December 01, 2000 12:39 AM
> To: Roelker, Daniel J.
> Subject: Re: SIOCAIFADDR: File Exists on network startup
>
>
> dan, could you follow up to the list with your /etc/ipf.rules and
> whatnot?
>
> * Roelker, Daniel J. <Daniel.Roelker@jhuapl.edu> [001130 20:54]:
> > I've changed my network setup to two non-smc nic cards and am getting the
> > same error upon network startup. They both appear to be up and running,
> but
> > the rl0 interface can't communicate with anything. While I can ping it
> > internally, it cannot be pinged externally, for example.
> >
> > Does anyone have any ideas what might be causing this? I've included the
> > dmesg.
> >
> > OpenBSD 2.7-stable (SMAUG) #1: Wed Nov 29 13:48:44 EST 2000
> > root@smaug:/usr/src/sys/arch/i386/compile/SMAUG
> > cpu0: disabling processor serial number
> > cpu0: Intel Pentium III ("GenuineIntel" 686-class, 512KB L2 cache) 601 MHz
> > cpu0:
> >
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SYS,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,
> > SIMD
> > real mem = 133738496 (130604K)
> > avail mem = 119693312 (116888K)
> > using 1658 buffers containing 6791168 bytes (6632K) of memory
> > mainbus0 (root)
> > bios0 at mainbus0: AT/286+(1a) BIOS, date 09/07/00
> > apm0 at bios0: Power Management spec V1.2
> > apm0: AC on, battery charge unknown
> > pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
> > pchb0 at pci0 dev 0 function 0 "VIA VT82C691 (Apollo Pro) Host-PCI" rev
> 0x44
> > ppb0 at pci0 dev 1 function 0 "VIA VT82C598 (Apollo MVP3) PCI-AGP" rev
> 0x00
> > pci1 at ppb0 bus 1
> > "SIS 6326 AGP Video" rev 0x0b at pci1 dev 0 function 0 not configured
> > pcib0 at pci0 dev 7 function 0 vendor "VIA", unknown product 0x596 rev
> 0x23
> > pciide0 at pci0 dev 7 function 1 "VIA VT82C586A IDE" rev 0x10: DMA,
> channel
> > 0 configured to compatibility, channel 1 configured to compatibility
> > wd0 at pciide0 channel 0 drive 0: <ST38410A>
> > wd0: can use 32-bit, PIO mode 4, DMA mode 2, Ultra-DMA mode 2
> > wd0: 32-sector PIO, LBA, 8223MB, 16383 cyl, 16 head, 63 sec, 16841664
> > sectors
> > pciide0: channel 0 interrupting at irq 14
> > wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (using DMA data
> > transfers)
> > atapiscsi0 at pciide0 channel 1
> > scsibus0 at atapiscsi0: 2 targets
> > cd0 at scsibus0 targ 0 lun 0: <E-IDE, CD-ROM 52X/AKH, A60> SCSI0 5/cdrom
> > removable
> > cd0: can use 32-bit, PIO mode 4, DMA mode 2
> > pciide0: channel 1 interrupting at irq 15
> > cd0(pciide0:1:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
> > "VIA VT83C572 USB" rev 0x11 at pci0 dev 7 function 2 not configured
> > pchb1 at pci0 dev 7 function 3 vendor "VIA", unknown product 0x3050 rev
> 0x30
> > fxp0 at pci0 dev 11 function 0 "Intel 82557" rev 0x02: irq 12, address
> > 00:a0:c9:6b:86:6e
> > inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 0
> > rl0 at pci0 dev 12 function 0 "Realtek 8139" rev 0x10: irq 10 address
> > 00:40:33:e2:d5:e6
> > rlphy0 at rl0 phy 0: RTL internal phy
> > isa0 at pcib0
> > isadma0 at isa0
> > lpt0 at isa0 port 0x378/4 irq 7
> > npx0 at isa0 port 0xf0/16: using exception 16
> > pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> > pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
> > vt0 at isa0 port 0x60/16 irq 1: vga 80 col, color, 8 scr, mf2-kbd
> > pms0: irq 12 already in use
> > fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> > fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
> > biomask c040 netmask d440 ttymask d4c2
> > pctr: 686-class user-level performance counters enabled
> > mtrr: Pentium Pro MTRR support
> > dkcsum: wd0 matched BIOS disk 80
> > root on wd0a
> > rootdev=0x0 rrootdev=0x300 rawdev=0x302
> >
> > I'm seriously baffled by this. I've searched man pages, mailing lists.
> If
> > anyone has any ideas . . .
> >
> > Dan
> >
> >
> >
> >
>
> --
> ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all
> really impressed down here, I can tell you.''
--
``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all
really impressed down here, I can tell you.''