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

    Status: no carrier - При том что кабель подключён

    Scheduled Pinned Locked Moved Russian
    20 Posts 6 Posters 17.7k Views
    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.
    • K
      Konstanti @Prototip
      last edited by Konstanti

      @Prototip а линк от провайдера быстро поднимается , при включении кабеля ???
      После загрузки pf , покажите вывод команды ifconfig -m

      И еще вопрос - если между pf и провайдером поставить коммутатор , работающий на уровне 2 ( те шнур от провайдера и шнур от pfsense были бы в одном vlan-e ), что-нибудь изменится ???

      1 Reply Last reply Reply Quote 0
      • P
        Prototip
        last edited by

        ifconfig -m сразу после загрузки:

        re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        capabilities=18399b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_UCAST,WOL_MCAST,WOL_MAGIC,LINKSTATE,NETMAP>
        ether d4:ca:6d:29:8f:fc
        hwaddr d4:ca:6d:29:8f:fc
        inet6 fe80::d6ca:6dff:fe29:8ffc%re0 prefixlen 64 scopeid 0x1
        inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet 100baseTX <full-duplex>
        status: active
        supported media:
                media autoselect mediaopt flowcontrol
                media autoselect
                media 1000baseT mediaopt full-duplex,flowcontrol,master
                media 1000baseT mediaopt full-duplex,flowcontrol
                media 1000baseT mediaopt full-duplex,master
                media 1000baseT mediaopt full-duplex
                media 1000baseT mediaopt master
                media 1000baseT
                media 100baseTX mediaopt full-duplex,flowcontrol
                media 100baseTX mediaopt full-duplex
                media 100baseTX
                media 10baseT/UTP mediaopt full-duplex,flowcontrol
                media 10baseT/UTP mediaopt full-duplex
                media 10baseT/UTP
                media none
re1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        capabilities=18399b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_UCAST,WOL_MCAST,WOL_MAGIC,LINKSTATE,NETMAP>
        ether 50:3e:aa:08:ca:5b
        hwaddr 50:3e:aa:08:ca:5b
        inet6 fe80::523e:aaff:fe08:ca5b%re1 prefixlen 64 scopeid 0x2
        inet 10.10.11.101 netmask 0xffffff00 broadcast 10.10.11.255
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
        supported media:
                media autoselect mediaopt flowcontrol
                media autoselect
                media 1000baseT mediaopt full-duplex,flowcontrol,master
                media 1000baseT mediaopt full-duplex,flowcontrol
                media 1000baseT mediaopt full-duplex,master
                media 1000baseT mediaopt full-duplex
                media 1000baseT mediaopt master
                media 1000baseT
                media 100baseTX mediaopt full-duplex,flowcontrol
                media 100baseTX mediaopt full-duplex
                media 100baseTX
                media 10baseT/UTP mediaopt full-duplex,flowcontrol
                media 10baseT/UTP mediaopt full-duplex
                media 10baseT/UTP
                media none
enc0: flags=0<> metric 0 mtu 1536
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        groups: enc
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        capabilities=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        groups: lo
pflog0: flags=100<PROMISC> metric 0 mtu 33160
        groups: pflog
pfsync0: flags=0<> metric 0 mtu 1500
        groups: pfsync
        syncpeer: 224.0.0.240 maxupd: 128 defer: on
        syncok: 1

        Поставил между pfSense и провайдером 100Мбит неуправляемый свитч, ничего не изменилось.

        А теперь интересное уточнение, связанное со временем появления сети (лог из Packet Capture):

        pfSense загрузился.
