bugGNUstep - Bugs: bug #24693, gdomap failure on netbsd

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #24693: gdomap failure on netbsd

Submitted by:  Riccardo Mottola <rmottola>
Submitted on:  Wed 29 Oct 2008 06:08:58 PM UTC  
 
Category: Base/FoundationSeverity: 2 - Minor
Item Group: Change RequestStatus: Invalid
Privacy: PublicAssigned to: None
Open/Closed: Declined

Wed 11 Feb 2009 11:21:56 PM UTC, comment #3:

it appears to be a kernel bug... I have no further news, I will close the bug for now. I was using a beta kernel. If it will behave the same way when released, we can investigate again.

Riccardo Mottola <rmottola>
Project Member
Tue 16 Dec 2008 08:56:01 AM UTC, comment #2:

I added improved diagnostics logging to gdomap ... does that help explain what's wrong with your system?

Richard Frith-Macdonald <CaS>
Project Member
Wed 29 Oct 2008 06:38:17 PM UTC, comment #1:

This is annoying, but not a major bug ... so I changed this to a minor change request as the program actually tells you the easy workaround.

In practice, to fix it you need a BSD programmer with a BSD system to track down why it can't find/use the network interface on that system (yes, presumably specific to the network hardware/drivers on the system).

Richard Frith-Macdonald <CaS>
Project Member
Wed 29 Oct 2008 06:08:58 PM UTC, original submission:

on my netbsd laptop, when I start gdomap -f it fails with the following messages:

SIOCGIFFLAGS: m
SIOCGIFFLAGS: m
SIOCGIFFLAGS: m
SIOCGIFFLAGS: m
SIOCGIFFLAGS: m
SIOCGIFFLAGS: m
SIOCGIFFLAGS: m
SIOCGIFFLAGS: m
SIOCGIFFLAGS: m
SIOCGIFFLAGS: m
I can't find any network interfaces on this platform - use the '-a' flag to load interface details from a file instead.
exiting.

this is on NetBSD / x86.

Interesting on a different machine, same architecture, I don't experience that problme, so it might be specific to the interfaces available?

ifconfig -a shows:

saruman: {4} ifconfig -a
fwip0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
address: 00:08:02:71:9c:f4:fe:ff
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
capabilities=3f80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx>
enabled=0
address: 00:08:02:f4:70:b0
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 192.168.1.53 netmask 0xffffff00 broadcast 192.168.1.255
inet6 fe80::208:2ff:fef4:70b0%re0 prefixlen 64 scopeid 0x2
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3

maybe it gets confused by fwip0, which is the firewire interface?

Riccardo Mottola <rmottola>
Project Member

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by CaS (Posted a comment)
  • -unavailable- added by rmottola (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 4 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Wed 11 Feb 2009 11:22:57 PM UTCrmottolaStatusNone=>Invalid
      Open/ClosedOpen=>Declined
    Wed 29 Oct 2008 06:38:17 PM UTCCaSSeverity4 - Important=>2 - Minor
      Item GroupBug=>Change Request

    Back to the top


    Powered by Savane 3.1-cleanup1