Re: Problems with 8.1, PPPoE server, and Cisco client

2010-11-18 Thread Bjoern A. Zeeb

On Tue, 9 Nov 2010, Paul Thornton wrote:


Hi folks,

Keeping the list archives updated for any poor soul that has a similar
problem in future...

On 26/10/2010 18:55, Paul Thornton wrote:

I'm also going to give mpd a go and see if that works - but if it tries
the same config options as pppoed then I may be straight back to where I
am now.


The verdict with mpd is exactly the same - the Cisco takes exception to
the IPCP request immediately following the successful auth, and tears
down the connection.

I'm going to take this to the Cisco TAC and see if they can suggest
anything that may be causing this as it makes no sense at all when all
other clients I try work.


Unfortunately I have never seen the full ppp debug log I had initially
asked for.  Can't help without that.  It would tell you why it didn't
work.

/bz

--
Bjoern A. Zeeb  Welcome a new stage of life.
 Going to jail sucks --  All my daemons like it!
  http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: How to generate IPv6 RA without any prefixes?

2010-11-18 Thread Bjoern A. Zeeb

On Wed, 10 Nov 2010, sth...@nethelp.no wrote:

Hi,


In IPv6 it should be possible to generate a Router Advertisement which
contains no prefix options (the idea being that I want the host to
populate its default router list but nothing else). However, I cannot
seem to get rtadvd to do this.

If I start rtadvd with no /etc/rtadvd.conf file, it sends RAs with a
prefix option corresponding to the IPv6 address of the interface. In
the /etc/rtadvd.conf I can explicitly specify prefixes ("addr"), but
I can't find any way to specify that no prefix options should be sent.

Any suggestions?


What if you start rtadvd with -s and have a basically empty (default)
config file entry?

I haven't checked but theat would be my best guess?

/bz

--
Bjoern A. Zeeb  Welcome a new stage of life.
 Going to jail sucks --  All my daemons like it!
  http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: How to generate IPv6 RA without any prefixes?

2010-11-18 Thread sthaug
> > In IPv6 it should be possible to generate a Router Advertisement which
> > contains no prefix options (the idea being that I want the host to
> > populate its default router list but nothing else). However, I cannot
> > seem to get rtadvd to do this.
> >
> > If I start rtadvd with no /etc/rtadvd.conf file, it sends RAs with a
> > prefix option corresponding to the IPv6 address of the interface. In
> > the /etc/rtadvd.conf I can explicitly specify prefixes ("addr"), but
> > I can't find any way to specify that no prefix options should be sent.
> >
> > Any suggestions?
> 
> What if you start rtadvd with -s and have a basically empty (default)
> config file entry?
> 
> I haven't checked but theat would be my best guess?

Does not appear to work. With /etc/radvd.conf containing only:

vlan0:\
:raflags#128:

and starting rtadvd with -s, it still announces the /64 prefix I have
on the vlan0 interface.

It's possible we simply have some missing functionality here. The man
page for Mac OS X shows an "addrs" field which FreeBSD doesn't have -
but which still doesn't do quite what I want:

http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man5/rtadvd.conf.5.html

addrs   (num) Number of prefixes.  Its default is 0, so it must explicitly
 be set to positive values if you want to specify any prefix
 information option.  If its value is 0, rtadvd(8) looks up the
 system routing table and advertise the prefixes corresponding to
 interface routes on the interface.  If its value is more than 1,
 you must specify the index of the prefix for each item below.
 Indices vary from 0 to N-1, where N is the value of addrs.  Each
 index shall follow the name of each item, e.g., ``prefixlen2''.

Steinar Haug, Nethelp consulting, sth...@nethelp.no
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: How to generate IPv6 RA without any prefixes?

2010-11-18 Thread Bjoern A. Zeeb

On Thu, 18 Nov 2010, sth...@nethelp.no wrote:

Hi Steinar,


In IPv6 it should be possible to generate a Router Advertisement which
contains no prefix options (the idea being that I want the host to
populate its default router list but nothing else). However, I cannot
seem to get rtadvd to do this.

