On Fri, Mar 21, 2008 at 02:28:24PM +0100, Giulio Ferro wrote:
> Pyun YongHyeon wrote:
> > >
> > > # ping -s 2000 192.168.100.2
> > > PING 192.168.100.2 (192.168.100.2): 2000 data bytes
> > > 2008 bytes from 192.168.100.2: icmp_seq=0 ttl=64 time=0.264 ms
> > > 2008 bytes from 192.168.100.2: i
Pyun YongHyeon wrote:
>
> # ping -s 2000 192.168.100.2
> PING 192.168.100.2 (192.168.100.2): 2000 data bytes
> 2008 bytes from 192.168.100.2: icmp_seq=0 ttl=64 time=0.264 ms
> 2008 bytes from 192.168.100.2: icmp_seq=1 ttl=64 time=1001.186 ms
[...]
> 2008 bytes from 192.168.100.2: icmp_se
On Thu, Mar 20, 2008 at 06:02:53PM +0100, Giulio Ferro wrote:
> Pyun YongHyeon wrote:
> >Please try latest attempt to fix re(4) issues.
> > http://people.freebsd.org/~yongari/re/if_re.c
> > http://people.freebsd.org/~yongari/re/if_rlreg.h
> >
> >This one is attempt to fix the following bug re
Pyun YongHyeon wrote:
Please try latest attempt to fix re(4) issues.
http://people.freebsd.org/~yongari/re/if_re.c
http://people.freebsd.org/~yongari/re/if_rlreg.h
This one is attempt to fix the following bug reports on re(4).
- VLAN tagging does not work on multi-fragmented frames.
- Non-wo
On Fri, Mar 14, 2008 at 04:37:36PM +0100, Giulio Ferro wrote:
> Pyun YongHyeon wrote:
> >This hardware really make me crazy. There had been many attempts to
> >fix checksum offload related issues. But it seems that several users
> >still suffer from bad checksum or VLAN issues. So I guess the r
Pyun YongHyeon wrote:
This hardware really make me crazy. There had been many attempts to
fix checksum offload related issues. But it seems that several users
still suffer from bad checksum or VLAN issues. So I guess the root
cause of hardware bug was not yet known. This means that previous
patch
On Fri, Mar 14, 2008 at 01:14:40PM +0100, Giulio Ferro wrote:
> Giulio Ferro wrote:
> >That's it!
> >Now seems to work properly, the problem then is with hardware tagging.
> >
> >My question now is: can I use vlans without htag in a complex system with
> >heavy traffic without a significant p
On Fri, Mar 14, 2008 at 12:57:34PM +0100, Giulio Ferro wrote:
> Pyun YongHyeon wrote:
> > > No packet reached the other PC.
> >
> >Ok, then try disabling hardware VLAN tagging.
> >(#ifconfig re0 -vlanhwtag)
> >
> >
> That's it!
> Now seems to work properly, the problem then is with hardw
Giulio Ferro wrote:
That's it!
Now seems to work properly, the problem then is with hardware tagging.
My question now is: can I use vlans without htag in a complex system with
heavy traffic without a significant performance loss? If not, how much
will it
take to fix the issue with the driver?
Pyun YongHyeon wrote:
> No packet reached the other PC.
Ok, then try disabling hardware VLAN tagging.
(#ifconfig re0 -vlanhwtag)
That's it!
Now seems to work properly, the problem then is with hardware tagging.
My question now is: can I use vlans without htag in a complex system with
heav
On Fri, Mar 14, 2008 at 11:05:01AM +0100, Giulio Ferro wrote:
> Pyun YongHyeon wrote:
> > > The latter is if_rlreg.h, I guess...
> >
> >Oops, yes.
> > >
> > > Anyway they don't compile:
> > >
> >
> >Maybe you don't copy if_rlreg.h to /usr/src/sys/pci directory?
> >
>
> I didn't ;-)
Pyun YongHyeon wrote:
> The latter is if_rlreg.h, I guess...
Oops, yes.
>
> Anyway they don't compile:
>
Maybe you don't copy if_rlreg.h to /usr/src/sys/pci directory?
I didn't ;-)
Ok, I compiled and installed it.
The behavior didn't change: the simple ping works all right, but wh
On Thu, Mar 13, 2008 at 02:43:57PM +0100, Giulio Ferro wrote:
> Pyun YongHyeon wrote:
> >To rule out other possible issues, would you try the following
> >files on your box?
> >
> >http://people.freebsd.org/~yongari/re/if_re.c
> >http://people.freebsd.org/~yongari/re/if_rereg.h
Eygene Ryabinkin wrote:
Giulio, good day.
Thu, Mar 13, 2008 at 02:43:57PM +0100, Giulio Ferro wrote:
Pyun YongHyeon wrote:
To rule out other possible issues, would you try the following
files on your box?
http://people.freebsd.org/~yongari/re/if_re.c
http://people.freebsd.org/~yongari
Giulio, good day.
Thu, Mar 13, 2008 at 02:43:57PM +0100, Giulio Ferro wrote:
> Pyun YongHyeon wrote:
>> To rule out other possible issues, would you try the following
>> files on your box?
>>
>> http://people.freebsd.org/~yongari/re/if_re.c
>> http://people.freebsd.org/~yongari/re/if_rereg.h
>>
Pyun YongHyeon wrote:
To rule out other possible issues, would you try the following
files on your box?
http://people.freebsd.org/~yongari/re/if_re.c
http://people.freebsd.org/~yongari/re/if_rereg.h
The latter is if_rlreg.h, I guess...
Anyway they don't compile:
cc -c -O2 -frename-registe
On Wed, Mar 12, 2008 at 10:22:34PM +0100, Giulio Ferro wrote:
> Sam Leffler wrote:
> >You failed to provide the output of ifconfig on your running system.
> >Be sure any checksum offload is disabled (should be by the bridge).
> >
> >Sam
> My bad.
>
> I switched off checksum offload i
On Thu, Mar 13, 2008 at 11:13:14AM +1300, Andrew Thompson wrote:
> On Wed, Mar 12, 2008 at 12:38:06PM -0700, Sean Chittenden wrote:
> >> interface ethernet 1/g1
> >> switchport mode trunk
> >> switchport trunk allowed vlan add 10
> >> exit
> >
> > I think this is an issue with default VLAN membersh
interface ethernet 1/g1
switchport mode trunk
switchport trunk allowed vlan add 10
exit
I think this is an issue with default VLAN membership.
I don't think it's where the problem lies, otherwise even a simple
ping
wouldn't work. The problem here explicitly arises when packets are
fragmented
On Wed, Mar 12, 2008 at 12:38:06PM -0700, Sean Chittenden wrote:
>> interface ethernet 1/g1
>> switchport mode trunk
>> switchport trunk allowed vlan add 10
>> exit
>
> I think this is an issue with default VLAN membership. I have this config
> running on *hundreds* of servers without issue. Sin
Dear Giuilio,
Sean Chittenden wrote:
interface ethernet 1/g1
switchport mode trunk
switchport trunk allowed vlan add 10
exit
I think this is an issue with default VLAN membership.
I don't think it's where the problem lies, otherwise even a simple ping
wouldn't work. The problem here explic
Sean Chittenden wrote:
interface ethernet 1/g1
switchport mode trunk
switchport trunk allowed vlan add 10
exit
I think this is an issue with default VLAN membership.
I don't think it's where the problem lies, otherwise even a simple ping
wouldn't work. The problem here explicitly arises whe
Sam Leffler wrote:
You failed to provide the output of ifconfig on your running system.
Be sure any checksum offload is disabled (should be by the bridge).
Sam
My bad.
I switched off checksum offload in /etc/rc.conf like this:
ifconfig_re0="inet 192.168.60.1 netmask 255.255.255.0 -rxcsum
On Wed, March 12, 2008 8:38 pm, Sean Chittenden wrote:
>> interface ethernet 1/g1
>> switchport mode trunk
>> switchport trunk allowed vlan add 10
>> exit
>
> I think this is an issue with default VLAN membership. I have this
> config running on *hundreds* of servers without issue. Since Dell
>
interface ethernet 1/g1
switchport mode trunk
switchport trunk allowed vlan add 10
exit
I think this is an issue with default VLAN membership. I have this
config running on *hundreds* of servers without issue. Since Dell
should be a cisco rip-off, on your switchport config, throw in
(hav
25 matches
Mail list logo
