@larryjb said in Netgate 1100 connection: Even though I added my phone MAC to a static address Remember that (most ?!) phones change randomize their MAC address. If you trust your own wifi/LAN ( ^^ ), you could/should/would set, for this wifi connection, the randomize option off. This way the DHCP server can honor the static MAC lease, as the MAC doesn't change anymore.

@stephenw10 Thanks for the response. Sounds like a regression. (I saw a security advantage to the way 26.03 worked - beeping at login and logout - but I guess that itself was a regression from the intended operation - beep at login only.) I'll file a regression.

Urgh, dissatisfying indeed. Weird. Hard to see what might have caused that and just went away. Unless it was something upstream. Somehow.

@nvwasher So it was a 'drive' problem ?

All of that has to be handled by ACLs in the switch in that setup. It's non-trivial! If you truly need 25Gbps between internal subnets though that will do it.

@giorgix3 if you have not check already, have a search in the community forum of Swisscom, https://community.swisscom.ch.

Right. Does it ever show as linked correctly? Very odd to see packets both ways but no link!

@Laxarus Good guess. It is a 40mm 5v fan powered by one of the USB ports. Without cooling the WAS-110 will overheat and shutdown. With the fan and shroud it stays around 20c above ambient.

Yes it's unlikely we would see that in the 2.8.1 branch. That will be good if it proves two versions are no longer needed.

pfSense LCDproc package worked out of the box with a 635 on CE 2.8.1

@skogs This may be what is happening. I am having a very very slow load time on some webpages. I have never used developer tools before but I will try them on Safari and Firefox and see what is going on. btw, I have "private relay" off in Safari.

What program should I use to compare the original and modified file to see what has changed?

Yup you can confirm it at the console. Drop to the command line using option 8 at the menu then enter ifconfig. That will show you which NICs are linked. So if you connect only one port you will be able to see which NIC that is. For example on this box only the WAN is connected: [admin@4220.stevew.lan]/root: ifconfig igb0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500 options=4e100bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWFILTER,RXCSUM_IPV6,TXCSUM_IPV6,HWSTATS,MEXTPG> ether 00:08:a2:0b:c4:86 inet 172.21.16.214 netmask 0xffffff00 broadcast 172.21.16.255 inet6 fe80::208:a2ff:fe0b:c486%igb0 prefixlen 64 scopeid 0x1 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=823<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL,STABLEADDR> igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 description: LAN options=4e100bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWFILTER,RXCSUM_IPV6,TXCSUM_IPV6,HWSTATS,MEXTPG> ether 00:08:a2:0b:c4:87 inet 192.168.195.1 netmask 0xffffff00 broadcast 192.168.195.255 inet6 fe80::208:a2ff:fe0b:c487%igb1 prefixlen 64 scopeid 0x2 media: Ethernet autoselect status: no carrier nd6 options=821<PERFORMNUD,AUTO_LINKLOCAL,STABLEADDR>

@stephenw10 Thanks so much, the connection link really helped. I found the problem on Linux was the usb port name default was wrong. Why I do was run the active syslog viewer and saw which port was being used for the SG-1100. In Putty, the port was misspelled for that district of Linux. Once fixed, it worked. Thanks again.

@matt-q Indeed, appropriate SMD tools are strongly recommended both for the removal of such a tiny resistor and for the repair work. Sometimes its possible to run a bypass wire between the pads at each end of the track if they can be traced, but since in this case one end runs either to or under the Marvell chip, that's likely not an option. My comment about cutting tracks was general BTW as I have seen the suggestion mentioned elsewhere as well. This does provide an option In the absence of the necessary SMD tools but as you have discovered, is not without risk.

Yup the flow control is negotiated on the connection so whilst it might be enabled on both interfaces in pfSense only the switch is allowing it.

I got on Google Fiber about a week ago, the 3 gigabit tier. I used the Intel 540 card that I mentioned and it's working pretty well.

I used these steps along with those found at https://ryjelsum.me/homelab/sicom-bypass-cards/ the FTP password referenced on ryjelsum.me website is not working currently, so super stoked the author uploaded to internet archive. https://archive.org/details/silicom-pxgxbp-sd-cd With these steps and the files that ryjelsum uploaded to the internet archive, hopefully we can keep these old useful NIC's going for a bit longer. Currently the official website files at https://www.silicom-usa.com/cats/server-adapters/networking-bypass-adapters/ are all dead links, you click and get an 8bit file.

@stephenw10 Thank you. Updating the firewall fixed it. I'm embarrassed it was so far behind. Opendns was blocking it from showing an update was available and in addition it was reporting to me I was on the latest. Thanks for looking at my post!