Search
Results (250)
- Bug #9803 (Rejected): Bridge: client's traffic reaches PfSense but nothing comes back (SR-IOV)
- I am configuring my pfSense for the first tim ... any rule" bridge0 udp 255.255.255.255:67 <- 0.0.0.0:68 NO_TRAFFIC:SINGLE bridge0 udp 0.0.0.0:68 -> 255.255.255.255:67 SINGLE:NO_TRA ... know if I can provide any more information.
- Feature #9768 (Duplicate): IPsec for site-to-site scenario where one side has dynamic ip
- In practice really many sys admins have a nee ... /ConnSection#leftright-End-Parameters
- Bug #9767 (Resolved): Interesting Traffic Will not Initiate an IPsec VTI tunnel.
- Interesting Traffic Will not Initiate an IPse ... aggressive = no rightsubnet = 172.22.177.1,0.0.0.0/0 leftsubnet = 172.22.177.2/30,0.0.0.0/0 Status of IKE charon daemon (strongSwan ... key authentication con1000: child: 0.0.0.0/0|/0 === 0.0.0.0/0|/0 TUNNEL, dpdaction=restart Shunted Conn ... ry 3060s, dpd action is restart local: 0.0.0.0/0|/0 remote: 0.0.0.0/0|/0 ipsec1000: flags=8051<UP,POINTOPOINT ... aggressive = no rightsubnet = 172.22.177.2,0.0.0.0/0 leftsubnet = 172.22.177.1/30,0.0.0.0/0 Status of IKE charon daemon (strongSwan ... key authentication con1000: child: 0.0.0.0/0|/0 === 0.0.0.0/0|/0 TUNNEL, dpdaction=restart Shunted Conn ... ry 3060s, dpd action is restart local: 0.0.0.0/0|/0 remote: ...
- Bug #9668 (Resolved): Running /etc/rc.newipsecdns breaks FRR BGP on VTI interfaces
- Running /etc/rc.newipsecdns breaks FRR BGP on ... > - selected route, * - FIB route K>* 0.0.0.0/0 [0/0] via 172.25.228.1, vtnet1, 00:03:07 ... > - selected route, * - FIB route K>* 0.0.0.0/0 [0/0] via 172.25.228.1, vtnet1, 00:06:55 ... </pre> Restarting FRR seems to clear it.
- Feature #9605 (Duplicate): Support custom CIDR on IPSEC Auto-Exclude LAN Address
- Hi. In my scenario, i have multiple LANs, and ... nnected). Problem is that, if i declare a 0.0.0.0/0 Remote Network on IPSEC to force each LAN ... tion. We know that is way to blunt to use 0.0.0.0/0 on ipsec, but since those lans inside my p ... d add this connection block inside ipsec.conf
- Bug #9602 (Resolved): Dynamic DNS with DigitalOcean not working
- After activating Dynamic DNS for Digital Ocea ... Dns: cacheIP != wan_ip. Updating. Cached IP: 0.0.0.0 WAN IP: 82.213.208.103 Initial update. Jun ... hp: phpDynDNS (@): (Unknown Response) </pre>
- Bug #9442 (Not a Bug): Wrong route when using openvpn client and multiple subnet ?
- I'm using 2.4.4 version I setup an openvpn ... fault 192.168.10.1 UGS 112829 1500 vmx1 10.0.0.0/24 192.168.62.200 UGS 1588 1500 vmx0 10.8 ... 68.62.100 link#1 UHS 538689 16384 lo0 </pre>
- Bug #9429 (Rejected): When enabling https access to WebConfigurator
- Running pfSense dev 2.5.0.a.20190322.1846 rel ... 1', the output was 'nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) ngin ... ess already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) ngin ... ess already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) ngin ... ess already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) ngin ... ess already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) ngin ... /24 15:17:21 [emerg] 83087#100219: bind() to 0.0.0.0:443 failed (48: Address already in use) Mar ... /24 15:17:21 [emerg] 83087#100219: bind() to 0.0.0.0:443 failed (48: Address already in use) Mar ... /24 15:17:21 [emerg] 83087#100219: bind() to 0.0.0.0:443 failed (48: Address already in use) Mar ... /24 15:17:21 [emerg] 83087#100219: bind() to ...
- Bug #9338 (New): igmpproxy ignoring downstream vlan interface
- Hi, following config doesn't accept any IG ... it 0 threshold 1 altnet 128.0.0.0/1 altnet 0.0.0.0/1 phyint vtnet1.13 downstream ratelimit 0 ... it 0 threshold 1 altnet 128.0.0.0/1 altnet 0.0.0.0/1 phyint vtnet1 downstream ratelimit 0 th ... abled </pre> I believe this is a bug.
- Bug #9324 (Resolved): IPv6 on top of a PPPOE ... terface to default route, not pppoe interface
- Hi, Have been seeing this since at least 2.4 ... k]/root: route -n show default route to: 0.0.0.0 destination: 0.0.0.0 mask: 0.0.0.0 gateway: 212.42.162.225 fib: 0 ... g/max/std-dev = 16.207/16.635/17.052/0.286 ms