Hi.
Is there any way to use /31's on ordinary ethernet links in 7.2?
"ifconfig addr dest-addr" does not work either. It keeps setting the
last ip as broadcast.
Sincerley,
Sebastian H
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.or
Chuck Swiger skrev:
On Oct 30, 2009, at 4:46 PM, Sebastian Hyrwall wrote:
Is there any way to use /31's on ordinary ethernet links in 7.2?
"ifconfig addr dest-addr" does not work either. It keeps setting the
last ip as broadcast.
A /31 subnet is only defined for point-to-point network links,
Freddie Cash skrev:
Reading the man page for ifconfig will show the "ptp" option for
ifconfig, that configures the interface as a point-to-point
interface.. :)
It will also show that it seems to be only for bridgeing,
# ifconfig fxp0 ptp fxp0
ifconfig: unable to get bridge flags: Invalid
On Oct 30, 2009, at 5:22 PM, Sebastian Hyrwall wrote:
A /31 subnet is only defined for point-to-point network links, per:
http://www.rfc-editor.org/rfc/rfc3021.txt
Ordinary ethernet links have BROADCAST flag set instead of
POINTOPOINT.
Well how do I set the POINTOPOINT flag and remove th
On Oct 30, 2009, at 3:37 PM, Chuck Swiger wrote:
ifconfig en0 inet 192.1.1.10 inet 192.1.1.2
Whoops-- copy-paste-typo; instead should be:
ifconfig en0 inet 192.1.1.10 192.1.1.11
--
-Chuck
___
freebsd-net@freebsd.org mailing list
http://lists.fre
Reading the man page for ifconfig will show the "ptp" option for ifconfig,
that configures the interface as a point-to-point interface.. :)
On Fri, Oct 30, 2009 at 5:22 PM, Sebastian Hyrwall wrote:
> Chuck Swiger skrev:
>
>> On Oct 30, 2009, at 4:46 PM, Sebastian Hyrwall wrote:
>>
>>> Is ther
On Oct 30, 2009, at 4:46 PM, Sebastian Hyrwall wrote:
Is there any way to use /31's on ordinary ethernet links in 7.2?
"ifconfig addr dest-addr" does not work either. It keeps setting the
last ip as broadcast.
A /31 subnet is only defined for point-to-point network links, per:
http://www.
Chuck Swiger skrev:
On Oct 30, 2009, at 5:22 PM, Sebastian Hyrwall wrote:
A /31 subnet is only defined for point-to-point network links, per:
http://www.rfc-editor.org/rfc/rfc3021.txt
Ordinary ethernet links have BROADCAST flag set instead of POINTOPOINT.
Well how do I set the POINTOPOINT
/31 on point to point ether is exceedingly common in inter-router
topologies.
you may be amused to also read draft-kohno-ipv6-prefixlen-p2p-00.txt
randy
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To un
> > A /31 subnet is only defined for point-to-point network links, per:
> >
> > http://www.rfc-editor.org/rfc/rfc3021.txt
> >
> > Ordinary ethernet links have BROADCAST flag set instead of POINTOPOINT.
> >
> > Regards,
> Well how do I set the POINTOPOINT flag and remove the BROADCAST-flag on
> e
> No, Cisco does not *support* it. They make it available, which is a
> completely different story.
>
> We have asked Cisco repeatedly, through official channels, whether
> they *support* /31 on Ethernet links. The answer is always that it
> *may* work, use at your own peril.
i have managed O(10^
> > We have asked Cisco repeatedly, through official channels, whether
> > they *support* /31 on Ethernet links. The answer is always that it
> > *may* work, use at your own peril.
>
> i have managed O(10^3) ciscos in isp backbone(s). /31s predominate for
> ether links in that space. though i su
> However, I was simply reacting to the claim that it was *supported* by
> Cisco.
have you noticed a difference in the bug rate between things that are
'supported by cisco' and those that just happen to be there? :)
but you're right. i liked. our p2ps are /30s, not /31s. and we're
moving from
Sebastian Hyrwall wrote:
Chuck Swiger skrev:
inside, or using a /32 and an explicit default route via your
ethernet interface.
Unfortunetly that doesn't work. It just sets 192.1.1.2 as broadcast.
Well wrapping a /31 inside of a /30 kinda defeats the purpose :)
You could still use a /32 a
Nikos Vassiliadis skrev:
Sebastian Hyrwall wrote:
Chuck Swiger skrev:
inside, or using a /32 and an explicit default route via your
ethernet interface.
Unfortunetly that doesn't work. It just sets 192.1.1.2 as broadcast.
Well wrapping a /31 inside of a /30 kinda defeats the purpose :)
On Sat, 31 Oct 2009, Randy Bush wrote:
Hi,
However, I was simply reacting to the claim that it was *supported* by
Cisco.
have you noticed a difference in the bug rate between things that are
'supported by cisco' and those that just happen to be there? :)
but you're right. i liked. our p2p
Sebastian Hyrwall wrote:
You could still use a /32 and then add a route for the other IP via
the ethernet interface. This is effectively the same with a /31.
Does not work,
I see, I've checked this on 9.0 and found it working, not on 7.2.
Nikos
__
17 matches
Mail list logo
