at least I would know it’s
a problem unique to me.
Thanks.
- Chris
> On Oct 5, 2025, at 23:40, Lexi Winter wrote:
>
> Chris Ross wrote in <1cb5332a-5e7e-420a-a6ac-3f2d70a0b...@distal.com>:
>> 1. Is interface renaming just too dangerous to use?
>
> i use interface renaming on many systems and have not run into problems
>
complicated, and also to change as few variables as
possible. But, there are too many variables here already, I now see.
I don’t know that removing the switches is possible, but everything else
should be. I’ll try to prep a system for that so that I can experiment
when I am able to next deny internet
> On Sep 18, 2025, at 16:36, Chris Ross wrote:
>
>> On 17 Sep 2025, at 14:20, Chris Ross wrote:
>> So, on the idea of trying to back-date the whole machine, I have ZFS
>> snapshots of the whole root from just before the first upgrade,
>> Aug 7/8. […]
>
>
> On 17 Sep 2025, at 14:20, Chris Ross wrote:
> So, on the idea of trying to back-date the whole machine, I have ZFS
> snapshots of the whole root from just before the first upgrade,
> Aug 7/8. […]
Brief update, more to come later I hope.
I don’t know all of the magic of freebsd
e to doing that,
respond off-list (off freebsd-net at least). I thought I’d answered
the kernel question, but last night showed that 14.1 kernel doesn’t
always work, to be sure. If I can run as 14.1 again, for a few days
or weeks, it will confirm at least that it’s my side for sure that’s
changed.
- Chris
> On Sep 16, 2025, at 23:24, Chris Ross wrote:
>>
>>>
>>> On Sep 15, 2025, at 15:05, Tom Pusateri wrote:
>>>
>>> I would try running the 14.3p2 system without the VLAN configuration and a
>>> direct connection to the upstream pro
> On Sep 15, 2025, at 18:54, Chris Ross wrote:
>
>> On Sep 15, 2025, at 15:01, Ronald Klop wrote:
>>
>> Are you able to boot a 14.2 kernel?
>> To split the search space in two.
>
> I could do that. What’s the easy way to get an unpacked 14.2 generic am
On 2025-09-15 17:24, Chris wrote:
On 2025-09-15 15:54, Chris Ross wrote:
On Sep 15, 2025, at 15:01, Ronald Klop wrote:
Are you able to boot a 14.2 kernel?
To split the search space in two.
I could do that. What’s the easy way to get an unpacked 14.2 generic amd64
kernel?
I can install a
On 2025-09-15 15:54, Chris Ross wrote:
On Sep 15, 2025, at 15:01, Ronald Klop wrote:
Are you able to boot a 14.2 kernel?
To split the search space in two.
I could do that. What’s the easy way to get an unpacked 14.2 generic amd64
kernel?
I can install a VM at work and copy it, but I assume
ace I can do that. It just requires rewriting all of the systems config
to know that the
outside is different than it is now, which _should_ be easy, but I don’t know
the depth of
it since I haven’t done it in eons. I’ll look to find a time to try that.
- Chris
know anything else I can gather to help track this regression.
-Chris
> It is a patch to dhclient, not dhcpcd but does the same issue potentially
> apply?
>
I don’t know, but I think that isn’t my problem. It seems like the NS that
dhcpcd is sending is alright, and tcpdump doesn’t see an NA coming
back in at all.
- Chris
level, I’m just like “But I
didn’t change anything!!!” At least, that’s what my head keeps telling me. :-)
- Chris
can try to switch back
to 14.1, I’ll research whether I can do that via ZFS snapshots without it being
an act of no return. Google will tell me. Otherwise, I may try booting a 14.1
kernel and see what that does. Might break things with a 14.3 user land, but
easy to try.
- Chris
s like that. Try ipv6rs
ipv6rs
#ia_na 0
ipv6ra_autoconf
# Request a /56, then from that allocate the following subnets as noted
# 12 14 17 A4 DD 72 0F 66
ia_pd 0/::/56 int1/18 int2/20 int3/23 int4/164 int5/221 int6/114 int7/15
int8/102
---
“intN” replacements and different IPv6 subnets, but the above is what I have in
effect.
Thanks. Apologies to anyone who isn’t deeply involved for the long message.
:-)
- Chris
> On Mar 31, 2025, at 16:05, Marek Zarychta
> wrote:
> Hello Chris,
>
> our ip6 network stack is old and likely still relying on the older RFC 3041,
> even though RFC 4941 is mentioned in the man pages. However, both have been
> obsoleted by RFC 8981. If you're op
see information about setting these to 1,
and on using `ipv6_privacy` in /etc/rc.conf (which set them to 1), which
I did not do.
Is there documentation about what these variables mean, and if “2” is
a useful value different than “1”? If so, how are they different?
Thanks.
- Chris
> On Sep 20, 2024, at 06:15, DutchDaemon - FreeBSD Forums Administrator
> wrote:
>
> On 19-9-2024 19:43, Chris Ross wrote:
>> Alright. Coming back to this, I was clearly not paying attention. At the
>> time I stopped seeing the aforementioned problem, a new one starte
> On Sep 17, 2024, at 14:46, Chris Ross wrote:
>
> Hmm. Well, I updated my releng/14.1 tree and built a new kernel last night.
> I rebooted and after dhcpcd started up it was emitting the same notices
> for many hours. But, at about 07:30 this morning it stopped. It’s now
> On Sep 16, 2024, at 18:02, Chris Ross wrote:
>
> Build was from releng/14.1 back at the start of August. Looking
> now, I see that I’m behind by 24 commits, so maybe should try
> updating.
Hmm. Well, I updated my releng/14.1 tree and built a new kernel last night.
I reb
quot;
pflog_enable="YES"
(host) pf.conf:
EXT_ADDR="192.168.1.2"
set skip on { lo0, lo1 }
nat pass on wlan0 from { lo1 } to any -> $EXT_ADDR
rdr pass on wlan0 proto tcp from any to { lo1 } -> $EXT_ADDR
Exchanging the EXT_ADDR value with your hosts NIC address. I use
th
ilt after the recent
> zfs patch set hit) on stable/14 and it is not seeing that -- but it is not a
> router, it is an end-node running rtsold and gets its IPv6 address via SLACC
> from the router.
I also tried to reproduce this on a couple of non-router machines
and was not able to.
- Chris
Apologies for lack of important context, the below discusses a FreeBSD
14.1 amd64 system.
Thank you.
> On Sep 16, 2024, at 16:05, Chris Ross wrote:
>
> Hello. Following the earlier thread "DHCPv6 IA_PD - how-to” I have been
> bringing up a new gateway router for my network.
ption rapid_commit
require dhcp_server_identifier
slaac private
noipv6rs
noipv4
noipv4ll
allowinterfaces vlan0
interface vlan0
ipv6only
ipv6rs
ipv6ra_autoconf
ia_pd 0/::/56 intnet1/42 intnet2/56
Thanks.
- Chris
> On Aug 1, 2024, at 12:17, Roy Marples wrote:
>
> On Thu, 01 Aug 2024 16:24:54 +0100 Chris Ross wrote ---
>>
>> [Long message, apologies. Thoughts mostly after the log output.]
>>
>>> On Jul 24, 2024, at 04:12, Roy Marples r...@marples.name>
uld I ever
need to review the settings in the future.
I just wondered if having two methods is by design, as that way
one can have one value for tcp and another for udp if one goes
the sysctl route.
I think LOG_IN_VAIN=YES sets both these MIBs to 1.
--Chris
next question. Sub-interfaces
or alias interfaces maybe?
Thank you.
- Chris
try to _get_ an
address if there’s already an address, but. Maybe this
is a dhcpd problem, where it shouldn’t respond to requests
from the local address?
Thanks all, sorry for the long message.
- Chris
> On Jul 26, 2024, at 23:21, moto kawasaki wrote:
>
>
> Hi Chris, all
>
> I am struggling the same problem too, and here is my working
> configuration for dhcp6c in my test environment.
> Hope this can be help.
Thank you, moto-san. Roy was/is helping me get dhcpcd w
stion might provide me with what I need
as well. Otherwise, an example or three of receiving and utilizing an
IA_PD response is what I am looking for.
- Chris
the PD, so I’d have to code all of that myself.
Thank you.
- Chris
On 2024-06-14 05:50, Ed Maste wrote:
On Wed, 12 Jun 2024 at 18:05, Chris wrote:
As Rodeney already effectively explains; dropping packets makes routing,
and discovery exceedingly difficult. Which is NOT what the average user
wants,
This is on end hosts only, not routers (which already drop
On 2024-06-13 06:34, Rodney W. Grimes wrote:
On 2024-06-12 15:05, Chris wrote:
> On 2024-06-12 14:47, Rodney W. Grimes wrote:
>>> I propose that we start dropping inbound ICMP REDIRECTs by default, by
>>> setting the net.inet.icmp.drop_redirect sysctl to 1 by default
On 2024-06-13 06:34, Rodney W. Grimes wrote:
On 2024-06-12 15:05, Chris wrote:
> On 2024-06-12 14:47, Rodney W. Grimes wrote:
>>> I propose that we start dropping inbound ICMP REDIRECTs by default, by
>>> setting the net.inet.icmp.drop_redirect sysctl to 1 by default
On 2024-06-13 06:34, Rodney W. Grimes wrote:
On 2024-06-12 15:05, Chris wrote:
> On 2024-06-12 14:47, Rodney W. Grimes wrote:
>>> I propose that we start dropping inbound ICMP REDIRECTs by default, by
>>> setting the net.inet.icmp.drop_redirect sysctl to 1 by default
On 2024-06-13 06:34, Rodney W. Grimes wrote:
On 2024-06-12 15:05, Chris wrote:
> On 2024-06-12 14:47, Rodney W. Grimes wrote:
>>> I propose that we start dropping inbound ICMP REDIRECTs by default, by
>>> setting the net.inet.icmp.drop_redirect sysctl to 1 by default
On 2024-06-13 06:34, Rodney W. Grimes wrote:
On 2024-06-12 15:05, Chris wrote:
> On 2024-06-12 14:47, Rodney W. Grimes wrote:
>>> I propose that we start dropping inbound ICMP REDIRECTs by default, by
>>> setting the net.inet.icmp.drop_redirect sysctl to 1 by default
On 2024-06-13 06:34, Rodney W. Grimes wrote:
On 2024-06-12 15:05, Chris wrote:
> On 2024-06-12 14:47, Rodney W. Grimes wrote:
>>> I propose that we start dropping inbound ICMP REDIRECTs by default, by
>>> setting the net.inet.icmp.drop_redirect sysctl to 1 by default
On 2024-06-12 15:05, Chris wrote:
On 2024-06-12 14:47, Rodney W. Grimes wrote:
I propose that we start dropping inbound ICMP REDIRECTs by default, by
setting the net.inet.icmp.drop_redirect sysctl to 1 by default (and
changing the associated rc.conf machinery). I've opened a Phabricator
r
very exceedingly difficult. Which is NOT what the average user
wants,
or expects. I use "set block-policy drop" in pf(4). But as already noted,
this is for "filtering" purposes. Your suggestion also has the negative
affect
of hanging remote ports. Which can result in other negative results by peers.
Please don't. :)
--Chris
On 2024-03-14 21:13, Sreenath Battalahalli wrote:
Hi Chris,
Thanks for your message.
The wifi continues to be associated with access point, and I can ping 1.1.11
as well.
My USB wifi interface is rtwn(earlier urtwn)
It is just that DNS queries fail, even when 1.1.1.1 is accessible, at least
okups, are you still
associated?
eg; does the output of ifconfig still show associated? What are the settings
in rc.conf(5) related to your network setup?
Thanks,
Sreenath
HTH
--Chris
> On Nov 9, 2022, at 14:32, Patrick M. Hausen wrote:
>
>> Am 08.11.2022 um 06:38 schrieb Chris Ross :
>> I have a newer Freebsd 12.3 system with lagg across two 1gbe interfaces.
>> There are a collection of vlan interfaces on the lagg.
>>
>> I would
couple switches away on a single gigabit connection.
Looking on the Cisco switch, the port-channel (connected to the lagg) claims
"BW 200 Kbit/sec”.
Happy to share config with anyone who may be able to help, but won’t paste it
all here.
- Chris
is is the "net" mailing list, but any info about
other built-in components would be helpful as well.
Thanks,
Chris
still so in 13 or CURRENT, and/or let me know if
I’m doing something wrong?
- Chris
ssign a
name
via the adapters MAC address -- ie; assign the name us0 | ue1 to the
adapter/NIC
your interested in by it's MAC address and that would give it to you.
HTH
Chris
--HPS
0xBDE49540.asc
Description: application/pgp-keys
way
twice despite thinking I wasn’t.
Sorry for the noise.
- Chris
> On Jun 12, 2022, at 12:40, Chris Ross wrote:
>
>
> Tl;dr;
> I don’t know why I’m getting an EINVAL from a call to bind for a second socket
>
>
>
>
> 20 years ago, I s
be. I’m probably just missing
Something simple, and am looking for another set of eyes.
Thanks all. Contact me off list if you like, or on-list if it’s obvious
what I’ve done and it will help others.
- Chris
[1] https://github.com/vzaliva/simpleproxy
[2] inet6(4), "Intera
ndicates they brag on having better privacy than
their competition. Are they using any privacy extensions that may affect
your ability to ping(8) || traceroute(8) -- TCP/UDP/ICMP? Or is it just
that gig1-1-1.gw.davsca11.sonic.net's BGP is out of date (stale)?
HTH
--Chris
===
Mark Millard
marklmi at yahoo.com
0xBDE49540.asc
Description: application/pgp-keys
2020 Quarterly report[1]
as well as a report by Adrian that "We know whats missing"[2] somewhat
later on the mailing list.
So where can I find it? :-)
Thank you for all your time, and consideration.
--Chris
1. https://www.freebsd.org/status/report-2020-07-2020-09.html
2. https:/
On 2022-01-12 10:48, Gleb Smirnoff wrote:
Hi!
Thanks for the informative writeup, Gleb!
Untrimmed, sorry...
[crossposted to current@, but let's keep discussion at net@]
I have already touched the topic with rrs@, jtl@, tuexen@, rscheff@ and
Igor Sysoev (author of nginx). Now posting for wid
being done on re(4).
IOW if we can help in any way. We'll make ourselves available.
Thanks again.
--Chris
Regards,
Kevin
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe
lternatives and no users.
I should have stated the latter more explicitly.
> more important than the fact that it is old or we have more choices
> in the ports tree. If we have negative factors on maintaining them,
> removing them would be one of the choices as a result. If the
>
> and that "dns" already has "s" for system, so just "dns" is good
> with me :-)
> >> > >
> >> > > That's a good point.
> >>
> >> I don't agree. The term dns is too generic. People are often running
> &
implementation the rc dependency chains should stay the same.
Thanks!
--
Andriy Gapon
--Chris
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
But I'm also using pf, nat, and rdr. If that should that make a difference.
--Chris
--
Victor Sudakov, VAS4-RIPE, VAS47-RIPN
2:5005/49@fidonet http://vas.tomsk.ru/
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/list
your hoping to find; pfctl(8), pfctl -s,
and pfctl -T are a few examples.
HTH
--Chris
--
John W. O'Brien
OpenPGP keys:
0x33C4D64B895DBF3B
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubsc
On Tue, 26 Nov 2019 08:06:37 +0200 Artem Viklenko ar...@viklenko.net said
Sorry, small update.
Just re-cheked. It was not final change... wrong place. I've set it even
smaller than 4096. Now it 3072.
Bummer. :(
Sorry.
No problem. Thanks for trying! :)
--Chris
26.11.19 07:55,
uch, Artem. I'll have a closer look. I'm thinking of
taking your concept, and upping it to 7k. I'll post back, if anything good
comes of it. :)
Hope this helps.
It does. :)
--Chris
26.11.19 02:44, Chris пише:
> Or at least make it non fatal.
> OK here's the sto
iconductor Co., Ltd.'
device = 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'
class = network
subclass = ethernet
Thanks again!
--Chris
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
OK. I'll have a look and see what I can come up with. I'll poke you
when I can come up with anything worth while. BTW I meant what I said
about sending you one of these cards. Lemme know if you're interested.
Thanks again!
--Chris
-adrian
__
working on this (@adrian ?). :-)
Anyway, if anyone can further enlighten me on WiGig on FreeBSD. I'd *greatly*
appreciate it. :-)
Thanks!
--Chris
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To
a.
(The patches are in Git format, I applied them to the read-only
freebsd master tree on GitHub.)
Chris
>From 65145b74d3dae68feddcf8a2aad235c3f0a981e9 Mon Sep 17 00:00:00 2001
From: Chris Torek
Date: Mon, 8 Feb 2016 18:55:30 -0800
Subject: [PATCH 1/3] ip multicast debug: fix strings vs define
e
Dell PowerConnect 2724 and 2824 switches, which claim to support jumbo frames.
I’ll have to find out if I have to _do_ anything to support that, but it should
work. Thanks for the suggestion, I’ll look into that…
- Chris
signature.asc
Description: Message signed with OpenPGP using GPGMail
(unless I missed something) to the natural
MTUs on all interfaces. The vlan’s all show 1496, and the bee’s (and lagg0)
show 1500. The options on each of the bce’s show VLAN_MTU, and a few other
VLAN_ options.
- Chris
> On Mon, Dec 5, 2016 at 10:00 AM, Chris Ross wr
across pflog0,
vlan0 (external network) and vlan7 (internal network). I’d be happy to answer
any questions, or provide the traces off-list.
Does anyone have any idea what I’ve missed? Thank you very much for your help.
- Chris
quirement is guaranteed to be "sx lock first, then mtx lock"
(because the other way around causes sleeping while holding a
regular mutex!).
Chris
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To uns
driver or the bridge code? I.e.,
does the bridge driver need to release its lock here,
and if so, is that actually safe to do? (We might need
to restart the loop over all the members if we drop the
lock.)
- Or if the bridge driver should retain its lock, can it
use an sx lock here, to p
Thank you - I will check that out.
From: "Kevin Oberman"
To: "chris"
Cc: "freebsd-net"
Sent: Friday, July 22, 2016 2:23:26 PM
Subject: Re: Slow performance with Intel X540-T2 10Gb NIC
On Fri, Jul 22, 2016 at 6:48 AM, Chris Dunbar < ch...@dunbar.net
x and Linux so that doesn't quite
add up either. I may have to break out Wireshark and make some packet captures
to see if I can tell what's going on. If I find anything, I will be sure to
share it.
Regards,
Chris
From: "Sami Halabi"
To: "chris"
Cc: "free
.
Regards,
Chris
- Original Message -
From: "chris"
To: "freebsd-net"
Sent: Thursday, July 21, 2016 4:53:40 PM
Subject: Re: Slow performance with Intel X540-T2 10Gb NIC
Eric, et al:
I haven't tried netperf yet, but I do have some new information to share. I
h
t be nutty in my BIOS settings (or elsewhere) that would cause the new
server + FreeBSD 10.3 + X540 to equal slow performance?
Regards,
Chris
From: "Eric Joyner"
To: "chris" , "freebsd-net"
Sent: Thursday, July 21, 2016 1:27:10 PM
Subject: Re: Slow performance wi
kes a
noticeable difference. I'm increasingly skeptical that I am going to find a
setting or two that more than doubles the speed I am currently experiencing.
I am open to any and all suggestions at this point.
Thank you!
Chris
___
freebsd-net@freebsd.o
On Wed, 11 May 2016 11:27:20 -0700 "K. Macy" wrote
> On Wed, May 11, 2016 at 7:56 AM, Chris H wrote:
> > On Tue, 10 May 2016 10:25:24 -0700 hiren panchasara
> > wrote
> >
> >> + Kip, Scott.
> >>
> >> On 05/10/16 at 04:46P, David
?
>
> Kip or Scott may provide more info.
>
> Cheers,
> Hiren
--Chris
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
wants to received a lot of data.
Question: how do I set TcpRcvBuf on the ssh server? It's undocumented
so I guessed. Neither sshd_config ("TcbRcvBuf=8192") nor sshd_flags
("-oTcpRcvBuf=8192") worked.
Thank you,
Chris
[1] ssh -oTcpRcvBuf=8192 user@host
[2] https://
x.
Is there an easy place to get the packet timestamp? I saw the timestamp in
the flags, but it wasn't clear to me that it would be a received timestamp.
Also, since I'm not a regular list reader, please keep my email address on
the th
freebsd
> >
> >
> >
> >
> > What is the problem??
To effectively address your issue. More information is required;
What version, and revision of FreeBSD are you trying this on?
What is the contents of your /etc/pf.conf?
What is the error, or other reason that leads
O_SNDBUF) to get the value
set by setsockopt(SO_SNDBUF) -- use something else
Original thread from August 2015:
https://www.mail-archive.com/freebsd-net@freebsd.org/msg49793.html
Thank you,
Chris
___
freebsd-net@freebsd.org mailing list
https://lists
On 8/25/15 3:47 PM, Chris Stankevitz wrote:
Can anyone explain my abysmally small TCP window?
So I believe this is the story:
1. openssh limits the size of some outgoing buffer to 65KB
2. openssh/HPN tries to improve on this by increasing the size of the
outgoing buffer to match getsockopt
ing client is
limiting -- although I'm not sure why). This effectively caps my
bandwidth to 20 Mbps.
With iperf this limitation does not exist -- nor does the need to tune
these values (except for buf_inc which can get the ball rolling faster
as you pointed out).
sed 'dd
if=/dev/zero bs=1m | ssh` but at the time I did not know about `foo |
ktrace bar`.
Although if there is such a thing named "pipe buffer" I'm not sure it
would have made a difference...
Chris
___
freebsd-net@freebsd
change
Increase recvspace on "sending client": no change
Increase sendspace on "receiving server": no change
Increase recvspace on "receiving server": sending client's S-BCNT
increases proportionally!
I'm going to try Kurts parameters now...
ency between writes using ktrace to help figure this
out...
Yes, I believe something like this is happening now.
Thank you again for your help... this thread is proving to me one of
those quantum leap moments for me in terms of FreeBSD knowledge.
Chris
_
John-Mark,
Thank you for your reply.
On 8/25/15 6:03 PM, John-Mark Gurney wrote:
Chris Stankevitz wrote this message on Tue, Aug 25, 2015 at 15:47 -0700:
# cat /dev/urandom | ssh root@host 'cat > /dev/null'
Don't use this for testing... use /dev/zero or some other devic
On 8/25/15 4:11 PM, Bjoern A. Zeeb wrote:
On 25 Aug 2015, at 22:47 , Chris Stankevitz wrote:
Can anyone recommend some tools/tricks to figure out what in FreeBSD and/or
>> base SSH is limiting the send/recv buffer and/or TCP window?
if you have the memory, try these s
the send/recv buffer and/or TCP window?
Thank you,
Chris
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
et6'',
``atalk'',``ipx'', and ``link''. The default if available is
``inet'' or otherwise ``link''. ``ether''and ``lladdr'' are
synonyms for ``link''.
Can't you lock it down, via ETHER?
Or ma
exist any more.
I can't speak from personal experience to the rest. But as to
bpfstat(8); it was merged into netstat(1) ~RELENG_7.
--Chris
>
> q4)
> When activating zerocopy, should I immediately see a performance boost on
> the mac
the blinking lights to help determine which NIC belongs
to which number. Not extremely elegant, but will at least help
narrow down which NIC, is which.
Then in the end, you can allocate your NIC's out of rc.conf(5).
--Chris
>
> -- Martin
>
> _
On Thu, 04 Dec 2014 16:32:04 -0800 "Chris H" wrote
> On Thu, 4 Dec 2014 14:41:11 -0800 Adrian Chadd wrote
>
> > On 4 December 2014 at 14:24, Martin Hanson
> > wrote: > It is worth mentioning that the ONLY reason why this worked is
> > because > the v
butions, and would
like to be kept in the loop. :)
@Martin, Thank you very much for your diligence, and for
sharing your experience, and *especially* your solution.
@Warren; Thanks for your continued dedication!
--Chris
>
>
>
> -a
>
Dear Mailinglist
I just found out that there are two possibilities to get multicast
working in FreeBSD
There is:
- kldload ip_mroute.ko or
- to compile the kernel with: options MROUTING
Is there a difference between these two approaches?
I notice that, with a custom kernel, patching is much m
ic
"192.168.1.1 netmask"... broke.
If you have a quick fix I would be really appreciative, but I will say, at
this point I'm being lazy a bit. I haven't really done the homework myself
first. :)
In either case, I really appreciate your help.
thanks
chris
On Sat, Nov 1, 2
ssec-check-unsigned
#
# do IPv6 router advertisements for internal network
#
dhcp-range=::,constructor:re1,ra-only
enable-ra
Any help would be greatly appreciated.
thanks
Chris
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/m
_
freebsd-questi...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
--
Chris Hill ch...@monochrome.org
** [
ference I can see, is that I use STATIC (IPv4 && IPv6), and a default
(IPv4 && IPv6) gateway. If I telnet/ftp/ssh to any of my hosts, IPv6 is always
attempted first (opposite of your output above). This was also the case, when
I didn't enter a specific IP in the rc.conf(5). With on
g
> as you have the details about the tunnel server's IP and the prefix
> you're assigned, you can easily do it manually (or, better, write a tiny
> script to do it for you).
Yes. I have both.
That's good news. Thanks for t
1 - 100 of 315 matches
Mail list logo