If I start rtadvd with no /etc/rtadvd.conf file, it sends RAs with a
prefix option corresponding to the IPv6 address of the interface. In
the /etc/rtadvd.conf I can explicitly specify prefixes ("addr"), but
I can't find any way to specify that no prefix options should be sent.

Any suggestions?


What if you start rtadvd with -s and have a basically empty (default)
config file entry?

I haven't checked but theat would be my best guess?


Does not appear to work. With /etc/radvd.conf containing only:

vlan0:\
   :raflags#128:

and starting rtadvd with -s, it still announces the /64 prefix I have
on the vlan0 interface.

It's possible we simply have some missing functionality here. The man
page for Mac OS X shows an "addrs" field which FreeBSD doesn't have -
but which still doesn't do quite what I want:

http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man5/rtadvd.conf.5.html

addrs   (num) Number of prefixes.  Its default is 0, so it must explicitly
be set to positive values if you want to specify any prefix
information option.  If its value is 0, rtadvd(8) looks up the
system routing table and advertise the prefixes corresponding to
interface routes on the interface.  If its value is more than 1,
you must specify the index of the prefix for each item below.
Indices vary from 0 to N-1, where N is the value of addrs.  Each
index shall follow the name of each item, e.g., ``prefixlen2''.


we'll have to redo some of rtsol(d)/rtadvd anyway as IANA has (long)
assigned valid magic numbers for the formerly experimental options
from the initial days.

Can you open a PR and get it assigned to net@ or bz@, so this won't be
lost?  I am not sure I'll be able to look the next 10 days.

/bz

--
Bjoern A. Zeeb  Welcome a new stage of life.
 Going to jail sucks --  All my daemons like it!
  http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: request for MFC of em/igb drivers

2010-11-18 Thread Chris Peiffer

Thank you Jack, and thank you Eugene. I will integrate that NULL-check
into my tree immediately.