23:13:57.258183 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300   <-- запустил Packet Capture
23:13:58.260566 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
23:14:00.202766 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
23:14:05.165546 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
23:14:17.101047 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
23:14:19.089043 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300  <-- где-то здесь вытащил и воткнул интернет-кабель
23:14:23.305040 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
23:14:29.609039 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
23:14:42.152105 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
23:14:51.028713 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
23:15:01.528409 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
23:15:11.028113 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
23:16:00.463765 IP6 fe80::62e3:27ff:fe99:ade7.546 > ff02::1:2.547: UDP, length 92  <-- в консоли ввел команду "tcpdump -i re0 udp"
23:16:09.199577 IP6 fe80::62e3:27ff:fe99:ade7.546 > ff02::1:2.547: UDP, length 92
23:16:26.517223 IP6 fe80::62e3:27ff:fe99:ade7.546 > ff02::1:2.547: UDP, length 92
23:16:27.583056 IP6 fe80::62e3:27ff:fe99:ade7.546 > ff02::1:2.547: UDP, length 92
23:16:29.683420 IP6 fe80::62e3:27ff:fe99:ade7.546 > ff02::1:2.547: UDP, length 92
23:16:33.995735 IP6 fe80::62e3:27ff:fe99:ade7.546 > ff02::1:2.547: UDP, length 92
23:16:43.010774 IP6 fe80::62e3:27ff:fe99:ade7.546 > ff02::1:2.547: UDP, length 92
23:16:54.578956 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
23:16:54.605361 IP 5.100.120.1.67 > 5.100.120.31.68: UDP, length 321  <-- поймал настройки по dhcp
23:16:54.611194 IP 5.100.120.1.67 > 5.100.120.31.68: UDP, length 321
23:16:54.616286 IP 5.100.120.31.43022 > 202.12.27.33.53: UDP, length 28
23:16:54.617711 IP 5.100.120.1.67 > 5.100.120.31.68: UDP, length 321
23:16:54.650724 IP 202.12.27.33.53 > 5.100.120.31.43022: UDP, length 1097
23:16:55.695699 IP 5.100.120.31.11729 > 192.112.36.4.53: UDP, length 28
23:16:55.853101 IP 192.112.36.4.53 > 5.100.120.31.11729: UDP, length 1097
23:16:55.853354 IP 5.100.120.31.6857 > 193.0.14.129.53: UDP, length 28
23:16:55.958942 IP 193.0.14.129.53 > 5.100.120.31.6857: UDP, length 1289
23:16:55.959088 IP 5.100.120.31.54899 > 192.112.36.4.53: UDP, length 28
23:16:56.025344 IP 5.100.120.31.62528 > 109.126.2.209.53: UDP, length 45
23:16:56.025821 IP 109.126.2.209.53 > 5.100.120.31.62528: UDP, length 127
23:16:56.120957 IP 192.112.36.4.53 > 5.100.120.31.54899: UDP, length 1097
23:16:56.121136 IP 5.100.120.31.13696 > 199.9.14.201.53: UDP, length 28
23:16:56.425244 IP 199.9.14.201.53 > 5.100.120.31.13696: UDP, length 864
23:16:56.425413 IP 5.100.120.31.50035 > 199.7.83.42.53: UDP, length 28
23:16:56.533639 IP 199.7.83.42.53 > 5.100.120.31.50035: UDP, length 864
23:16:56.533793 IP 5.100.120.31.37366 > 202.12.27.33.53: UDP, length 28
23:16:56.568266 IP 202.12.27.33.53 > 5.100.120.31.37366: UDP, length 864
23:16:56.568387 IP 5.100.120.31.57465 > 198.97.190.53.53: UDP, length 28
23:16:56.804932 IP 198.97.190.53.53 > 5.100.120.31.57465: UDP, length 864
23:16:56.805057 IP 5.100.120.31.31978 > 192.112.36.4.53: UDP, length 28
23:16:56.959520 IP 192.112.36.4.53 > 5.100.120.31.31978: UDP, length 864
23:16:56.959610 IP 5.100.120.31.56797 > 198.41.0.4.53: UDP, length 28
23:16:57.025324 IP 5.100.120.31.6208 > 109.126.2.208.53: UDP, length 34
23:16:57.025861 IP 109.126.2.208.53 > 5.100.120.31.6208: UDP, length 97
23:16:57.121442 IP 198.41.0.4.53 > 5.100.120.31.56797: UDP, length 864
23:16:57.123191 IP 5.100.120.31.60356 > 198.97.190.53.53: UDP, length 37
23:16:57.316768 IP 5.100.120.31.47110 > 199.9.14.201.53: UDP, length 28
23:16:57.354167 IP 198.97.190.53.53 > 5.100.120.31.60356: UDP, length 709
23:16:57.618412 IP 199.9.14.201.53 > 5.100.120.31.47110: UDP, length 1097
23:16:57.618752 IP 5.100.120.31.19092 > 192.36.148.17.53: UDP, length 28
23:16:57.756296 IP 192.36.148.17.53 > 5.100.120.31.19092: UDP, length 864
23:16:57.756388 IP 5.100.120.31.33159 > 198.97.190.53.53: UDP, length 28
23:16:57.999490 IP 198.97.190.53.53 > 5.100.120.31.33159: UDP, length 864
23:16:58.001131 IP 5.100.120.31.51943 > 192.33.4.12.53: UDP, length 37
23:16:58.269117 IP 192.33.4.12.53 > 5.100.120.31.51943: UDP, length 709
23:16:59.057026 IP 5.100.120.31.52910 > 192.58.128.30.53: UDP, length 28
23:16:59.172112 IP 192.58.128.30.53 > 5.100.120.31.52910: UDP, length 1097
23:16:59.172325 IP 5.100.120.31.45298 > 193.0.14.129.53: UDP, length 32
23:16:59.275263 IP 5.100.120.31.42538 > 109.126.2.209.53: UDP, length 46
23:16:59.280657 IP 193.0.14.129.53 > 5.100.120.31.45298: UDP, length 1163
23:16:59.280939 IP 5.100.120.31.26202 > 192.42.93.30.53: UDP, length 40
23:16:59.427578 IP 192.42.93.30.53 > 5.100.120.31.26202: UDP, length 621
23:16:59.427753 IP 5.100.120.31.55654 > 208.123.73.80.53: UDP, length 46
23:16:59.427797 IP 5.100.120.31.9576 > 162.208.119.38.53: UDP, length 44
23:16:59.512237 IP 109.126.2.209.53 > 5.100.120.31.42538: UDP, length 158
23:16:59.667576 IP 162.208.119.38.53 > 5.100.120.31.9576: UDP, length 136
23:16:59.667682 IP 5.100.120.31.54456 > 208.123.73.80.53: UDP, length 44
23:16:59.701113 IP 208.123.73.80.53 > 5.100.120.31.55654: UDP, length 158
23:16:59.701291 IP 5.100.120.31.35308 > 192.33.4.12.53: UDP, length 28
23:16:59.701372 IP 5.100.120.31.61989 > 192.33.4.12.53: UDP, length 37
23:16:59.940757 IP 208.123.73.80.53 > 5.100.120.31.54456: UDP, length 90
23:16:59.971547 IP 192.33.4.12.53 > 5.100.120.31.35308: UDP, length 864
23:16:59.972870 IP 192.33.4.12.53 > 5.100.120.31.61989: UDP, length 709
23:16:59.973251 IP 5.100.120.31.25823 > 192.42.93.30.53: UDP, length 32
23:17:00.118602 IP 192.42.93.30.53 > 5.100.120.31.25823: UDP, length 743
23:17:00.207680 IP6 fe80::62e3:27ff:fe99:ade7.546 > ff02::1:2.547: UDP, length 92
23:17:00.908630 IP 5.100.120.31.17627 > 109.126.2.208.53: UDP, length 34
23:17:00.908645 IP 5.100.120.31.12327 > 109.126.2.208.53: UDP, length 34
23:17:00.909038 IP 109.126.2.208.53 > 5.100.120.31.12327: UDP, length 97
23:17:00.909057 IP 109.126.2.208.53 > 5.100.120.31.17627: UDP, length 116
23:17:00.909539 IP 5.100.120.31.53945 > 217.10.68.152.10000: UDP, length 32
23:17:01.009713 IP 5.100.120.31.53945 > 217.10.68.152.10000: UDP, length 32
23:17:01.055440 IP 217.10.68.152.10000 > 5.100.120.31.53945: UDP, length 88
23:17:01.056001 IP 5.100.120.31.53945 > 217.10.68.152.10000: UDP, length 40
23:17:01.155534 IP 217.10.68.152.10000 > 5.100.120.31.53945: UDP, length 88
23:17:01.156192 IP 5.100.120.31.53945 > 217.10.68.152.10000: UDP, length 40
23:17:01.202459 IP 217.116.122.138.10001 > 5.100.120.31.53945: UDP, length 88
23:17:01.234611 IP6 fe80::62e3:27ff:fe99:ade7.546 > ff02::1:2.547: UDP, length 92
23:17:01.302718 IP 217.116.122.138.10001 > 5.100.120.31.53945: UDP, length 88
23:17:01.356457 IP 5.100.120.31.53945 > 217.10.68.152.10000: UDP, length 40
23:17:01.502974 IP 217.116.122.138.10001 > 5.100.120.31.53945: UDP, length 88
23:17:01.756674 IP 5.100.120.31.53945 > 217.10.68.152.10000: UDP, length 40
23:17:01.903134 IP 217.116.122.138.10001 > 5.100.120.31.53945: UDP, length 88
23:17:02.556878 IP 5.100.120.31.53945 > 217.10.68.152.10000: UDP, length 40
23:17:02.703376 IP 217.116.122.138.10001 > 5.100.120.31.53945: UDP, length 88
23:17:03.421060 IP6 fe80::62e3:27ff:fe99:ade7.546 > ff02::1:2.547: UDP, length 92
23:17:04.157021 IP 5.100.120.31.53945 > 217.10.68.152.10000: UDP, length 40
23:17:04.303473 IP 217.116.122.138.10001 > 5.100.120.31.53945: UDP, length 88

        Получается, что пока я не введу команду tcpdump, передергивание кабеля не приводит к появлению сети.

        K 1 Reply Last reply Reply Quote 0
        • K
          Konstanti @Prototip
          last edited by

          @Prototip У меня есть подозрение , что это проблемы домового коммутатора провайдера ( это при условии , что мы говорим о домашнем интернете)

          1 Reply Last reply Reply Quote 0
          • P
            Prototip
            last edited by

            Да, провайдер домашний. При этом микротик и личный комп ловят настройки быстро, без ручного ограничения скорости сети. Точно известно, что у провайдера коммутатор с гигабитными портами. И с их слов скорость на моем порту стоит 100Мбит (но не факт).

            K 2 Replies Last reply Reply Quote 0
            • K
              Konstanti @Prototip
              last edited by

              @Prototip У Вас стоит Реалтек - эта карта не всегда корректно работает c PF
              в журналах нет никаких записей странных ????

              1 Reply Last reply Reply Quote 0
              • K
                Konstanti @Prototip
                last edited by

                @Prototip
                Попробуйте в настройках сделать так
                /System/Advanced/Networking

                68f05887-0768-48a5-86c8-aa968d0211c4-image.png

                1 Reply Last reply Reply Quote 0
                • P
                  Prototip
                  last edited by Prototip

                  @Konstanti said in Status: no carrier - При том что кабель подключён:

                  Попробуйте в настройках сделать так

                  Не помогло.

                  А пока нашел такую странность. В логах DHCP сразу после загрузки, без всяких телодвижений:

                  Aug 21 00:00:38	dhclient		PREINIT
