Hello Casey
On 31.10.2013 21:10, Casey Scott wrote:
The problem I'm encountering is that a portion of my outbound internal
traffic is being blocked by ipfw. This is a fresh Freebsd installaion, so
I'm kind of at a loss since the config matches the handbook. Any suggestions
are appreciated.
Did
Hello javocado
On 26.10.2013 00:00, javocado wrote:
i.e. what are the private net blocks for ipv6
The RFC 5156 "Special-Use IPv6 Addresses" [1] is probably the
best documentation for this. And just as reference for IPv4,
there is RFC 5735 "Special Use IPv4 Addresses" [2].
[1] http://ww
Hello
To test tables with IPv6 for use with fail2ban (see thread "IPv6
Support" [1]), I tried it out on a FreeBSD 9.1-RELEASE (r244668)
system. Not all possible rules with tables which include IPv6
addresses seem to work.
[1] http://sourceforge.net/mailarchive/message.php?msg_id=29387087
Hello Pavel
On 28.07.2011 13:24, Pavel Timofeev wrote:
Now if I you want to use forwarding in ipfw I need to build custom kernel.
Yes, this is correct.
I found similar thread
http://lists.freebsd.org/pipermail/freebsd-ipfw/2010-March/004148.html
Have you changed anything since then?
I do
Hello Andrey
On 05.07.2011 21:04, Andrey V. Elsukov wrote:
fwd does not work when ipfw loaded as module.
Ups, did not know this exactly, thanks for clarify. But it really
makes sense that both options are in the kernel.
After sending out my mail, it somehow crossed my mind that this
eventua
Hello Unga
On 05.07.2011 20:22, Unga wrote:
--- On Wed, 7/6/11, Andrey V. Elsukov wrote:
You should add 'options IPFIREWALL' in the your kernel
config too.
ipfw(8) man page for 'fwd' shows to add only the IPFIREWALL_FORWARD.
I guess the manpage implies that 'options IPFIREWALL' is al
Hello Unga
On 05.07.2011 12:47, Unga wrote:
Following ipfw rule develop error indicated:
ipfw add 100 fwd 127.0.0.1,1234 tcp from any to any 1234 out via wlan0
Error:
ipfw: getsockopt(IP_FW_ADD): Invalid argument
Does your kernel have 'options IPFIREWALL_FORWARD' (if this is
needed for 8.1,
Hello Daniel
On 27.04.09 18:19, Daniel Dias Gonçalves wrote:
What may be happening ? I'm with polling enabled on all interfaces, can
you influence ?
If I disable the polling, no network interface work, begins to display
"em4 watchdog timeout".
If you are using polling on the Ethernet interf
Hello
On 31.03.09 09:51, zgabe wrote:
I use the following command as root:
ipfw add 101 fwd pppgateway ipv6 from pppaddress to any
(pppgateway and pppaddress ipv6 addresses)
It throws "getsockopt(IP_FW_ADD): Invalid argument" error!
Thoughts?
I do have a similar setup, which works fin
Hello Julian
On 15.06.08 22:43, Julian Elischer wrote:
Fabian Wenk wrote:
Just use ipfw the same like for IPv4, then since FreeBSD 6.x it does
also support IPv6. If you still have an older version of FreeBSD, use
ip6fw.
there are some features that are not yet suported.. (e.g. tables
Hello Edwin
On 14.06.08 04:27, Edwin Sanjoto wrote:
Do you know how to set firewall for IPv6 using IPFW?
Just use ipfw the same like for IPv4, then since FreeBSD 6.x it
does also support IPv6. If you still have an older version of
FreeBSD, use ip6fw.
bye
Fabian
___
11 matches
Mail list logo
