A
A
asch112017-05-14 16:19:47
FreeBSD
asch11, 2017-05-14 16:19:47

Flies ip address to freebsd. Where did I mess up?

homeserver. in proxmoxe a virtual switch, 2 network cards not in a virtual fra in bridged mode look in the switch, pf is enabled, so far it lets everything through in all directions. In rc.conf, of course, both ip'a of the external and internal interfaces (virtual) are registered like this: f82e064c744b494893b43b9319df43a3.png
however, when loading free on the second one (as if there is no ipchik on the internal interface): 16208575b3e94db1a30818be59a080b0.png
ifconfig em1 192.168.0.4 solves the problem before reboot and as a result, the gateway starts working , pings from a test virtual machine connected via freu are flying ....1e2b464ec2414e3ebfbf1487f40f8c5e.png
And one more thing, when you turn on this homeserver to the provider, I'm afraid of screwing up the thread and, for example, sending him dhtsp answers or requests (it's strange, it gives IPs to unregistered users exclusively for local access 0-0), how can I isolate this traffic? Of course, it immediately comes to mind that vlans, hang up on all interfaces, except for the fact that some kind of vlan 2222 is looking towards the dip... but maybe someone more experienced will say how it is better and with what they eat this in general?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
A
asch11, 2017-05-14
@asch11

figured it out, just an error in rc.confe in the line where the netmasT ipchik is written, corrected everything after the reboot, it’s strange that the rc conf was loaded :( I thought if there was an error, it wouldn’t take off. well, the second part of the question is still valid

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question