Two subnets communicating

SirDice said:
That's because it's gateway_enable, not enable_gateway.
Click to expand...

My bad. It is enable_gateway indeed. It is written correctly in rc.conf. So, I need to create a VLAN. I didn't know that. Thank you bbzz. I'll try it in a few minutes and be back with informations.

Same thing. I can ping 172.23.8.1 and 172.23.0.1 for about two minutes after I restart the server and it just suddenly dies. Checking logs now. Maybe I'll find something useful.
 
Found something a little weird:
Code: 
May 16 19:35:08 s3 dhcpd: DHCPDISCOVER from f4:e3:21:88:e4:d6 via bge1
May 16 19:35:08 s3 dhcpd: [b]imcp_echorequest 172.23.8.253: Invalid argument [/b]
May 16 19:35:09 s3 dhcpd: DHCPOFFER on 172.23.8.253 to f4:e3:21:88:e4:d6 (workstation2) via bge1
May 16 19:35:09 s3 dhcpd: DHCPREQUEST for 172.23.8.253 (172.23.0.1) from f4:e3:21:88:e4:d6 (workstation2) via bge1
May 16 19:35:09 s3 dhcpd: DHCPACK on 172.23.8.253 to f4:e3:21:88:e4:d6 (workstation2) via bge1
Can't understand what's bolded. Why
Code: 
echorequest 172.23.8.253: Invalid argument
?

Sorry for the double-post. I thought that I was editing my last post.
 
You currently have some serious networking issues. The server on 172.23.0.1 should be issuing addresses in the 172.23.0.0/21 range. It's currently issuing addresses from the 172.23.8.0/23 range.

Either both subnets are lumped together on the switch, or your FreeBSD machine is only connected to the 172.23.0.0/21 VLAN.

In any case, I seriously recommend finding someone that can configure the network for you, especially the switch.

For everything to start working properly the switch must have 2 VLANs, one for each subnet. You then need a VLAN trunk port to connect your FreeBSD machine on. Only when all that is set up correctly should you configure VLANs on the FreeBSD machine.

If you keep struggling because you don't know exactly what you're doing I can pretty much guarantee you you will get chased around the building by an angry mob of dissatisfied users because they can't work.
 
I wanted it to issue IP addresses in both the subnets. Still, I think I am missing something.

Maybe I could use the first subnet, which is used only from 172.23.0.1 to 172.23.6.3 and get like 20 IPs from there? I could edit the dhcpd.conf like this:
Code: 
subnet 172.23.0.0 netmask 255.255.248.0{
option routers 172.23.0.1;
option broadcast-address 172.23.7.255;
option subnet-mask 255.255.248.0;
option domain-name "s3-network";

pool {
range 172.23.6.4 172.23.6.24;
allow unknown-clients;
Would this work?
 
You must log in or register to reply here.
Back
Top