https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233283
Bjoern A. Zeeb changed:
What|Removed |Added
Assignee|n...@freebsd.org |melif...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233283
Sam Frenick changed:
What|Removed |Added
CC||jaunts_buys...@icloud.com
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233283
--- Comment #17 from Jamie Landeg-Jones ---
ifconfig_vtnet0_ipv6="inet6 2001:19f0:300:2185::1:1 prefixlen 64 accept_rtadv"
ipv6_activate_all_interfaces="YES"
rtsold_enable="YES"
rtsold_flags="-Fa" # Flags to an IPv6 router solicitation
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233283
Jamie Landeg-Jones changed:
What|Removed |Added
CC||ja...@catflap.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233283
--- Comment #15 from Conrad Meyer ---
(In reply to Andrey V. Elsukov from comment #14)
I see, thanks for explaining Andrey.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233283
--- Comment #14 from Andrey V. Elsukov ---
(In reply to Conrad Meyer from comment #13)
> (In reply to Andrey V. Elsukov from comment #7)
> Isn't this patch a bit of a kludge? The existing check for the entry in our
> L2 entry cache should
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233283
--- Comment #13 from Conrad Meyer ---
(In reply to Andrey V. Elsukov from comment #7)
Isn't this patch a bit of a kludge? The existing check for the entry in our L2
entry cache should be sufficient — why don't we populate LLE cache with on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233283
jin...@wide.ad.jp changed:
What|Removed |Added
CC||jin...@wide.ad.jp
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233283
--- Comment #11 from peos42 ---
(In reply to Conrad Meyer from comment #8)
RFC 4861 say:
--snip--
If the source address of the packet prompting the solicitation is the
same as one of the addresses assigned to the outgoing interface
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233283
--- Comment #10 from Conrad Meyer ---
Further (§8.3, Host Specification):
A host receiving a valid redirect SHOULD update its Destination Cache
accordingly so that subsequent traffic goes to the specified target.
...
If the Target
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233283
--- Comment #9 from Conrad Meyer ---
(In reply to peos42 from comment #6)
Maybe this part?
Router Advertisements contain a list of prefixes used for on-link
determination and/or autonomous address configuration; flags
associated w
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233283
--- Comment #8 from Conrad Meyer ---
(In reply to peos42 from comment #6)
Could they be more specific in how they think BSD is non-compliant with that
RFC? It's a large document and the critique is not specific.
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233283
--- Comment #7 from Andrey V. Elsukov ---
Created attachment 199377
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=199377&action=edit
Proposed patch
I just tried to patch, and it seems with this patch I can add on-link route to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233283
--- Comment #6 from peos42 ---
Maybe there is a reason why DragonflyBSD fixed it.
The cloud provider in the same support case I started this thread with said:
--snip--
Additionally, if BSD followed RFC compliance for neighbour table disc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233283
Andrey V. Elsukov changed:
What|Removed |Added
CC||a...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233283
Bjoern A. Zeeb changed:
What|Removed |Added
Severity|Affects Many People |Affects Some People
Hi!
I need some help, I had working multicast IPv6 routing using freebsd 8.3 but
when i try to test it I failed. my topology is like this with freebsd as router
and xp as server and client :
XP1<---2001:abcd:10::/64--->FBSD1<---2001:abcd:20::/64--->FBSD2<---2001:abcd:30::/64--->XP2
this is my
At 12:34 PM 8/23/2010, Xavier HUMBERT wrote:
Mike Tancsa wrote:
> I dont understand, why is 10.75.2.1 going out your default interface
> ? It should look for packets on the same subnet that the vlan3
interface is on
E According to the interfaces status and the routing table,
this is
Aleksandr A Babaylov <"."@babolo.ru> wrote:
> I had similar prolem in 8.0-STABLE. Try
>
> sysctl net.inet.flowtable.enable=0
Tried it with no success. Tks anyway
Mike Tancsa wrote:
> I dont understand, why is 10.75.2.1 going out your default interface
> ? It should look for packets on the s
At 11:52 AM 8/20/2010, Xavier HUMBERT wrote:
vlan3: flags=8843 metric 0 mtu 1500
description: Chateau
options=3
ether 00:e0:81:2d:62:3e
inet 10.75.2.251 netmask 0xff00 broadcast 10.75.2.255
media: Ethernet autoselect (1000baseT )
status: active
vlan: 30 parent inte
Aleksandr A Babaylov <"."@babolo.ru> wrote:
> On Fri, Aug 20, 2010 at 05:52:50PM +0200, Xavier HUMBERT wrote:
> > I've got some trouble routing vlans through FreeBSD 8.1-RELEASE.
>
> I had similar prolem in 8.0-STABLE. Try
>
> sysctl net.inet.flowtable.enable=0
I tried net.link.vlan.soft_pad wi
On Fri, Aug 20, 2010 at 05:52:50PM +0200, Xavier HUMBERT wrote:
> I've got some trouble routing vlans through FreeBSD 8.1-RELEASE.
I had similar prolem in 8.0-STABLE. Try
sysctl net.inet.flowtable.enable=0
___
freebsd-net@freebsd.org mailing list
http:
Hi all,
I've got some trouble routing vlans through FreeBSD 8.1-RELEASE.
The core backbone of our network is a Nortel 5520-48T-PWR stack, configured
L2/L3, with 470-24T-PWR stacks in each building (5 including core), fiber
connected.
Since the company who built our network is unable to make the
Synopsis: [em] FreeBSD 7 multicast routing problem
State-Changed-From-To: feedback->closed
State-Changed-By: bms
State-Changed-When: Sat 10 Apr 2010 12:07:35 UTC
State-Changed-Why:
Timeout on feedback. I believe yongari has merged driver fixes where
relevant to this issue.
Responsible-Chan
Honestly, I never gave many credits to mrouted. I do all testing of my
mcast stuff with xorp. If you want, I'll send you some examples of
config.boot files for xorp, they can look mess if you use it for
first time.
If you want to stick with mrouted, can you describe your problem with a
bit more d
Thank you all that give me help,I configure mrouted with the handbook and
update to 8.0 stable ,but it cannot multicast routing yet. please give me
more advice.This is the steps of my configuration following:
1.configure the kernel options,add the following
options MROUTING
2.build and install ne
I belive that mrouting in 8.o is broken due to some kind of paranoid
filter that drops IGMP joins, can't rememeber exact problem. Anyway, bms
commited patch to -STABLE, so maybe you may need to pull up kernel
source from cvs.
Ivor
On Thu, Jan 21, 2010 at 09:52:56AM +0800, yanqing you wrote:
> ho
Hi,
Try recompiling your kernel with MROUTING. Have a look in the Handbook for
details.
Le Jeu 21 janvier 2010 02:52, yanqing you a écrit :
> how to enable multicast routing in freeBSD8.0,please give the steps of
> configuration. ___
> freebsd-net@fre
how to enable multicast routing in freeBSD8.0,please give the steps of
configuration.
___
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"
The following reply was made to PR kern/122839; it has been noted by GNATS.
From: 4...@legis.krsn.ru
To: pyu...@gmail.com
Cc: bug-follo...@freebsd.org, b...@freebsd.org, freebsd-net@freebsd.org,
j...@freebsd.org
Subject: kern/122839: [multicast] FreeBSD 7 multicast routing problem
Date
Hi,
Thank you for your response.
Sorry, but i'm unable to test your patch for if_msk.c wich you suggested,
becouse our production core router need to be up and ready 24 hours a day,
and our quick fix for if_msk.c also helped us with multicast routing
problem. Right now i don't have
The following reply was made to PR kern/122839; it has been noted by GNATS.
From: Pyun YongHyeon
To: 4...@legis.krsn.ru
Cc: bug-follo...@freebsd.org, b...@freebsd.org, freebsd-net@freebsd.org,
j...@freebsd.org
Subject: Re: kern/122839: [multicast] FreeBSD 7 multicast routing problem
Date
On Fri, Mar 20, 2009 at 05:56:11PM +0700, 4...@legis.krsn.ru wrote:
> Hi,
>
> As i wrote before, based on the patch, suggested by Tomas Svensson, we
> have made our version of that patch. And about
> a year already we using it on a production inside core router without any
> problems. Also we p
The following reply was made to PR kern/122839; it has been noted by GNATS.
From: 4...@legis.krsn.ru
To: bug-follo...@freebsd.org, b...@freebsd.org, freebsd-net@FreeBSD.org
Cc:
Subject: kern/122839: [multicast] FreeBSD 7 multicast routing problem
Date: Fri, 20 Mar 2009 17:56:11 +0700
Hi
Hi,
As i wrote before, based on the patch, suggested by Tomas Svensson, we
have made our version of that patch. And about
a year already we using it on a production inside core router without any
problems. Also we patched if_msk.c, and it also
working just fine same amount of time on the same
The following reply was made to PR kern/122839; it has been noted by GNATS.
From: 4...@legis.krsn.ru
To: bug-follo...@freebsd.org, b...@freebsd.org, freebsd-net@FreeBSD.org
Cc:
Subject: kern/122839: [multicast] FreeBSD 7 multicast routing problem
Date: Fri, 20 Mar 2009 12:54:41 +0700
Копия:
Тема: Re: kern/122839: [multicast] FreeBSD 7 multicast routing
problem
Hi,
Have you managed to chase the em(4) patch upstream?
It would be great if you could let me know so this PR can either be
closed,
or assigned to the em(4) driver maintainer.
thank
The following reply was made to PR kern/122839; it has been noted by GNATS.
From: Bruce Simpson
To: Eugene <4...@legis.krsn.ru>, freebsd-gnats-sub...@freebsd.org
Cc:
Subject: Re: kern/122839: [multicast] FreeBSD 7 multicast routing problem
Date: Thu, 19 Mar 2009 17:47:38 +
Hi,
The following reply was made to PR kern/122839; it has been noted by GNATS.
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Cc:
Subject: Re: kern/122839: [multicast] FreeBSD 7 multicast routing problem
Date: Wed, 18 Jun 2008 22:47
Hello.
A box of mine has an interface configured with two IPs on two different
nets:
# ifconfig
xl0: flags=8943 mtu 1500
options=9
inet 192.168.2.2 netmask 0xff00 broadcast 192.168.2.255
inet 192.168.0.2 netmask 0xff00 broadcast 192.168.0.255
ether 00:50:
The following reply was made to PR kern/122839; it has been noted by GNATS.
From: Tomas Svensson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Cc:
Subject: Re: kern/122839: [multicast] FreeBSD 7 multicast routing problem
Date: Wed, 23 Apr 2008 15:16:56 +0200
There is an o
The following reply was made to PR kern/122839; it has been noted by GNATS.
From: "Bruce M. Simpson" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: kern/122839: [multicast] FreeBSD 7 multicast routing problem
Date: Tue, 22 Apr 200
The following reply was made to PR kern/122839; it has been noted by GNATS.
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Cc:
Subject: Re: kern/122839: [multicast] FreeBSD 7 multicast routing problem
Date: Tue, 22 Apr 2008 22:52:53 +0800
Hi.
I cold&#
The following reply was made to PR kern/122839; it has been noted by GNATS.
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Cc:
Subject: Re: kern/122839: [multicast] FreeBSD 7 multicast routing problem
Date: Fri, 18 Apr 2008 15:50:02 +0800
Thank you very mach for your
Thank you very mach for your response!
Yes, as i wrote before, if mrouted daemon, or pimdd daemon is running,
then ALLMULTI flag appears on all interfaces (i can see it from ifconfig
output). But multicast routing do not work.
I have a machine with an old FreeBSD4.9 running, wich working as a
Synopsis: [multicast] FreeBSD 7 multicast routing problem
State-Changed-From-To: open->feedback
State-Changed-By: bms
State-Changed-When: Thu 17 Apr 2008 08:49:01 UTC
State-Changed-Why:
The symptoms you describe do not sound like a multicast routing issue.
Given your description it sounds l
Old Synopsis: FreeBSD 7 multicast routing problem
New Synopsis: [multicast] FreeBSD 7 multicast routing problem
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Apr 17 05:45:46 UTC 2008
Responsible-Changed-Why:
Over
IL PROTECTED]>
To:
Sent: Tuesday, September 05, 2006 11:00 PM
Subject: Re: routing problem?
> Do you have gateway_enable=YES in your /etc/rc.conf
> Look the net.inet.ip.forwarding:
> # sysctl net.inet.ip.forwarding
>
>
> Gilberto
>
> 2006/9/1, Mihail Balikov <[E
Yes, forwarding is enabled, this machine works like router
- Original Message -
From: "Gilberto Villani Brito" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, September 05, 2006 11:00 PM
Subject: Re: routing problem?
> Do you have gateway_enable=YES in your /etc/rc.
Do you have gateway_enable=YES in your /etc/rc.conf
Look the net.inet.ip.forwarding:
# sysctl net.inet.ip.forwarding
Gilberto
2006/9/1, Mihail Balikov <[EMAIL PROTECTED]>:
Hello,
Running "route -n monitor" I see a lot of strange RTM_MISS messages :
got message of size 96 on Fri Sep 1 1
Hello,
Running "route -n monitor" I see a lot of strange RTM_MISS messages :
got message of size 96 on Fri Sep 1 19:00:54 2006
RTM_MISS: Lookup failed on this address: len 96, pid: 0, seq 0, errno 0,
flags:
locks: inits:
sockaddrs:
default
#route -n get default
route to: default
destinati
Dear all,
I am trying to connect to my office's freebsd mpd server, but I am not
able to ping other subnet except those same subnet that I was assigned
by the mpd server.
eg.
Here is the IPs assigned to my laptop from my office's mpd server:
IP: 10.2.99.23
Default gateway: 10.2.99.23 <<--
On Tuesday 30 August 2005 21:43, Paul Schenkeveld wrote:
> > I am wondering what the "right" solution is here - I guess I could assign
> > an IP to the tunnel but it seems like a bit of a waste..
>
> You could assign the same IP address as dc1 to your gif0 interface but
> with a /32 netmask.
Hmm,
t; From: "Julian Elischer" <[EMAIL PROTECTED]>
> To: "Donatas" <[EMAIL PROTECTED]>
> Sent: Saturday, August 20, 2005 8:31 AM
> Subject: Re: routing problem (with corrected scheme)
>
>
>> did my sugestion work?
>>
>
Hi,
I have this problem trying to get a FreeBSD 4.x router to work with my ISP -
it pretty much works except for one thing.
We have a business DSL connection which is bridged ethernet (dc1), we also
have a class C routed via gif. Recently the ISP changed things slightly and
now all our out boun
generated packets
come to firewall from ip_input and fails on this rule? Using "pass" instead of
"fwd" results in the same.
- Original Message -
From: "Julian Elischer" <[EMAIL PROTECTED]>
To: "Donatas" <[EMAIL PROTECTED]>
Sent
Donatas wrote:
Hello Julian,
Do the users have to have real IP addresses or can they have NAT'd addresses?
In other words,
do they have INCOMING sessions or just outgoing sessions?
actualy there are hundreds of users with registered(real) IP's. So nat'ing,
looking the most
logical solution
Hello Julian,
> Do the users have to have real IP addresses or can they have
> NAT'd addresses? In other words, do they have INCOMING sessions
> or just outgoing sessions?
actualy there are hundreds of users with registered(real) IP's. So nat'ing,
looking the most logical solution, in this case c
Donatas wrote:
hello,
I am sorry for a previous diagram that got wrapped .
If someone could take a look at the picture explaining the problem, I would be
thankfull.
ftp://temp:[EMAIL PROTECTED]/routing_problem.jpg - 136Kbytes.
Short description of a problem: I can't find a way to divert or route
hello,
I am sorry for a previous diagram that got wrapped .
If someone could take a look at the picture explaining the problem, I would be
thankfull.
ftp://temp:[EMAIL PROTECTED]/routing_problem.jpg - 136Kbytes.
Short description of a problem: I can't find a way to divert or route inbound
traffic
please see the scheme below:
user1---[usa]>machine1 machine2
vlan1(default gw)
vlan1>em0(USA) ?<---
-=-=-=-=-->
>So, what's wrong with my setup? How can I correct it and make ipv6
>multicast routing work?
>Thanks!
>
>Vincent
>
Hi Vincent
pim6stat shows that RP-set is empty.
If you are using PIM-SM in ASM mode, you must configure RP/BSR information
#syntax :[time] [priority]
#syntax :[priority]
Hi everybody:
I'm setting up a Freebsd router box to perform ipv6 unicast & multicast
routing, but I cannot make multicast routing work. Unicast routing just
works well.
The router box is set up as follow:
1) FreeBSD 5.2.1 with kame-20041101-freebsd521-snap;
2) Quagga (zebra) 0.96.5 for ipv6 uni
Brilliant, you are a genius!
I need to do a little more testing on my code, but this looks really good!
Many thanks to you and to all who took my question seriously,
dave c
you wrote:
> On Wed, 29 Jan 2003, Dave Cornejo wrote:
>
> > We have this running on Linux, but it's my belief that we're
On Wed, 29 Jan 2003, Dave Cornejo wrote:
> We have this running on Linux, but it's my belief that we're actually
> exploiting a bug or flaw in the Linux routing. The closest I've
> gotten is to set add a route like this on .1:
>
> .1 has a netmask of 0x
>
> route add 192.168.1.2 -interf
On Wed, Jan 29, 2003 at 02:07:32PM -0800, Dave Cornejo wrote:
> Hi,
>
> I've got a unique routing problem:
>
> local network is 192.168.1.0/24
>
> 192.168.1.4
> |
> |
> 192.168.1.1 -- ethernet -- 192.1
> I over-simplified the problem - I'm not talking about 4 hosts on pure
> Ethernet here, I'm really talking about hundreds to thousands with
> some portions running over radio. The rules change dynamically and
> pretty frequently (like potentially on the order of seconds) - I have
> a routing daem
On Wed, Jan 29, 2003 at 02:07:32PM -0800, Dave Cornejo wrote:
> Hi,
>
> I've got a unique routing problem:
>
> local network is 192.168.1.0/24
>
> 192.168.1.4
> |
> |
> 192.168.1.1 -- ethernet -- 192.1
you wrote:
> On Wed, 29 Jan 2003, Dave Cornejo wrote:
>
> > local network is 192.168.1.0/24
> >
> > 192.168.1.4
> > |
> > |
> > 192.168.1.1 -- ethernet -- 192.168.1.2 / global IP addr -- internet
> > |
> > |
> >
On Wed, 29 Jan 2003, Dave Cornejo wrote:
> local network is 192.168.1.0/24
>
> 192.168.1.4
> |
> |
> 192.168.1.1 -- ethernet -- 192.168.1.2 / global IP addr -- internet
> |
> |
> 192.168.1.3
>
> now,
Hi,
I've got a unique routing problem:
local network is 192.168.1.0/24
192.168.1.4
|
|
192.168.1.1 -- ethernet -- 192.168.1.2 / global IP addr -- internet
|
|
192.168.1.3
now, the rules:
i need some help with a routing problem i face.
below is my setup.
|
|
10.0.0.1 firewall/router
|
_ _ _ _ |_ _ _ _ _
| |
|10.0.0.2 |10.0.0.3
Desktop1 Desktop2
10.0.1.1
I don't know where the bug is...
Simple network:
- two routers (1 and 2)
- host C with IP 192.168.1.3
- host S with IP 192.168.2.1
All machines are FreeBSD 4.3-STABLE.
Router 1 routes pkts between the Internet and 192.168.1.0
Router 2 routes pkts between 192.168.1.0 and 192.168.2.0
On Tue, 17 Apr 2001, Peter Brezny wrote:
> The excerpt from my rc.conf mostly illustrates what I'm trying to do.
> I want to connect a host (10.30.1.15) to xl1 So that I can partition
> it's traffic from that of the lan connected to xl2.
>
> 10.30.1.1 GWxl0 10.30.1.30 FW xl210.20.30.
The excerpt from my rc.conf mostly illustrates what I'm trying to do. I
want to connect a host (10.30.1.15) to xl1 So that I can partition it's
traffic from that of the lan connected to xl2.
10.30.1.1 GWxl0 10.30.1.30 FW xl210.20.30.1 LAN
|
You have one subnet (10.30.1/24) accessible through two interfaces.
That causes the kernel 'cognitive dissonance' :-}.
Regards,
Justin
On Tuesday, April 17, 2001, at 07:07 AM, Peter Brezny wrote:
> The excerpt from my rc.conf mostly illustrates what I'm trying to do. I
> want to connect a h
At 2001-04-17T14:07:08Z, Peter Brezny <[EMAIL PROTECTED]> writes:
> 10.30.1.1 GWxl0 10.30.1.30 FW xl210.20.30.1 LAN
> |
> xl1
> |
> |
> 10.30.1.15 FW - 10.20.15.1 LA
The excerpt from my rc.conf mostly illustrates what I'm trying to do. I
want to connect a host (10.30.1.15) to xl1 So that I can partition it's
traffic from that of the lan connected to xl2.
10.30.1.1 GWxl0 10.30.1.30 FW xl210.20.30.1 LAN
|
Hi
I am having a machine with 3 interfaces, fxp0, nge0 and nge1. nge0 and
nge1 are pseudo ethernet interfaces implemented using 'ng_eiface'
netgraph nodes in freebsd-current.
I wish that the response to a ping from host1(some machine on LAN)
to fxp0/nge0/nge1 should come from the respective inte
79 matches
Mail list logo