On Wed, Nov 17, 2010 at 09:39:14AM -0800, Jack Vogel wrote:
> Yes, everyone, I plan on updating all the drivers, there has been no
> activity
> because I've tracking down a couple bugs that are tough, involving days
> of testing to reproduce. I know we're getting close and I appreciate any
> reports like this before.
> 
> Stay tuned
> 
> Jack
> 
> 
> On Wed, Nov 17, 2010 at 5:22 AM, Vlad Galu  wrote:
> 
> > On Wed, Nov 17, 2010 at 1:54 PM, Eugene Grosbein 
> > wrote:
> > > On 17.11.2010 13:04, Chris Peiffer wrote:
> > >>
> > >> Hi,
> > >>
> > >> I've been watching the traffic here over the last few months relating
> > >> to the em and igb Intel ethernet drivers. It seems like there's a big
> > >> consensus that HEAD has some good new fixes.
> > >>
> > >> Looking at this:
> > >>
> > >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/e1000/if_em.c
> > >>
> > >> There's a pretty big commit to HEAD in rev 1.58 on Sep 27 that's
> > >> marked "MFC: a week" but it doesn't look like anything's been MFC'd
> > >> since. (And several other revisions that look more experimental have
> > >> since gone into HEAD.)
> > >>
> > >> We've been seeing some weird issues with em devices under high load
> > >> and if these changes in 1.58 are ready for STABLE we'd love to test
> > >> them live.
> > >>
> > >> So this is a beg... if the relevant committers are out here, can that
> > >> MFC go through soon? Or if it can't, or I'm reading the logs wrong,
> > >> please explain.
> > >>
> > >> Thanks in advance.
> > >
> > > Indeed, in RELENG_8 em(4) is not useable for us because of two flaws:
> > >
> > > 1. It panices system due to NULL pointers dereference.
> > > It needs the following patch taken from CURRENT's igb(4):
> > >
> > > --- if_em.c.orig2010-11-02 15:45:56.0 +0600
> > > +++ if_em.c 2010-11-08 14:24:46.0 +0600
> > > @@ -4181,9 +4181,11 @@
> > >ifp->if_ierrors++;
> > >/* Reuse loaded DMA map and just update mbuf chain
> > */
> > >mp = rxr->rx_buffers[i].m_head;
> > > +   if(mp) {
> > >mp->m_len = mp->m_pkthdr.len = MCLBYTES;
> > >mp->m_data = mp->m_ext.ext_buf;
> > >mp->m_next = NULL;
> > > +   }
> > >if (adapter->max_frame_size <=
> > >(MCLBYTES - ETHER_ALIGN))
> > >m_adj(mp, ETHER_ALIGN);
> > >
> > > igb(4) in RELENG_8 has not this fix too and there is a PR:
> > > http://www.freebsd.org/cgi/query-pr.cgi?pr=150920
> > >
> > > 2. It makes physical link down/up for every vlan creation/deletion
> > > that leads to 3 seconds of service interruption and
> > > down/up events for all other vlans based on same parent interface.
> > > It needs the following patch that's already present in CURRENT
> > > but not in RELENG_8:
> > >
> > > @@ -4342,7 +4344,8 @@
> > >em_shadow_vfta[index] |= (1 << bit);
> > >++adapter->num_vlans;
> > >/* Re-init to load the changes */
> > > -   em_init(adapter);
> > > +   if (ifp->if_capenable & IFCAP_VLAN_HWFILTER)
> > > +   em_init(adapter);
> > >  }
> > >
> > >  /*
> > > @@ -4366,7 +4369,8 @@
> > >em_shadow_vfta[index] &= ~(1 << bit);
> > >--adapter->num_vlans;
> > >/* Re-init to load the changes */
> > > -   em_init(adapter);
> > > +   if (ifp->if_capenable & IFCAP_VLAN_HWFILTER)
> > > +   em_init(adapter);
> > >  }
> > >
> > >  static void
> > > ___
> > > freebsd-net@freebsd.org mailing list
> > > http://lists.freebsd.org/mailman/listinfo/freebsd-net
> > > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
> > >
> >
> > Any plans for bringing in version 2.2.3 of ixgbe(4)?
> >
> >
> > --
> > Good, fast & cheap. Pick any two.
> > ___
> > freebsd-net@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-net
> > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
> >
> ___
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: kern/152360: [dummynet] [panic] Crash related to dummynet.

2010-11-18 Thread linimon
Old Synopsis: Crash related to dummynet.
New Synopsis: [dummynet] [panic] Crash related to dummynet.

Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Nov 18 17:34:27 UTC 2010
Responsible-Changed-Why: 
reclassify.

http://www.freebsd.org/cgi/query-pr.cgi?pr=152360
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: Problem with re0

2010-11-18 Thread Gabor Radnai
re0: flags=8843 metric 0 mtu 1500

options=389b
ether d8:5d:4c:80:b4:88
inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255
media: Ethernet autoselect (1000baseT )
status: active
nfe0: flags=8843 metric 0 mtu 1500
options=80008
ether 00:1a:92:38:dc:95
inet 192.168.0.200 netmask 0xff00 broadcast 192.168.0.255
media: Ethernet autoselect (1000baseT )
status: active
lo0: flags=8049 metric 0 mtu 16384
options=3
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff00
nd6 options=3


On Fri, Nov 12, 2010 at 11:53 PM, Pyun YongHyeon  wrote:

