@Lord Ruthwein
Jak zinterpretowac i zrealizowac nastepujace sformulowania:
Your lan got that via dhcp.. That is not something lan is normal gotten from anyway because normally you run dhcpd on pfsense, etc. etc.. and it needs to be static.
If you want to run this for your whole network then do this.. Your box needs 2 interfaces min or smart switch and vlans but then gets way more complicated.
Interface your going to connect to your internet - wan, would be bridge in VB. Your Lan side interface in PC would be bridged in VB.
In your PC that is running vb you would not have any binding to the wan nic.
Your PC would have an IP on the lan side bridge interface in vb..
Your pfsense vm in vb would have virt nic connected to your phy wan interface that is bridged and get your public IP from your ISP or if behind nat some rfc1918 from your gateway/router from your ISP. Your lan side network or lan interface in vb would be some different network that is bridged to your lan side PC interface. This would be connected to your phy switching setup. All other devices would be connected here, wireless AP would be connected here.
Your PC would have IP on this network.. This is what it would use for internet access.
My router - 192.168.0.1
My host - 192.168.0.182
pfSense WAN - 192.168.0.48
Well your host is on the pfsense WAN.. As I showed in the my setup your PC running vm IP should be on the interface that is bridged to pfsense lan and your network - can not be connected to your routers network. Do this your going to need another switch. Can not just have 1 router as your only connection.
Your pfsense vm in vb would have virt nic connected to your phy wan interface that is bridged and get your public IP from your ISP or if behind nat some rfc1918 from your gateway/router from your ISP. Your lan side network or lan interface in vb would be some different network that is bridged to your lan side PC interface. This would be connected to your phy switching setup. All other devices would be connected here, wireless AP would be connected here.
To jest chyba jasne, oba interfejsy w trybie bridged zbindowane do odpowiednich kart.
Nie masz czasu aby rozwiązać swój problem, a MY mamy go mieć?
To rozkaz, że musimy Ci podać gotowe rozwiązanie oraz przetłumaczyć powyższy tekst?
Wiesz, my nic nie musimy, a że coś podamy to raczej po to aby nakierować abyś trafił na właściwą drogę i tok myślenia. Ale skoro samemu nie chcesz popracować tylko oczekujesz gotowego rozwiązania to trochę źle trafiłeś. Wiec sobie sam przemyśl czego żądasz i się ogarnij!
pfSense® software is a free, open source customized distribution of FreeBSD specifically tailored for use as a firewall and router that is entirely managed via web interface. In addition to being a powerful, flexible firewalling and routing platform, it includes a long list of related features and a package system allowing further expandability without adding bloat and potential security vulnerabilities to the base distribution.
więc chyba pomyliłeś fora. To FreeBSD/pfsense czyli system BSD, a nie linux
Moderowano: Usunięto część wypowiedzi bez związku z tematem wątku. Takie uwagi należy zawierać w osobnych wątkach do tego przeznaczonych lub zgłaszać poprzez PW.
Temat zamykam.
Zeby cieszyc sie vm pfSense na VB trzeba ustawic na VM VB 2 interfejsy: bridged, host-only. Na vm pfSense em0(WAN) i em1(LAN) adresacja dla em0 z sieci fizycznej, adresacja dla sieci em1 z sieci wirtualnej. To wszystko, i dziala pieknie.
Minusem jest znacznie zwiekszone zuzycie pradu, niestety.
Powodzenia.
Ps. za linki bardzo dziekuje, z pewnosci beda mi niebawem potrzebne.
