Solved networking issues with static IP

GlitchyDot

GlitchyDot

Hi, i did fresh install of FreeBSD Release 14.1 on my gaming rig and i choose to use static IP instead of DHCP. Now i have issues.
My network setup is:
Netgear Nighthawk M1 -> Zyxel GS1200-8 Web Managed Switch --> one port for WS (Linux) one port for my gaming and laptopt on wifi.
From laptop on wifi i can ssh to my WS but i can not ssh to my gaming rig , from my gaming i can ssh to WS and rig has connection to internet.
Everything is ipv4 only.
Ive added ifconfig and netstat -r .
 

Attachments

  • ifconfig.txt
    842 bytes · Views: 19
  • netstat.txt
    754 bytes · Views: 16
So, gaming rig: 192.168.1.200/24, default gateway 192.168.1.1. That looks correct if the rest of your systems (the WS and laptop) also have an address in the 192.168.1.0/24 range.

Can you ssh from the WS to the gaming rig? What is the error you're getting? Connection refused or connection timed out? Is sshd(8) actually running on the FreeBSD host?
 
No, can not. ssh: connect to host 192.168.1.200 port 22: Operation timed out. Same from WS.
sshd_enabled="YES" inside my /etc/rc.conf on gaming rig
If i understood correctly i can set up my ip up to xxx.xxx.xxx.255
All pc`s have 192.168.1.1 as gateway and only laptop runs DHCP
ifconfig_wlan0="WPA DHCP" in /etc/rc.conf
 
GlitchyDot said:
No, can not. ssh: connect to host 192.168.1.200 port 22: Operation timed out. Same from WS.
Click to expand...
This is typical behavior when a firewall is blocking the connection.

GlitchyDot said:
If i understood correctly i can set up my ip up to xxx.xxx.xxx.255
Click to expand...
No, up to and including .254. .255 is the broadcast address of that network range. Each range has two addresses you cannot assign to a host, all zeros and all ones. In a 192.168.1.0/24 the 192.168.1.0 (binary; 00000000; all zeros) and 192.168.1.255 (binary; 11111111; all ones) addresses cannot be assigned to a host. They are the network and broadcast address of that subnet.

GlitchyDot said:
only laptop runs DHCP
Click to expand...
That's fine, as long as the IP address it receives is in the 192.168.1.0/24 range.
 
SirDice said:
This is typical behavior when a firewall is blocking the connection.
Click to expand...
I think i know then what is what... gonna quickly try to move my pf.conf file to see if it changes anything.
SirDice said:
No, up to and including .254. .255 is the broadcast address of that network range. Each range has two addresses you cannot assign to a host, all zeros and all ones. In a 192.168.1.0/24 the 192.168.1.0 (binary; 00000000; all zeros) and 192.168.1.255 (binary; 11111111; all ones) addresses cannot be assigned to a host. They are the network and broadcast address of that subnet.
Click to expand...
Understood.
 
Connection refused usually means it received a RST to a SYN packet (the connection attempt). You get a RST if the port is closed, that usually means the service isn't running and there's nothing listening on that port. A "connection timed out" happens when the SYN was sent and it never received a response. That's usually a firewall dropping the SYN.

Firewalls can be configured to send a RST in response to a SYN, so it isn't foolproof, but most firewalls are configured to simply drop the packet.
 
You must log in or register to reply here.
Back
Top