> On Fri, Nov 12, 2010 at 10:18:40PM +0100, Gabor Radnai wrote:
> > Hi,
> >
> > I hope you are interested in inet section it looks like this (will able
> to
> > send the exact output only a bit later unfortunately as removed the card)
> :
> > inet 0.0.0.0 netmask 255.255.255.255
> >
>
> This might be caused by dhclient(i.e. dhclient(8) failed to receive
> DHCP ACK).
> BTW, you still didn't show me the output of ifconfig re0 after UP
> the interface(i.e. ifconfig re0 up).
>
> > Thanks,
> > Gabor
> >
> > On Thu, Nov 11, 2010 at 10:26 PM, Pyun YongHyeon 
> wrote:
> >
> > > On Thu, Nov 11, 2010 at 09:56:26PM +0100, Gabor Radnai wrote:
> > > > Hi,
> > > >
> > > > I have an Asus M2NPV-VM motherboard with integrated Nvidia MCP51
> Gigabit
> > > > Ethernet NIC and
> > > > TP-Link TG-3468 PCIe network card which is using Realtek 8111 chip.
> > > >
> > > > I have problem with the re driver: the Nvidia network interface is
> > > working
> > > > properly but the other
> > > > though it seems recognized by OS I cannot use. Sporadically it
> remains
> > > down
> > > > and if it gets up then
> > > > does not get ip address via DHCP nor help if I set static ip address.
> Can
> > > > manipulate via ifconfig but
> > > > unreachable via IP.
> > > >
> > > > I replaced cable, interchanged cable working with Nvidia, restarted
> > > > switch/router but no luck so far.
> > > > Also using this nic in a Windows machine - it works. Using my Asus
> mob
> > > with
> > > > Ubuntu Live CD - card works.
> > > >
> > > > Can it be a driver bug or this type of chip is not supported by re
> > > driver?
> > > >
> > >
> > > Eh, you already know the answer, recognized by re(4) but does not
> > > work so it's a bug of re(4). Would you show me the output of
> > > ifconfig re0 after UP the interface(i.e. ifconfig re0 up).
> > >
>
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: How to generate IPv6 RA without any prefixes?

2010-11-18 Thread Siquijor Philips
> On Wed, 10 Nov 2010, sth...@nethelp.no wrote:
>
> Hi,
>
>
> In IPv6 it should be possible to generate a Router Advertisement which
> contains no prefix options (the idea being that I want the host to
> populate its default router list but nothing else). However, I cannot
> seem to get rtadvd to do this.
>
> If I start rtadvd with no /etc/rtadvd.conf file, it sends RAs with a
> prefix option corresponding to the IPv6 address of the interface. In
> the /etc/rtadvd.conf I can explicitly specify prefixes ("addr"), but
> I can't find any way to specify that no prefix options should be sent.
>
> Any suggestions?

You mean to say that you want your router to act as the default IPv6
gateway only advertising default route via RA and the IPv6 prefixes
are managed by other means such as DHCPv6 server? Because by its the
only way I can think of with your case now. You can specify
'pinfoflags' with 'l' in the /etc/rtadvd.conf to suppress the prefix
information option being advertised.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: How to generate IPv6 RA without any prefixes?

2010-11-18 Thread Siquijor Philips
On Fri, Nov 19, 2010 at 11:19 AM, Siquijor Philips
 wrote:
>> On Wed, 10 Nov 2010, sth...@nethelp.no wrote:
>>
>> Hi,
>>
>>
>> In IPv6 it should be possible to generate a Router Advertisement which
>> contains no prefix options (the idea being that I want the host to
>> populate its default router list but nothing else). However, I cannot
>> seem to get rtadvd to do this.
>>
>> If I start rtadvd with no /etc/rtadvd.conf file, it sends RAs with a
>> prefix option corresponding to the IPv6 address of the interface. In
>> the /etc/rtadvd.conf I can explicitly specify prefixes ("addr"), but
>> I can't find any way to specify that no prefix options should be sent.
>>
>> Any suggestions?
>
> You mean to say that you want your router to act as the default IPv6
> gateway only advertising default route via RA and the IPv6 prefixes
> are managed by other means such as DHCPv6 server? Because by its the
> only way I can think of with your case now. You can specify
> 'pinfoflags' with 'l' in the /etc/rtadvd.conf to suppress the prefix
> information option being advertised.
>

My suggestion above is not complete, you should have something in your
/etc/rtadvd.conf

vlan0:\
 :raflags="mo":pinfoflags="l":
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"