DragonFlyBSD bugtracker: Issueshttps://bugs.dragonflybsd.org/https://bugs.dragonflybsd.org/favicon.ico?16293952082006-06-28T21:31:11ZDragonFlyBSD bugtracker
Redmine DragonFlyBSD - Bug #219 (Closed): IPFW2 Patch part 1https://bugs.dragonflybsd.org/issues/2192006-06-28T21:31:11Zdragonfly
<p>Hello,</p>
<p>This patch removes ipfw1 in favour of ipfw2. ipfw2 is a superset of <br />ipfw1 and no functionality should be lost. This will make bringing in <br />improvements to ipfw2 from FreeBSD easier. This includes a PFIL_HOOKS <br />conversion and additional functionality.</p>
<p>After applying the patch you must rebuild world and kernel. [ Or at <br />least kernel, sbin/ipfw and lib/libalias are recompiled and reinstalled. ]</p>
<p>Regards</p>
<p>Gary</p>
<p>Files that can be removed.<br /> sbin/ipfw/ipfw.c<br /> sys/net/ipfw/ip_fw.c</p>
<p>Files modified by patch.<br /> lib/libalias/Makefile<br /> lib/libalias/alias_db.c<br /> sbin/ipfw/Makefile<br /> src/sbin/ipfw/ipfw.8<br /> sys/conf/options<br /> src/sys/i386/conf/LINT<br /> sys/net/dummynet/Makefile<br /> sys/net/dummynet/ip_dummynet.c<br /> sys/net/ipfw/Makefile<br /> sys/net/ipfw/ip_fw.h<br /> sys/net/ipfw/ip_fw2.c</p> DragonFlyBSD - Bug #171 (Closed): VIA C3 identificationhttps://bugs.dragonflybsd.org/issues/1712006-05-09T01:22:30Zdragonfly
<p>Hello,</p>
<p>I've added identifying additional VIA processors from FreeBSD. My C3 is <br />now named correctly on startup.</p>
<p>Regards<br />Gary</p> DragonFlyBSD - Bug #160 (Closed): Import of libmd SHA256https://bugs.dragonflybsd.org/issues/1602006-04-29T04:33:34Zdragonfly
<p>I brought in libmd SHA256 support from FreeBSD to help with a build<br />issue. The attached patch is a simple import with minimal changes and<br />passes the "make test" built-in diagnostics.</p>
<p>Regards</p>
<p>Gary</p> DragonFlyBSD - Bug #159 (Rejected): ipsec-tools patchhttps://bugs.dragonflybsd.org/issues/1592006-04-28T20:27:20Zdragonfly
<p>The ipsec-tools port included in pkgsrc does not compile on DragonFly.<br />The included program racoon is useful for setting up IPsec between<br />PCs/Firewalls. The attached patch alows building under DragonFly.</p>
<p>I have tested the raccon daemon negotiating with WinXP. Is it worth <br />submitting this upstream and/or to pkgsrc?</p>
<p>Build ipsec-tools (<a class="external" href="http://ipsec-tools.sourceforge.net">http://ipsec-tools.sourceforge.net</a>) and install into<br />/usr/pkg. Configuration files will be stored under /usr/pkg/etc/racoon.</p>
<p>tar xfvj ipsec-tools-0.6.5.tar.bz2<br />cd ipsec-tools-0.6.5<br />patch -p1 < ~/ipsec-tools-0.6.5.diff<br />./configure --prefix=/usr/pkg --sysconfdir=/usr/pkg/etc/racoon<br />make<br />make install</p>
<p>Regards</p>
<p>Gary</p> DragonFlyBSD - Bug #158 (Closed): OpenSSL missing types.h include.https://bugs.dragonflybsd.org/issues/1582006-04-28T17:34:00Zdragonfly
<p>The openssl headers make use of "size_t" but <sys/types.h> is not <br />included. I'm not sure where the correct place to add the header is but <br />e_os2.h seems ok.</p>
<p>The following code does not compile on DragonFly.</p>
<p>#include <openssl/sha.h></p>
<p>int main()
{<br /> return 0;<br />}</p>
<p>Regards</p>
<p>Gary</p> DragonFlyBSD - Bug #150 (Resolved): IPSEC/FAST_IPSEC panic.https://bugs.dragonflybsd.org/issues/1502006-04-22T22:56:20Zdragonfly
<p>I have been experiencing panics when testing IPSEC under HEAD. The <br />Kernel panics when sending or receiving Authentication Headers (AH) and <br />TCP connections encapsulated in ESP time out.</p>
<p>I've made some progress resolving the panic but I can't get IPSEC or <br />FAST_IPSEC to work correctly. I've gone through the ipsec code looking <br />for any glaring errors. Any help would be appreciated.</p>
<p>Regards</p>
<p>Gary</p>
<p>Communication between DragonFly Head and FreeBSD 4/6 using IPSEC.</p>
<p>options IPSEC<br />options IPSEC_ESP</p>
<p>IPSEC AH ICMP, UDP and TCP are working between PCs.<br />IPSEC ESP ICMP and UDP work. TCP connections time out.<br />IPSEC AH-ESP ICMP and UDP work. TCP connections time out.</p>
<p>options FAST_IPSEC</p>
<p>IPSEC AH Kernel panic.<br />IPSEC ESP ICMP, UDP and TCP are working between PCs.<br />IPSEC AH-ESP Kernel panic.</p> DragonFlyBSD - Bug #30 (Closed): NIC vlan(4) capabilitieshttps://bugs.dragonflybsd.org/issues/302005-12-31T04:15:20Zdragonfly
<p>Hello,</p>
<p>This updates the drivers equipped to do hardware VLAN support to <br />announce the fact. This is already done by em(4) and re(4) and allows <br />control of the features via ifconfig. Capabilities were checked against <br />FreeBSD and the respective man pages.</p>
<p>Is it worth setting IFCAP_VLAN_MTU in dc(4), fxp(4), sis(4), ste(4) and <br />tx(4) as they are documented as supporting long frames for vlan natively?</p>
<p>Regards</p>
<p>Gary</p> DragonFlyBSD - Bug #27 (Closed): ip_output.c bug?https://bugs.dragonflybsd.org/issues/272005-12-27T23:44:10Zdragonfly
<p>Hello,</p>
<p>I have been looking at IPFW and think the following patch may also be <br />applicable to DragonFly.</p>
<p>ip_output.c 1.99.2.46<br /><a class="external" href="http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/ip_output.c">http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/ip_output.c</a></p>
<p>Regards</p>
<p>G.Allan</p> DragonFlyBSD - Bug #26 (Closed): vlan(4) broken.https://bugs.dragonflybsd.org/issues/262005-12-27T03:18:20Zdragonfly
<p>Hello,</p>
<p>I have been experiencing problems with vlan(4) on DragonFlyBSD HEAD.<br />Received tagged packets are not being passed down to ether_input()<br />correctly and transmitted packets are not being tagged. [Packet capture<br />shows no 802.1Q header on transmitted packets from DragonFlyBSD PC.]</p>
<p>The error message "ether_input got mbuf without embedded<br />ethernet header" was added to if_ethersubr.c during the recent if_bridge <br />import.</p>
<p>I have included details below.</p>
<p>Regards</p>
<p>G.Allan</p>
<p>DragonFlyBSD HEAD</p>
<p>ifconfig vr0<br />vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500<br /> inet6 fe80::240:63ff:fed8:230d%vr0 prefixlen 64 scopeid 0x1<br /> ether 00:40:63:d8:23:0d<br /> media: Ethernet autoselect (100baseTX <full-duplex>)<br /> status: active</p>
<p>ifconfig vlan10<br />vlan10: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1496<br /> inet 192.168.100.12 netmask 0xffffff00 broadcast 192.168.100.255<br /> inet6 fe80::240:63ff:fed8:230d%vlan10 prefixlen 64 scopeid 0x8<br /> ether 00:40:63:d8:23:0d<br /> media: Ethernet autoselect (100baseTX <full-duplex>)<br /> status: active<br /> vlan: 10 parent interface: vr0</p>
<p>All received packets tagged with VLAN 10 generate the following diagnostic.</p>
<p>Dec 26 17:00:48 fire kernel: ether_input got mbuf without embedded<br />ethernet header<br />Dec 26 17:19:09 fire kernel: ether_input got mbuf without embedded<br />ethernet header<br />Dec 26 17:37:30 fire kernel: ether_input got mbuf without embedded<br />ethernet header</p>
<p>FreeBSD 4.11</p>
<p>ifconfig vlan10<br />vlan10: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1496<br /> inet 192.168.100.10 netmask 0xffffff00 broadcast 192.168.100.255<br /> ether 00:0c:29:b5:d3:29<br /> vlan: 10 parent interface: fxp0</p>
<p>Attempts to ping 192.168.100.12 generate the following diagnostics.</p>
<p>Dec 18 17:08:40 build /kernel: arp: 192.168.100.12 is on vlan10 but got<br />reply from 00:40:63:d8:23:0d on fxp0<br />Dec 18 17:08:45 build last message repeated 4 times</p> DragonFlyBSD - Bug #22 (Closed): RealTek 8169S/8110S support.https://bugs.dragonflybsd.org/issues/222005-12-24T05:22:30Zdragonfly
<p>Matthew Dillon wrote:<br /> ><br /> > Do a boot -v and report which MII driver is currently attaching<br /> > to the RE ethernet. It's probably the generic driver (ukphy), in<br /> > which case we will need to port rgephy.c from FreeBSD to DragonFly.<br /> ><br /> > FreeBSD: sys/dev/mii/rge*<br /> > DragonFly: sys/dev/netif/mii_layer/rge*<br /> ><br /> > There is some fairly minor porting work that needs to be done,<br /> > which you can look at by looking at the cvs log history for some<br /> > of the other MII source modules in DragonFly.<br /> ><br /> > -Matt</p>
<p>Please find attached my attempt to import support for the RealTek <br />8169S/8110S from FreeBSD. This supports my DLink 528(T) Card. Could <br />someone please review/test? The patch is against HEAD. I ran into two <br />main issues.</p>
<p>DragonFly is missing a mii_phy_update() function so I wrote an <br />rge_phy_update() replacement. I'm not sure this is 100% correct.</p>
<p>The card would not auto-negotiate a 1Gbit connection. I increased the <br />auto-negotiation interval to 17 seconds from five which solved the <br />problem. There was PR report with this problem and solution for re(4) <br />and a Cisco switch but I can no longer find the link.</p>
<p>I can see why the cards are $12. I'm slightly disappointed that two of <br />these cards back to back only manage ~150Mbit/s but it's an improvement <br />over my built-in vr0.</p>
<p>Regards</p>
<p>G.Allan</p>
<p>ifconfig re0<br />re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500<br /> options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING><br /> inet6 fe80::213:46ff:fe2f:5a8e%re0 prefixlen 64 scopeid 0x3<br /> ether 00:13:46:2f:5a:8e<br /> media: Ethernet autoselect (1000baseT <full-duplex>)<br /> status: active</p>
<p>dmesg | grep miibus2<br />miibus2: <MII bus> on re0<br />rgephy0: <RTL8169S/8110S media interface> on miibus2</p>