Well create a php script like
<?php
pfSense_ngctl_attach(".", "re0");
?>Execute that before running daemonology commands. But if you just want to test for one time. I cannot imagine keeping that stable without suppport in teh architecture of pfSense. On Mon, Nov 5, 2012 at 11:31 PM, David Brodski <da...@brodski.eu> wrote: > Thank you for the replay, but I it is not working. > > If I try to use the commands from > > http://www.daemonforums.org/showpost.php?s=192d3b485d84462d3982051f5959b35a&p=19494&postcount=12 > > ngctl mkpeer . eiface hook ether <- works > ifconfig ngeth0 up <- works > > [2.0.1-RELEASE][admin@pfsense.localdomain]/root(5): ngctl mkpeer ngeth0: > bridge lower link0 > ngctl: send msg: Protocol family not supported > > and that is where it does not work anymore. > > If I try your command: > > [2.0.1-RELEASE][admin@pfsense.localdomain]/root(2): ngctl ether re0 -iirc > ngctl: "ether": unknown command > > Any idea what went wrong? > > Thanks, > David > > General information: > re0 is the external interface, ngeth0 is created after the first command. > I can assign an other mac to ngeth0 but of course I can not send any data. > > [2.0.1-RELEASE][admin@pfsense.localdomain]/root(8): ngctl list > There are 5 total nodes: > Name: <unnamed> Type: socket ID: 00000010 Num hooks: 0 > Name: <unnamed> Type: socket ID: 0000000f Num hooks: 0 > Name: ngctl31879 Type: socket ID: 0000002e Num hooks: 0 > Name: ngeth0 Type: eiface ID: 0000002a Num hooks: 0 > Name: fwe0 Type: ether ID: 00000001 Num hooks: 0 > > > [2.0.1-RELEASE][admin@pfsense.localdomain]/root(7): ifconfig > fwe0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 > options=8<VLAN_MTU> > ether 02:00:00:00:00:00 > ch 1 dma -1 > fwip0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 > lladdr 0.0.0.0.0.0.0.0.a.2.ff.fe.0.0.0.0 > re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > > > options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC> > ether 00:03:1d:03:e8:1c > inet6 fe80::203:1dff:fe03:e81c%re0 prefixlen 64 scopeid 0x3 > inet 83.XXX.XXX.XX netmask 0xfffffe00 broadcast 83.XXX.XXX.255 > nd6 options=3<PERFORMNUD,ACCEPT_RTADV> > media: Ethernet autoselect (100baseTX <full-duplex>) > status: active > re1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > > > options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC> > ether 00:03:1d:03:e8:1d > inet 192.168.140.2 netmask 0xffffff00 broadcast 192.168.140.255 > inet6 fe80::203:1dff:fe03:e81d%re1 prefixlen 64 scopeid 0x4 > nd6 options=3<PERFORMNUD,ACCEPT_RTADV> > media: Ethernet autoselect (1000baseT <full-duplex>) > status: active > plip0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> metric 0 mtu 1500 > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 > options=3<RXCSUM,TXCSUM> > inet 127.0.0.1 netmask 0xff000000 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 > nd6 options=3<PERFORMNUD,ACCEPT_RTADV> > pfsync0: flags=0<> metric 0 mtu 1460 > syncpeer: 224.0.0.240 maxupd: 128 syncok: 1 > pflog0: flags=100<PROMISC> metric 0 mtu 33200 > enc0: flags=0<> metric 0 mtu 1536 > ngeth0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu > 1500 > ether 00:00:00:00:00:00 > inet6 fe80::203:1dff:fe03:e81c%ngeth0 prefixlen 64 scopeid 0xa > nd6 options=3<PERFORMNUD,ACCEPT_RTADV> > > > On 05.11.2012 16:56, Ermal Luçi wrote: > > you have to attache the interface yourself to netgraph. > > > > ngctl ether $iface -iirc > > > > After that you can continue renaming the interface etc... > > But you will have issues with restart of pfSense. > > > > There was never something pushing this to be implemented. > > > > > > On Mon, Nov 5, 2012 at 2:16 PM, David Brodski <da...@brodski.eu > > <mailto:da...@brodski.eu>> wrote: > > > > Hi, > > > > my ISP gives me one global IP per computer (mac address / dhcp) > > attached to my cable modem. When I use pfsense as firewall, I can > > only get one IP since it only has one wan interface. I do not know > > the IP addresses before, they are not static IPs. > > Is there a way to do that in pfsense without adding another > > ethernet card? I already found similar topics, but they are quit > > old and the links are not working > > (http://www.mail-archive.com/support@pfsense.com/msg02096.html). > > It seams that either I need the kernel modul ng_ether.ko or change > > some scripts since I can not add a bridge to my interfaces. > > If I run "ngctl list" I'll get unamed interfaces and the real > > interfaces re0 and re1 are not in the list, similar to > > http://forum.pfsense.org/index.php/topic,36722.msg189344.html . > > The solution they describe is missing some steps or I just do not > > get it :-D. > > I also tried > > > http://www.daemonforums.org/showpost.php?s=3301fb2839be371ede93676af845f86b&p=19494&postcount=12 > > but the line "ngctl mkpeer ngeth0: bridge lower link0" gives me an > > error (probably the missing ng_ether.ko). > > > > Is there a way to get that kind of configuration? > > > > This is the first time working with BSD so don't be to harsh :-) > > > > Thanks for the help, > > David > > > > -- > > > > > > _______________________________________________ > > List mailing list > > List@lists.pfsense.org <mailto:List@lists.pfsense.org> > > http://lists.pfsense.org/mailman/listinfo/list > > > > > > > > > > -- > > Ermal > > > > > > _______________________________________________ > > List mailing list > > List@lists.pfsense.org > > http://lists.pfsense.org/mailman/listinfo/list > > > > _______________________________________________ > List mailing list > List@lists.pfsense.org > http://lists.pfsense.org/mailman/listinfo/list > > -- Ermal
_______________________________________________ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