Aug 21 00:00:38	dhclient	5890	DHCPREQUEST on re0 to 255.255.255.255 port 67
Aug 21 00:00:40	dhclient	5890	DHCPREQUEST on re0 to 255.255.255.255 port 67
Aug 21 00:00:45	dhclient	5890	DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 1
Aug 21 00:00:46	dhclient	5890	DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 2
Aug 21 00:00:48	dhclient	5890	DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 2
Aug 21 00:00:50	dhclient	5890	DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 3
Aug 21 00:00:53	dhclient	5890	DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 4
Aug 21 00:00:57	dhclient	5890	DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 10
Aug 21 00:01:07	dhclient	5890	DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 15
Aug 21 00:01:22	dhclient	5890	DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 14
Aug 21 00:01:36	dhclient	5890	DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 10
Aug 21 00:01:46	dhclient	5890	No DHCPOFFERS received.
Aug 21 00:01:46	dhclient	5890	Trying recorded lease 5.100.120.31
Aug 21 00:01:46	dhclient		TIMEOUT
Aug 21 00:01:46	dhclient		Starting add_new_address()
Aug 21 00:01:46	dhclient		ifconfig re0 inet 5.100.120.31 netmask 255.255.254.0 broadcast 5.100.121.255
Aug 21 00:01:46	dhclient		New IP Address (re0): 5.100.120.31
Aug 21 00:01:46	dhclient		New Subnet Mask (re0): 255.255.254.0
Aug 21 00:01:46	dhclient		New Broadcast Address (re0): 5.100.121.255
Aug 21 00:01:46	dhclient		New Routers (re0): 5.100.120.1
Aug 21 00:01:47	dhclient		New Routers (re0): 5.100.120.1
Aug 21 00:01:48	dhclient		Deleting old routes
Aug 21 00:01:49	dhclient	5890	bound: renewal in 2704 seconds.

                  Как будто настройки применились. Но ifconfig показывает:

                  re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
        ether d4:ca:6d:29:8f:fc
        hwaddr d4:ca:6d:29:8f:fc
        inet6 fe80::d6ca:6dff:fe29:8ffc%re0 prefixlen 64 scopeid 0x1
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet 100baseTX <full-duplex>
        status: active
                  K 1 Reply Last reply Reply Quote 0
                  • K
                    Konstanti @Prototip
                    last edited by Konstanti

                    @Prototip Просто настройки сохранены были во временных файлах , оттуда он их и пытается взять
                    Самое странное,что нет ответа на DHCPrequest

                    1 Reply Last reply Reply Quote 0
                    • werterW
                      werter
                      last edited by werter

                      Добрый.

                      Вставьте эту сетевую в комп с Вин и проверьте. Не заведется - пишите в
                      спортлото                       провайдеру

                      Сетевой абсолютно все равно 2 или 4 пары обжаты, если обжим одинаков с обеих концов кабеля. Для FE - 1,2,3 и 6 , для GE - все пары.

                      1 Reply Last reply Reply Quote 0
                      • P
                        Prototip
                        last edited by

                        Спасибо всем за помощь, проблема была во строенной в мать сетевой карточке. Докупил вторую внешнюю карту (TP-LINK TG-3468), ограничил скорость до 100Мбит и всё заработало.
                        Материнская плата Intel DH61HO.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.