Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    LAN machine can't ping printer

    Scheduled Pinned Locked Moved
    Virtualization
    4
    25
    524
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • johnpozJ
      johnpoz LAYER 8 Global Moderator @JonathanLee
      last edited by

      @JonathanLee my guess is he just posted the numbers he saw on an output of ifconfig or something without really understanding what it was

      inet 192.168.2.253 netmask 0xffffff00 broadcast 192.168.2.255

      That is just showing the directed broadcast address.

      An intelligent man is sometimes forced to be drunk to spend time with his fools
      If you get confused: Listen to the Music Play
      Please don't Chat/PM me for help, unless mod related
      SG-4860 24.03 | Lab VMs 2.7.2, 24.03

      E 1 Reply Last reply Reply Quote 2
      • E
        eiger3970 0 @johnpoz
        last edited by

        This post is deleted!
        1 Reply Last reply Reply Quote 0
        • E
          eiger3970 0 @JonathanLee
          last edited by eiger3970 0

          @JonathanLee I'm confused?
          My printer did have network settings:
          192.168.1.160/24 255.255.255.0, but I changed it to:
          192.168.1.160/24 192.168.1.255, because the output of the LAN computer and VM router both show:
          192.168.1.120/24 192.168.1.255 and:
          192.168.1.170/24 192.168.1.255 respectively.

          I have always used 255.255.255.0, so I'm a bit unclear why this changed to 192.168.1.255?

          johnpozJ JonathanLeeJ 2 Replies Last reply Reply Quote 0
          • johnpozJ
            johnpoz LAYER 8 Global Moderator @eiger3970 0
            last edited by

            @eiger3970-0 nothing changed the mask should be 255.255.255.0 or /24.. That 192.168.1.255 is the directed broadcast address.. See the netmask there in my example 0xffffff00, that would convert to 255.255.255.0

            No wonder your having issues if you changed the mask to 192.168.1.255 - which to be honest not sure why the printer would even accept such a number, its not a valid network mask.

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.03 | Lab VMs 2.7.2, 24.03

            E 1 Reply Last reply Reply Quote 1
            • E
              eiger3970 0 @johnpoz
              last edited by

              @johnpoz thanks.
              I changed 255.255.255.0 to 192.168.1.255 after the problem, as a fix attempt.

              Yes, somehow it's working, but I'll change back to the typical 255.255.255.0 on the printer.

              1 Reply Last reply Reply Quote 0
              • JonathanLeeJ
                JonathanLee @eiger3970 0
                last edited by

                @eiger3970-0 Don't change that it should be 255.255.255.0 as your subnet with the cider notion of /24

                Make sure to upvote

                E 1 Reply Last reply Reply Quote 1
                • E
                  eiger3970 0 @JonathanLee
                  last edited by

                  @JonathanLee Hello, I changed the printe to:
                  IP address: 192.168.1.160
                  Netmask: 255.255.255.0
                  Gateway 192.168.1.170

                  Unfortunately, the computer won't ping the printer via the VM router?

                  Computer with Ethernet cable to printer.

                  linuxmint@linuxmint:~$ ip -c a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 1c:61:b4:6d:38:4f brd ff:ff:ff:ff:ff:ff
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:ca:06:f0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 1c:61:b4:6d:38:4f brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.120/24 brd 192.168.1.255 scope global noprefixroute br0
       valid_lft forever preferred_lft forever
    inet6 fe80::1e61:b4ff:fe6d:384f/64 scope link 
       valid_lft forever preferred_lft forever
6: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:ac:44:b5 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:feac:44b5/64 scope link 
       valid_lft forever preferred_lft forever
7: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:a1:d1:e2 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fea1:d1e2/64 scope link 
       valid_lft forever preferred_lft forever
8: vnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN group default qlen 1000
    link/ether fe:54:00:09:d3:92 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:fe09:d392/64 scope link 
       valid_lft forever preferred_lft forever

                  VM router:

                  linuxmint@linuxmint:~$ ssh admin@192.168.1.170
(admin@192.168.1.170) Password for admin@pfSense.home.arpa:
QEMU Guest - Netgate Device ID: 623d6cd6daf11688adb4

*** Welcome to pfSense 2.7.2-RELEASE (amd64) on pfSense ***

 WAN (wan)       -> re0        -> v4/DHCP4: 100.76.25.213/10
 LAN (lan)       -> vtnet0     -> v4: 192.168.1.170/24

 0) Logout (SSH only)                  9) pfTop
 1) Assign Interfaces                 10) Filter Logs
 2) Set interface(s) IP address       11) Restart webConfigurator
 3) Reset webConfigurator password    12) PHP shell + pfSense tools
 4) Reset to factory defaults         13) Update from console
 5) Reboot system                     14) Disable Secure Shell (sshd)
 6) Halt system                       15) Restore recent configuration
 7) Ping host                         16) Restart PHP-FPM
 8) Shell

Enter an option: 8

[2.7.2-RELEASE][admin@pfSense.home.arpa]/root: ifconfig
vtnet0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
	description: LAN
	options=800b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,LINKSTATE>
	ether 52:54:00:09:d3:92
	inet 192.168.1.170 netmask 0xffffff00 broadcast 192.168.1.255
	inet6 fe80::5054:ff:fe09:d392%vtnet0 prefixlen 64 scopeid 0x1
	media: Ethernet autoselect (10Gbase-T <full-duplex>)
	status: active
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
re0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
	description: WAN
	options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
	ether a8:a1:59:6e:1f:8b
	inet 100.76.25.213 netmask 0xffc00000 broadcast 100.127.255.255
	inet6 fe80::aaa1:59ff:fe6e:1f8b%re0 prefixlen 64 scopeid 0x2
	media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
enc0: flags=0 metric 0 mtu 1536
	options=0
	groups: enc
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
lo0: flags=1008049<UP,LOOPBACK,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 16384
	options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
	inet 127.0.0.1 netmask 0x0
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
	groups: lo
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
pflog0: flags=100<PROMISC> metric 0 mtu 33152
	options=0
	groups: pflog
pfsync0: flags=0 metric 0 mtu 1500
	options=0
	maxupd: 128 defer: off version: 1400
	syncok: 1
	groups: pfsync
ovpns1: flags=1008043<UP,BROADCAST,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 1500
	options=80000<LINKSTATE>
	inet 10.0.8.1 netmask 0xffffff00 broadcast 10.0.8.255
	inet6 fe80::aaa1:59ff:fe6e:1f8b%ovpns1 prefixlen 64 scopeid 0x7
	groups: tun openvpn
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
	Opened by PID 54760
                  E 1 Reply Last reply Reply Quote 0
                  • E
                    eiger3970 0 @eiger3970 0
                    last edited by

                    @eiger3970-0 Just noticed the computer said Wired Lan cable was unplugged.
                    I barely touched the Ethernet cable at the back and the RJ45 NIC PCIe LED turned on and green.
                    I guess that's the LAN enp2s0 that changed from DOWN to UP.
                    Must be something wrong with the NIC, the NIC's insertion into the MOBO or the cable...nothing was touched before the problem.

                    1 Reply Last reply Reply Quote 0
                    • JonathanLeeJ
                      JonathanLee
                      last edited by

                      Your gateway isn’t .1 ?

                      Make sure to upvote

                      E 1 Reply Last reply Reply Quote 1
                      • E
                        eiger3970 0 @JonathanLee
                        last edited by

                        @JonathanLee This is solved, somehow, I don't remember...just noting the thread can be closed.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post